gnome-shell crashes when closing laptop lid #267
Comments
|
Tiling Assistant listens to a maximized/tiled window's I unfortunately can't reproduce it on my laptop that is connected to an external monitor. Can you reproduce it consistently? If so, does it require a specific window/app or something? |
|
Maybe related: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6731 [EDIT] Meaning that it might just be a GNOME bug. |
(Un)Fortunately, I've seen this only the one time; so don't have a (somewhat) reliable reproducer. |
The stacktrace looks quite different though (crash in mutter directly vs crash in JS). I'll open an issue on the GNOME Gitlab, too; maybe they have an idea. Presumably, even if there was a logic bug in Tiling assistant, that shouldn't result in gnome-shell crashes? |
|
I get it consistently ever after i installed Tiling-Assistant, exactly when moving the mouse in the locked screen while then trying to re-login (not from standby, jurt screen blanked): gnome-shell[1256292]: #1 56467f9fbfe8 i /home/user/.local/share/gnome-shell/extensions/tiling-assistant@lele>
gnome-shell[1256292]: #0 56467f9fc0d8 i /home/user/.local/share/gnome-shell/extensions/tiling-assistant@lele>
gnome-shell[1256292]: == Stack trace for context 0x56467d844980 ==
gnome-shell[1256292]: Bail out! libmutter:ERROR:../src/core/window.c:5779:meta_window_get_work_area_for_logical_moni>
gnome-shell[1256292]: libmutter:ERROR:../src/core/window.c:5779:meta_window_get_work_area_for_logical_monitor: asser>
gnome-shell[1256292]: **
How can i help? |
|
I cannot reproduce it anymore after reboot. |
|
It just happened again :-( |
|
My best guess as an interim solution: Can you comment out these 2 lines
in Note that the 'tiling states' of windows won't be saved after the screen is locked anymore. The windows will only look tiled but are considered floating. |
|
Some days now, and more than 3 times i have logged in without wayland crashing, and without observing any side-effects. Regarding the root cause, my guess is my 2 monitors and the asymetrical use of workspaces on them, Please consider merging this as is, or as an option for those who suffer like me :-) |
I am currently in my last semester, so I don't have much time ATM. Will be able to work on T-A again in a few weeks. I have an idea for a fix. That said, can you confirm that the workaround works? I could make a new release with just the workaround... |
Yes, it works. Today i had a crash without re-logging-in from a lock-screen: |
|
I confirm that now this last point i reported above crashes 3-4 times a day when i come back before the screen has been locked but it has dimmed, I'd appreciate if you can suggest me another hot-fix. |
|
@ankostis Can you open a new issue with some more information since it isn't related to the lockscreen (e. g. how do you trigger it, does it require specific windows or using specific features of Tiling Assistant). That said, that JS stack trace points to the 'active window hint' triggering the crash (somehow). So you can disable it in the preference window of Tiling Assistant. |
|
That won't fly for me, the active window hint has become by now a significant motivation for using the extension. I don't know if it is related, but since then i didn't have any crash (the last 3 days). For sure the bug is in mutter, and maybe happens in the is-maximized check, not in the is-full-screen. Anyhow, i think i will open x2 new issues, one for the crash you suggested and another one asking for hint-on-maximized windows. |
Describe the bug
gnome-shell crashes when closing the laptop's lid while connected to two external monitors via a dock. Reporting this here rather than for gnome-shell/mutter, since the extension is topmost in the stacktrace.
Steps To Reproduce
see above (this is the first time this happened to me, so it's possible that a specific layout of windows/overview being open/etc might be required)
System Info:
mainbranch...): 41, from EGOJournalctl logs
The text was updated successfully, but these errors were encountered: