Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Dash To Dock Causes Gnome Shell to crash when trying to lock computer #812

Closed
apastuszak opened this issue Sep 20, 2018 · 19 comments
Closed

Dash To Dock Causes Gnome Shell to crash when trying to lock computer #812

apastuszak opened this issue Sep 20, 2018 · 19 comments
Labels
bug

Comments

@apastuszak
Copy link

This happens when using Windows+L, when timeout value is reached, or when computer wakes from suspend. Any time the lock screen password prompt comes up, instead, Gnome Shell crashes and restarts.

I am using v64 on Gnome 3.30 on Arch Linux.

If I disable the extension, then the issue goes away.
@anhskohbo
Copy link

Confirm that, that happen to me too.

@alyssoncs
Copy link

That is happening to me too, after the computer wakes up, the lock screen becomes unresponsive. Not alowing me to access the login screen, although I'm still able to interact with the top bar.
The system acts normally after disableling the extension.

Debian unstable (buster)
Gnome 3.30.1

@Julien76
Copy link

Same issue here.
Manjaro with Gnome 3.30.

On the log screen the dock is visible.
After log-in, the dock becomes black (it is set to be transparent) and auto hide does not work and the dock is frozen to its state before screen lock: if I open a new software, it does not appears on the dock, if I click on the icon of an already opened software, nothing happens.

@Henry78
Copy link

Henry78 commented Oct 19, 2018 •
edited
Loading

Happens for me on Arch, report abou other extensions are crashing: Arch Forum Topic 240556

On my installation the keyboard stops working after locking the desktop with dash-to-dock installed. I'm still able to use the mouse (e.g. change the volume), but no keyboard, no unlock.

@apastuszak
Copy link
Author

apastuszak commented Oct 19, 2018 via email

@marko911
Copy link

The extension crashes when my screen auto locks and I have to re-install it every time.

@micheleg micheleg added the bug label Oct 28, 2018
@micheleg
Copy link
Owner

Probably same as #820.

@dvorapa
Copy link
Contributor

dvorapa commented Oct 8, 2019

#820 has been fixed, is this still an issue?

@SlimDeluxe
Copy link

Happens to me on Ubuntu 20.04 LTS with gnome 3.36.2.
Was working fine on 19.10 with kernel 5.3.*

So I am unable to use my favourite gnome extension 😢

syslog:

May 22 15:26:45 FX705GD kernel: [  312.903435] gnome-shell[6154]: segfault at 0 ip 00007f87d5e5c252 sp 00007ffc7a0e9280 error 4 in libst-1.0.so[7f87d5e3c000+4c000]
May 22 15:26:45 FX705GD kernel: [  312.903440] Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f
May 22 15:26:45 FX705GD systemd[4344]: gnome-shell-x11.service: Main process exited, code=dumped, status=11/SEGV
May 22 15:26:45 FX705GD systemd[4344]: gnome-shell-x11.service: Failed with result 'core-dump'.
May 22 15:26:45 FX705GD systemd[4344]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 4.
May 22 15:26:45 FX705GD systemd[4344]: Stopped target GNOME X11 Session (session: ubuntu).
May 22 15:26:45 FX705GD systemd[4344]: Stopping GNOME X11 Session (session: ubuntu).
May 22 15:26:45 FX705GD systemd[4344]: Stopped target GNOME X11 Session.
May 22 15:26:45 FX705GD systemd[4344]: Stopping GNOME X11 Session.
May 22 15:26:45 FX705GD systemd[4344]: Stopped target GNOME Shell on X11.
May 22 15:26:45 FX705GD systemd[4344]: Stopping GNOME Shell on X11.
May 22 15:26:45 FX705GD systemd[4344]: Stopped GNOME Shell on X11.
May 22 15:26:45 FX705GD systemd[4344]: Starting GNOME Shell on X11...

@SlimDeluxe
Copy link

SlimDeluxe commented May 24, 2020 •
edited
Loading

I have narrowed the problem down to using the Workspace Indicator extension by fmuellner.
Disabling the extension and then disabling and re-enabling "Dash to panel" fixes the problem. I can lock the screen again.
Edit: actually, it crashes without Workspace indicator too.

@1989gironimo
Copy link

Running 3.36 gnome on PureOS without having workspace indicator enabled and can confirm, that it doesn't crash.

@ksmolder
Copy link

On Ubuntu 20.04, the crash is unrelated to Workspace Indicator. Seeing the same behaviour as @SlimDeluxe:

May 30 18:07:19 saga kernel: [ 8424.892768] gnome-shell[56038]: segfault at 0 ip 00007ff87e5e97ff sp 00007ffe1c581950 error 4 in libst-1.0.so[7ff87e5c7000+4c000]
May 30 18:07:19 saga kernel: [ 8424.892774] Code: 97 00 00 00 48 83 eb 08 49 39 dc 0f 84 aa 01 00 00 48 8b 85 28 01 00 00 b9 0d 00 00 00 4c 89 ff 48 8b 14 18 48 8b 02 48 8b 00 <48> 8b 30 f3 a6 0f 97 c0 1c 00 84 c0 75 cc 48 8b 42 08 8b 08 83 f9
May 30 18:07:19 saga gsd-keyboard[56197]: Error reading events from display: Broken pipe
May 30 18:07:19 saga gsd-wacom[56219]: Error reading events from display: Broken pipe
May 30 18:07:19 saga nextcloud[56292]: Error reading events from display: Broken pipe
May 30 18:07:19 saga gsd-media-keys[56198]: Error reading events from display: Broken pipe
May 30 18:07:19 saga gsd-power[56199]: Error reading events from display: Broken pipe
May 30 18:07:19 saga evolution-alarm[56275]: Error reading events from display: Broken pipe
May 30 18:07:19 saga gsd-color[56192]: Error reading events from display: Broken pipe
May 30 18:07:19 saga nautilus[56159]: Error reading events from display: Broken pipe
May 30 18:07:19 saga systemd[52014]: gsd-media-keys.service: Main process exited, code=exited, status=1/FAILURE
May 30 18:07:19 saga systemd[52014]: gsd-media-keys.service: Failed with result 'exit-code'.
May 30 18:07:19 saga systemd[52014]: gsd-keyboard.service: Main process exited, code=exited, status=1/FAILURE
May 30 18:07:19 saga systemd[52014]: gsd-keyboard.service: Failed with result 'exit-code'.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Keyboard handling.
May 30 18:07:19 saga systemd[52014]: gsd-keyboard.service: Triggering OnFailure= dependencies.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Keyboard handling.
May 30 18:07:19 saga gnome-shell[56079]: (EE) failed to read Wayland events: Broken pipe
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Media keys handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Power management handling.
May 30 18:07:19 saga systemd[52014]: Started GNOME Session Failed lockdown screen (user).
May 30 18:07:19 saga systemd[52014]: Reached target GNOME Session Failed.
May 30 18:07:19 saga systemd[52014]: gsd-wacom.service: Main process exited, code=exited, status=1/FAILURE
May 30 18:07:19 saga systemd[52014]: gsd-wacom.service: Failed with result 'exit-code'.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Wacom handling.
May 30 18:07:19 saga systemd[52014]: gsd-power.service: Main process exited, code=exited, status=1/FAILURE
May 30 18:07:19 saga systemd[52014]: gsd-power.service: Failed with result 'exit-code'.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Power management handling.
May 30 18:07:19 saga systemd[52014]: gsd-power.service: Triggering OnFailure= dependencies.
May 30 18:07:19 saga gsd-xsettings[56416]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
May 30 18:07:19 saga gnome-session-failed[56603]: Unable to init server: Could not connect: Connection refused
May 30 18:07:19 saga gnome-session-f[56603]: Cannot open display: 
May 30 18:07:19 saga systemd[52014]: gnome-shell-wayland.service: Main process exited, code=dumped, status=11/SEGV
May 30 18:07:19 saga systemd[52014]: gsd-color.service: Main process exited, code=exited, status=1/FAILURE
May 30 18:07:19 saga systemd[52014]: gsd-color.service: Failed with result 'exit-code'.
May 30 18:07:19 saga systemd[52014]: gsd-xsettings.service: Main process exited, code=exited, status=1/FAILURE
May 30 18:07:19 saga systemd[52014]: gsd-xsettings.service: Failed with result 'exit-code'.
May 30 18:07:19 saga systemd[52014]: gsd-xsettings.service: Triggering OnFailure= dependencies.
May 30 18:07:19 saga systemd[52014]: gnome-session-failed.service: Main process exited, code=exited, status=1/FAILURE
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Session Failed.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Color management.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Wayland Session (session: gnome).
May 30 18:07:19 saga systemd[52014]: Stopped target Current graphical user session.
May 30 18:07:19 saga systemd[52014]: unicast-local-avahi.path: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped Path trigger for Avahi .local domain notifications.
May 30 18:07:19 saga systemd[52014]: update-notifier-crash.path: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped Path trigger for Apport crash notifications.
May 30 18:07:19 saga systemd[52014]: update-notifier-release.path: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped Path trigger for new release of Ubuntu notifications.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Session.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Wayland Session.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Session (session: gnome).
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Accessibility settings.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Date & Time handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Maintenance of expirable data.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Printer notifications.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME RFKill handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Freedesktop screensaver handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Sharing handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Smartcard handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME Sound sample caching handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME USB protection handling.
May 30 18:07:19 saga systemd[52014]: Stopped target GNOME WWan management.
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Accessibility settings...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Date & Time handling...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Maintenance of expirable data...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Printer notifications...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME RFKill handling...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Freedesktop screensaver handling...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Sharing handling...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Smartcard handling...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME Sound sample caching handling...
May 30 18:07:19 saga systemd[52014]: Stopping GNOME USB protection handling...
May 30 18:07:19 saga kernel: [ 8425.046133] rfkill: input handler enabled
May 30 18:07:19 saga systemd[52014]: Stopping GNOME WWan management...
May 30 18:07:19 saga systemd[52014]: gnome-session-failed.service: Failed with result 'exit-code'.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Session Failed lockdown screen (user).
May 30 18:07:19 saga systemd[52014]: gnome-session-failed.service: Triggering OnFailure= dependencies.
May 30 18:07:19 saga systemd[52014]: gsd-a11y-settings.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Accessibility settings.
May 30 18:07:19 saga systemd[52014]: gsd-smartcard.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Smartcard handling.
May 30 18:07:19 saga systemd[52014]: gsd-datetime.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Date & Time handling.
May 30 18:07:19 saga systemd[52014]: gsd-print-notifications.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Printer notifications.
May 30 18:07:19 saga systemd[52014]: gsd-rfkill.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME RFKill handling.
May 30 18:07:19 saga systemd[52014]: gsd-screensaver-proxy.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Freedesktop screensaver handling.
May 30 18:07:19 saga systemd[52014]: gsd-sharing.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Sharing handling.
May 30 18:07:19 saga systemd[52014]: gsd-usb-protection.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME USB protection handling.
May 30 18:07:19 saga systemd[52014]: gsd-wwan.service: Succeeded.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME WWan management.
May 30 18:07:19 saga systemd[52014]: gnome-shell-wayland.service: Failed with result 'core-dump'.
May 30 18:07:19 saga systemd[52014]: Stopped GNOME Shell on Wayland.

@ghost
Copy link

ghost commented Jun 1, 2020

This will probably help - home-sweet-gnome/dash-to-panel#976

@VariableDeclared
Copy link

Happens to me on Ubuntu 20.04 LTS with gnome 3.36.2.
Was working fine on 19.10 with kernel 5.3.*

So I am unable to use my favourite gnome extension

syslog:

May 22 15:26:45 FX705GD kernel: [  312.903435] gnome-shell[6154]: segfault at 0 ip 00007f87d5e5c252 sp 00007ffc7a0e9280 error 4 in libst-1.0.so[7f87d5e3c000+4c000]
May 22 15:26:45 FX705GD kernel: [  312.903440] Code: 48 83 c3 01 41 39 9f 30 01 00 00 0f 8e 27 01 00 00 49 8b 87 28 01 00 00 48 8d 35 ee 07 03 00 48 8b 2c d8 48 8b 45 00 48 8b 00 <4c> 8b 20 4c 89 e7 e8 63 31 fe ff 85 c0 74 c7 41 80 7c 24 0a 00 0f
May 22 15:26:45 FX705GD systemd[4344]: gnome-shell-x11.service: Main process exited, code=dumped, status=11/SEGV
May 22 15:26:45 FX705GD systemd[4344]: gnome-shell-x11.service: Failed with result 'core-dump'.
May 22 15:26:45 FX705GD systemd[4344]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 4.
May 22 15:26:45 FX705GD systemd[4344]: Stopped target GNOME X11 Session (session: ubuntu).
May 22 15:26:45 FX705GD systemd[4344]: Stopping GNOME X11 Session (session: ubuntu).
May 22 15:26:45 FX705GD systemd[4344]: Stopped target GNOME X11 Session.
May 22 15:26:45 FX705GD systemd[4344]: Stopping GNOME X11 Session.
May 22 15:26:45 FX705GD systemd[4344]: Stopped target GNOME Shell on X11.
May 22 15:26:45 FX705GD systemd[4344]: Stopping GNOME Shell on X11.
May 22 15:26:45 FX705GD systemd[4344]: Stopped GNOME Shell on X11.
May 22 15:26:45 FX705GD systemd[4344]: Starting GNOME Shell on X11...

Also seeing this in 20.04

@SlimDeluxe
Copy link

More info from my part:

  1. I was wrong - it's not limited to using the Workspace indicator extension.
  2. My Ubuntu 20.04 was upgraded from 19.10.
  3. I was trying out kernel 5.4 on 19.10 while searching for my laptop keyboard backlight fix and one of the problems I had with it was this exact same locking problem, so I had to revert to 5.3.

@Fmstrat
Copy link

Fmstrat commented Jun 18, 2020 •
edited
Loading

If it is helpful, I have one machine that works, and one that doesn't. Here is a package diff of GNOME packages. Both are running version 37 of Dash to Panel.

Everything works fine in <, but the crash occurs in >.

< gnome-control-center-data/focal,focal,now 1:3.36.1-1ubuntu5 all [installed,upgradable to: 1:3.36.2-0ubuntu1]
< gnome-control-center-faces/focal,focal,now 1:3.36.1-1ubuntu5 all [installed,upgradable to: 1:3.36.2-0ubuntu1]
< gnome-control-center/focal,now 1:3.36.1-1ubuntu5 amd64 [installed,upgradable to: 1:3.36.2-0ubuntu1]
< gnome-desktop3-data/focal,focal,now 3.36.1-1ubuntu1 all [installed,upgradable to: 3.36.2-0ubuntu2]
---
> gnome-control-center-data/focal-updates,focal-updates,now 1:3.36.2-0ubuntu1 all [installed,automatic]
> gnome-control-center-faces/focal-updates,focal-updates,now 1:3.36.2-0ubuntu1 all [installed,automatic]
> gnome-control-center/focal-updates,now 1:3.36.2-0ubuntu1 amd64 [installed,automatic]
> gnome-desktop3-data/focal-updates,focal-updates,now 3.36.2-0ubuntu2 all [installed,automatic]
401c403
< gnome-initial-setup/focal,now 3.36.1-1ubuntu1 amd64 [installed,upgradable to: 3.36.2-0ubuntu1]
---
> gnome-initial-setup/focal-updates,now 3.36.2-0ubuntu1 amd64 [installed,automatic]
404c406
< gnome-logs/focal,now 3.34.0-1 amd64 [installed,upgradable to: 3.34.0-1ubuntu1]
---
> gnome-logs/focal-updates,now 3.34.0-1ubuntu1 amd64 [installed,automatic]
414,416c416,418
< gnome-settings-daemon-common/focal,focal,now 3.36.0-1ubuntu2 all [installed,upgradable to: 3.36.1-0ubuntu1]
< gnome-settings-daemon/focal,now 3.36.0-1ubuntu2 amd64 [installed,upgradable to: 3.36.1-0ubuntu1]
< gnome-shell-common/focal,focal,now 3.36.1-5ubuntu1 all [installed,upgradable to: 3.36.2-1ubuntu1~20.04.1]
---
> gnome-settings-daemon-common/focal-updates,focal-updates,now 3.36.1-0ubuntu1 all [installed,automatic]
> gnome-settings-daemon/focal-updates,now 3.36.1-0ubuntu1 amd64 [installed,automatic]
> gnome-shell-common/focal-updates,focal-updates,now 3.36.2-1ubuntu1~20.04.1 all [installed,automatic]
418,420c420,422
< gnome-shell-extension-desktop-icons/focal,focal,now 20.04.0-1 all [installed,upgradable to: 20.04.0-2~ubuntu20.04.1]
< gnome-shell-extension-prefs/focal,now 3.36.1-5ubuntu1 amd64 [installed,upgradable to: 3.36.2-1ubuntu1~20.04.1]
< gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 all [installed,upgradable to: 68ubuntu1~20.04.1]
---
> gnome-shell-extension-desktop-icons/focal-updates,focal-updates,now 20.04.0-2~ubuntu20.04.1 all [installed,automatic]
> gnome-shell-extension-prefs/focal-updates,now 3.36.2-1ubuntu1~20.04.1 amd64 [installed,automatic]
> gnome-shell-extension-ubuntu-dock/focal-updates,focal-updates,now 68ubuntu1~20.04.1 all [installed,automatic]
422c424
< gnome-shell/focal,now 3.36.1-5ubuntu1 amd64 [installed,upgradable to: 3.36.2-1ubuntu1~20.04.1]
---
> gnome-shell/focal-updates,now 3.36.2-1ubuntu1~20.04.1 amd64 [installed,automatic]

@Fmstrat
Copy link

Fmstrat commented Jun 20, 2020

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2917

@SlimDeluxe
Copy link

gnome-shell updated to 3.36.3 a few days ago and I have not seen the problem since. Possibly fixed :)

@VariableDeclared
Copy link

gnome-shell updated to 3.36.3 a few days ago and I have not seen the problem since. Possibly fixed :)

Confirmed working now on Ubuntu 20.04 :)

@coralof coralof mentioned this issue Mar 29, 2021
Closed
@3v1n0 3v1n0 closed this as completed Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests