dash-to-dock from software crash the whole session in Bionic

Bug #1737412 reported by Christophe C
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell-extension-dashtodock (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

If i install dash-to-dock from the repo in bionic (sudo apt install gnome-shell-extension-dashtodock), the gnome-shell session crash (under xorg or wayland) => return to the connexion screen.

Installation of the extension from https://extensions.gnome.org/ work perfectly.

Others users on the ubuntu french forum have the same problem.

Tags: bionic
tags: added: bionic
Revision history for this message
dino99 (9d9) wrote :

I use that extension since a while now, and have not met instability. so that extension might not be blamed.

For testing purpose, unset all the installed extensions, via tweaks, then logout/in, and set back the extension one by one to find which one is conflicting.

I suppose you have already made some system cleaning using gtkorphan & bleachbit (as root, but select carefully the options).
A week back or so, some users have pointed a possible gjs cause; and we still wait for an upgrade.
Some others also have suggested to not install dash-to-panel and dashtodock together. (myself not using dash-to-panel)

Changed in gnome-shell-extension-dashtodock (Ubuntu):
status: New → Incomplete
Revision history for this message
dino99 (9d9) wrote :

Also joint the crash file to get a chance to identify the cause (or any message logged into journalctl.

Revision history for this message
Christophe C (batra3) wrote :
Download full text (7.2 KiB)

fresh install bionic today
No extensions
sudo apt update && sudo apt full-upgrade
sudo apt install gnome-shell-extension-dashtodock
deconnexion from the session
impossible to reconnect the session : the screen freeze during few seconds, then return to the connexion screen
ctrl+alt+F2 : sudo apt purge gnome-shell-extension-dashtodock
Able to reconnect => problem solved

It exist a duplicate bug here : https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1720547

journalctl (extract)
janv. 03 20:56:10 chris-desktop systemd[895]: pam_unix(systemd-user:session): session closed for user chris
janv. 03 20:56:10 chris-desktop systemd[1]: Stopped User Manager for UID 1000.
janv. 03 20:56:10 chris-desktop systemd[1]: Removed slice User Slice of chris.
janv. 03 20:56:10 chris-desktop dbus-daemon[1723]: [session uid=121 pid=1723] Activating service name='org.gnome.ScreenSaver' requested by ':1.12' (uid=121 pid=1725 comm="/usr/
janv. 03 20:56:10 chris-desktop org.gnome.ScreenSaver[1723]: Unable to init server: Impossible de se connecter : Connexion refusée
janv. 03 20:56:10 chris-desktop gnome-screensav[1731]: Impossible d'ouvrir l'affichage :
janv. 03 20:56:10 chris-desktop dbus-daemon[1723]: [session uid=121 pid=1723] Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status
janv. 03 20:56:10 chris-desktop gnome-session[1725]: gnome-session-binary[1725]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de StartSe
janv. 03 20:56:10 chris-desktop gnome-session-binary[1725]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Erreur lors de l’appel de StartServiceByName pour org.
janv. 03 20:56:11 chris-desktop org.gnome.Shell.desktop[1733]: glamor: EGL version 1.4 (DRI2):
janv. 03 20:56:11 chris-desktop dbus-daemon[1723]: [session uid=121 pid=1723] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':
janv. 03 20:56:11 chris-desktop systemd[1714]: Starting Accessibility services bus...
janv. 03 20:56:11 chris-desktop dbus-daemon[1723]: [session uid=121 pid=1723] Successfully activated service 'org.a11y.Bus'
janv. 03 20:56:11 chris-desktop systemd[1714]: Started Accessibility services bus.
janv. 03 20:56:11 chris-desktop at-spi-bus-launcher[1747]: dbus-daemon[1752]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=121 pid=1733 comm="/usr
janv. 03 20:56:11 chris-desktop at-spi-bus-launcher[1747]: dbus-daemon[1752]: Successfully activated service 'org.a11y.atspi.Registry'
janv. 03 20:56:11 chris-desktop at-spi-bus-launcher[1747]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
janv. 03 20:56:11 chris-desktop systemd[1714]: Starting Sound Service...
janv. 03 20:56:11 chris-desktop rtkit-daemon[1035]: Supervising 0 threads of 0 processes of 1 users.
janv. 03 20:56:11 chris-desktop rtkit-daemon[1035]: Supervising 0 threads of 0 processes of 1 users.
janv. 03 20:56:11 chris-desktop rtkit-daemon[1035]: Supervising 0 threads of 0 processes of 1 users.
janv. 03 20:56:11 chris-desktop rtkit-daemon[1035]: Supervising 0 threads of 0 processes of 1 users....

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell-extension-dashtodock (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell-extension-dashtodock (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.