-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Layout settings window is not showing up in Ubuntu 22.04 Wayland GNOME desktop #59
Comments
Interesting, I assume this holds for both the button on the main screen and the button in the live configuration screen? Is there any error output present in the console? On Windows this works fine and I don't immediately see anything that would be significantly different on Ubuntu, so this might be a hard one to debug. I'll first see if I can reliably reproduce this to get more data to work with. |
I found that this bug can be reproduced in Ubuntu 20.04 X11 GNOME desktop. The main screen is fine, and the grids are shown correctly. The layout configuration screen is not showing up. There is a Java exceptions showing in the console:
|
Awesome, that's exactly what I need. I have no idea what the root cause of this issue is, since in theory this looks like it should affect Windows as well (but it doesn't). However, this should be enough information to at least mitigate the issue even if I can't find the true cause. |
fix issue roan/KeysPerSecond#227 (GitLab) fix issue #59 (GitHub)
This should be fixed now in v8.7, though I didn't manage to reproduce the issue on my own Ubuntu install (not running Wayland GNOME though). However, it seems like this probably had more to do with the exact version/distribution of Java being used anyway. |
Still reproducable for v8.7 on Ubuntu 20.04 X11 GNOME. Exactly the same exception. |
Confirmed also still reproducable on another Ubuntu machine (Ubuntu 22.04). |
Thanks for the extra information, are you sure the exception is exactly the same? Because as far as I can tell that shouldn't be possible anymore. I should have a system lying around with those specifications though, so I'll try to reproduce it. |
Alright, I've managed to reproduce it (slightly different line numbers), still not sure what the cause is, but this should help to figure that out. |
Actually, the new line numbers gave it away. I fixed the bug in the location from your original exception, but it turns out that there is another place I used the same pattern that I did not fix. So this should be fairly easy to resolve. |
fix issue #59 fix issue roan/KeysPerSecond#227
Confirmed this to be really fixed now, the fix will be released with version 8.8 (already available on master). |
And thanks again for the report and extra information! |
Just as the title says. Other windows (configure keys, about, etc.) work just fine so far.
The text was updated successfully, but these errors were encountered: