workrave icon indicating copy to clipboard operation
workrave copied to clipboard

workrave causes gnome-shell to get stuck

Open jmallach opened this issue 6 years ago • 3 comments

Describe the bug

GNOME Shell gets stuck as if the Windows key was pressed, and only remedy is to close user session and start it again.

To Reproduce Steps to reproduce the behavior:

I haven't been able to figure out what triggers it. Sometimes it triggers when the session is in use, but most of the time I find that after unlocking the laptop after idling, the sessions is corrupt in this way. journal says:

d’ag. 08 15:59:41 penyagolosa workrave[28079]: g_bus_watch_name_on_connection: assertion 'g_dbus_is_name (name)' failed d’ag. 08 15:59:41 penyagolosa gnome-shell[27894]: Object St.BoxLayout (0x55872e0d7450), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroye d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: == Stack trace for context 0x55872bdac340 == d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #0 0x55872e61a238 i resource:///org/gnome/shell/ui/popupMenu.js:717 (0x7fd512623ef0 @ 22) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #1 0x7fff4c324650 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #2 0x7fff4c324700 b resource:///org/gnome/shell/ui/popupMenu.js:735 (0x7fd512626230 @ 23) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #3 0x7fff4c3247c0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #4 0x55872e61a140 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:271 (0x7fd5109bf5e8 @ 32) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #5 0x55872e61a0b0 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:148 (0x7fd51098dd58 @ 177) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #6 0x55872e61a020 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:110 (0x7fd51098dbc0 @ 43) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #7 0x7fff4c3254c0 b self-hosted:916 (0x7fd5242f1230 @ 367) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #8 0x55872c1682c8 i resource:///org/gnome/shell/ui/panelMenu.js:192 (0x7fd512676ef0 @ 74) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #9 0x7fff4c327990 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #10 0x55872c168250 i /usr/share/gnome-shell/extensions/[email protected]/extension.js:351 (0x7fd5109bf6f8 @ 12) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #11 0x55872c168190 i resource:///org/gnome/shell/ui/extensionSystem.js:82 (0x7fd512654d58 @ 431) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #12 0x55872c168110 i resource:///org/gnome/shell/ui/extensionSystem.js:344 (0x7fd51265c890 @ 13) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #13 0x7fff4c3286c0 b self-hosted:251 (0x7fd5242c4ab0 @ 223) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #14 0x55872c168090 i resource:///org/gnome/shell/ui/extensionSystem.js:343 (0x7fd51265c808 @ 64) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #15 0x55872c168010 i resource:///org/gnome/shell/ui/extensionSystem.js:361 (0x7fd51265c918 @ 87) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #16 0x7fff4c329b90 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5242d2230 @ 386) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #17 0x7fff4c32a380 b resource:///org/gnome/shell/ui/sessionMode.js:204 (0x7fd51236a670 @ 254) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #18 0x55872c167eb0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #19 0x55872c167e28 i resource:///org/gnome/shell/ui/sessionMode.js:166 (0x7fd51236a450 @ 40) d’ag. 08 15:59:41 penyagolosa gnome-shell[27894]: Object St.BoxLayout (0x55872e0d7450), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroye d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #20 0x55872c167d80 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #21 0x55872c167cd8 i resource:///org/gnome/shell/ui/screenShield.js:1279 (0x7fd51234fbc0 @ 188) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #22 0x55872c167c30 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #23 0x55872c167ba8 i resource:///org/gnome/shell/ui/screenShield.js:899 (0x7fd51234ecd0 @ 18) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #24 0x55872c167b00 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #25 0x55872c167a40 i self-hosted:916 (0x7fd5242f1230 @ 367) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #26 0x55872c167970 i resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5242d2230 @ 386) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #27 0x55872c1678f0 i resource:///org/gnome/shell/ui/lightbox.js:186 (0x7fd51263e560 @ 29) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #28 0x55872c167850 i resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7fd5242d2b38 @ 54) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #29 0x55872c167730 i resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7fd5242d2bc0 @ 1626) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #30 0x55872c1676a0 i resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7fd5242d2c48 @ 100) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #31 0x55872c167628 i resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7fd5242d2cd0 @ 10) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #32 0x55872c167558 i resource:///org/gnome/gjs/modules/signals.js:128 (0x7fd5242d2230 @ 386) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #33 0x55872c1674c8 i resource:///org/gnome/shell/ui/tweener.js:244 (0x7fd5242cf808 @ 159) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #34 0x55872c167420 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fd5242b5de0 @ 71) d’ag. 08 15:59:41 penyagolosa org.gnome.Shell.desktop[27894]: #35 0x55872c1673a0 i resource:///org/gnome/shell/ui/tweener.js:219 (0x7fd5242cf780 @ 15)

I haven't been able to pinpoint what update caused this either.

Expected behavior

GNOME Shell and workrave are good buddies and don't fight.

** Linux (please complete the following information in case you encountered the bug on Linux):**

  • Distribution: Debian
  • Distribution Version: current unstable
  • Desktop Environment: GNOME 3.28
  • Workrave Version: 1.10 as distributed by Debian

jmallach avatar Aug 09 '18 04:08 jmallach

I fix this assertion: d’ag. 08 15:59:41 penyagolosa workrave[28079]: g_bus_watch_name_on_connection: assertion 'g_dbus_is_name (name)' failed

Still checking the remainder of the stack trace.

rcaelers avatar Aug 29 '18 19:08 rcaelers

@jmallach I can reproduce this bug! Is it fixed for you?

mattia-b89 avatar Apr 14 '19 08:04 mattia-b89

I never managed to reproduce the "gets stuck" part of this report. Does it still happen with more recent versions of Gnome/Workrave?

rcaelers avatar May 12 '21 19:05 rcaelers