Public bug reported:

Hi,

for the second time in two days I've hit a full desktop crash dripping
me back to the login screen.

Being the second time I could look for a pattern and found this:

Jun 23 12:28:35 paelzer gnome-shell[733850]: JS ERROR: Error: Trying to operate 
on an unmanaging window!
                                             
initialize/assertExistenceFor/</window.assertExistence@file:///usr/share/gnome-shell/extensions/[email protected]/src/extension/tilingWindowManager.js:36:31
                                             
_onMoveFinished@file:///usr/share/gnome-shell/extensions/[email protected]/src/extension/moveHandler.js:241:20
                                             
_onMoveStarted/id<@file:///usr/share/gnome-shell/extensions/[email protected]/src/extension/moveHandler.js:233:26
                                             
@resource:///org/gnome/shell/ui/init.js:20:20
Jun 23 12:28:35 paelzer google-chrome.desktop[735525]: 
[735520:735520:0623/122835.650515:ERROR:ui/compositor/presentation_time_recorder.cc:183]
 Invalid feedback timestamp (12): timestamp is not set
Jun 23 12:28:35 paelzer google-chrome.desktop[735525]: 
[735520:735520:0623/122835.650535:ERROR:ui/compositor/presentation_time_recorder.cc:183]
 Invalid feedback timestamp (13): timestamp is not set
Jun 23 12:28:35 paelzer google-chrome.desktop[735525]: 
[735520:735520:0623/122835.709374:ERROR:ui/compositor/presentation_time_recorder.cc:183]
 Invalid feedback timestamp (14): timestamp is not set
Jun 23 12:28:35 paelzer google-chrome.desktop[735525]: 
[735520:735520:0623/122835.709389:ERROR:ui/compositor/presentation_time_recorder.cc:183]
 Invalid feedback timestamp (15): timestamp is not set
Jun 23 12:28:35 paelzer gnome-shell[733850]: **
Jun 23 12:28:35 paelzer gnome-shell[733850]: 
libmutter:ERROR:../src/core/window.c:6041:meta_window_get_workspaces: code 
should not be reached
Jun 23 12:28:35 paelzer gnome-shell[733850]: Bail out! 
libmutter:ERROR:../src/core/window.c:6041:meta_window_get_workspaces: code 
should not be reached
Jun 23 12:28:35 paelzer gnome-shell[733850]: GNOME Shell crashed with signal 6
Jun 23 12:28:35 paelzer gnome-shell[733850]: == Stack trace for context 
0x6457d660d200 ==
Jun 23 12:28:35 paelzer gnome-shell[733850]: #0   7ffecd97aac0 b   
file:///usr/share/gnome-shell/extensions/[email protected]/src/extension/moveHandler.js:497
 (279e00561bf0 @ 449)
Jun 23 12:28:35 paelzer gnome-shell[733850]: #1   6457d6704eb8 i   
file:///usr/share/gnome-shell/extensions/[email protected]/src/extension/moveHandler.js:482
 (279e00561c40 @ 114)
Jun 23 12:28:35 paelzer gnome-shell[733850]: #2   6457d6704e28 i   
resource:///org/gnome/shell/ui/init.js:20 (12080d98d8d0 @ 48)

That seems similar but not the same as https://github.com/ubuntu/Tiling-
Assistant/issues/329

But then I found https://github.com/ubuntu/Tiling-Assistant/issues/435
which seems to be exactly that.

Sadly I'm not even sure what to do further to debug this, for now all I
can do is probably disabling the extension? If this has been reported
more, or if you can tell me what debug info you need please let me know,

P.S. I do not yet know how to force-reproduce it :-/

** Affects: gnome-shell-extensions (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: gnome-shell-extensions
   Importance: Undecided
       Status: New

** No longer affects: gnome-shell-extensions

** Bug watch added: github.com/ubuntu/Tiling-Assistant/issues #435
   https://github.com/ubuntu/Tiling-Assistant/issues/435

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2157969

Title:
  tiling-assistant crashes 26.04 gnome desktop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/2157969/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to