-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Handle exotic window managers better #212
Comments
Thank you for testing! |
From the stack-trace, it doesn't seem related to the window-manager, though. |
If you want to debug more, you can try passing |
will do |
When running with
|
Running with all other flags, i get a pretty "This program has crashed" Dialog, and the following output in gdb:
Backtrace:
|
@kusma I agree it doesn't seem to be directly related to the window-manager, but my theory is that it is a "follow error" due to uno disagreeing with the OS on the window size, as it is forced. I do not expect any references to the window manager in this case, and we do see that |
No, this seems to happen in the type system, which I think is extremely unlikely to be related to window geometry. |
Ok. How can i assist in debugging this issue further |
If you can set a breakpoint and inspect local variables, it'd be interesting to see the values of |
Also, does it crash if you run a plain empty project?
|
Note: i am not expecting some fancy solution to this, i'm just suggesting that it doesn't crash
My window manager(i3) starts applications as tiles with forced sizes by default. Fuse does not like this, and segfaults. I figured out that was the reason, as adding a float override to the window title in i3's config solved the issue.
Stack trace:
Expected behavior
App launches in some way shape or form
Actual behavior
Segfault
Suggested fix
My assumption is that uno is making assumptions based on an expected window size. I think, without looking at the code, that basing all size calculations on the actual window size coud fix this. But it's probably not that easy.
OS details
The text was updated successfully, but these errors were encountered: