New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GUI stops updating unless the window is resized on some Linux setups #358
Comments
Indeed, I've been seeing these issues as well. I've spent many days poring over SolveSpace's OpenGL code and found absolutely nothing; half of my debugging tools do not indicate that I'm doing anything wrong at all, and the other perturb the environment just enough to make the bugs disappear. These are very frustrating. |
Can't reproduce this problem. |
@diggit are you using compositor? I have Qtile with Compton and no window decorations. |
Usually, I do not use compositor. Now I tested solvespace with compton and xcompmgr using some default config and everything seemed ok. That probably points to HW specific problem or some special SW combination/settings. |
Closing as upstream bug (see comment). |
Keeping this open since people are still hitting it... |
I'm affected as well. On my first computer with nVidia graphics SolveSpace works, but on second with only Intel graphics not. Both laptops have Gentoo Linux and KDE with compositor (kwin). On both SolveSpace compiled from sources. nVidia one compiled at 22:42:50 1.10.2018 (3.0~258545a3). The Intel only version I will check tomorrow. |
Yep. Unfortunately there is nothing I can do as this is an upstream bug. I'm sorry. |
Just tested a patch in upstream bug and it fixed SolveSpace behaviour on my i965. |
Fixed in git, I can confirm that it now works better than ever before. |
Was this supposed to be fixed? |
I have also hit this recently with NVidia graphics. Unfortunately still no idea what causes it. Sorry. |
Sorry to keep bumping this old issue, but I just managed to get it working again by using updated drivers from this PPA: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers , hopefully it may help others too. So now I can use Solvespace again :) Thanks for your work on this great program. |
This also worked for me on Lubuntu 18.04 on Dell Vostro laptop - can
finally start exploring v3 :)
Thanks guys for all the great work.
Phil
…On Fri, 1 Mar 2019 at 02:00, PhilipAnderson ***@***.***> wrote:
Sorry to keep bumping this old issue, but I just managed to get it working
again by using updated drivers from this PPA:
https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers , hopefully
it may help others too.
So now I can use Solvespace again :)
Thanks for your work on this great program.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#358 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ArunrtzSmndLrBWHJNRoxnSLy8ssUJqTks5vSInEgaJpZM4XAejB>
.
|
Thus far, I haven't hit this, except for the menu bug. I'm using Ubuntu 18.04 and NVidia RTX cards. |
I'm closing this because it's a fixed upstream bug I can't do anything about, but I'm also pinning it so that people can see it easily if they also have that problem. |
System information
SolveSpace version: 3.0~fb138f49 (from ppa) and also happens in 3.0~88d59ea7 (compiled myself a while ago)
Operating system: Ubuntu 18.10
Expected behavior
Rotation/zoom changes should be rendered immediately.
Actual behavior
They are rendered only after SolveSpace's window resizing
Demo: https://nextcloud.mokrynskyi.com/s/r8A8bdewa3qtZFK
Additional information
I believe this is a regression I've got after upgrading from Mesa 18.1.5 to 18.2.1, which fixed one bug I had and introduced this one.
UPD: The same happens on Mesa 18.3 from Git
UPD 2: Software rendering with
LIBGL_ALWAYS_SOFTWARE=1 solvespace
works nice and smooth, but menu is not rendering until clicked for the first time on each menu item.UPD 3: Mesa bug report: https://bugs.freedesktop.org/show_bug.cgi?id=108097
The text was updated successfully, but these errors were encountered: