** Description changed: + [SRU] 2.74.1: + https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2138629 + + [ Impact ] + + Upgrading gnome-session causes an abortion due to the fact that the + graphical session has been already started + + [ Test Plan ] + + 1. Reproduce with snapd deb 2.74 + + - Upgrading gnome-session + - Confirm this causes an abort and "A graphical session is already running!" + + + 2. Prove fixed with snapd deb 2.74.1 + + - Upgrading gnome-session + - Confirm this does not cause an abort. + - Remove snapd-desktop-integration and prompting-client snaps and reinstall and ensure all is still working. + + + This test run against all targeted Ubuntu releases. + + + ---original--- + Upgrading gnome-session to 50 causes an abortion due to the fact that the graphical session has been already started: - feb 11 21:30:15 resolute gnome-session-i[1755]: A graphical session is already running! Full log https://paste.ubuntu.com/p/tQsH99bpyX/ Removing snapd-desktop-integration and prompting-client snaps, the GDM session is able to start. Installing them again, will crash the session: feb 12 00:08:07 resolute gdm-authd][3856]: gkr-pam: stashed password to try later in open session feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): pam-systemd: initializing... feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Automatically chose session class 'user'. feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Asking logind to create session: uid=1000 pid=3856 service=gdm-authd type=wayland class=user desktop= seat=seat0 vtnr=2 tty=tty2 display= remote=no remote_user= remote_host= feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a feb 12 00:08:07 resolute systemd-logind[1357]: New session '4' of user 'marco' with class 'user' and type 'wayland'. feb 12 00:08:07 resolute snapd-desktop-i[3795]: Detected new session 4 at /org/freedesktop/login1/session/_34 feb 12 00:08:07 resolute snapd-desktop-i[3795]: The new session is of desktop type. Relaunching snapd-desktop-integration. feb 12 00:08:07 resolute snapd-desktop-i[3795]: Loop exited. Forcing reload. feb 12 00:08:07 resolute systemd[1]: Started session-4.scope - Session 4 of User marco. feb 12 00:08:07 resolute systemd[3569]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 572ms CPU time over 41.191s wall clock time, 75.1M memory peak. feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Reply from logind: id=4 object_path=n/a runtime_path=/run/user/1000 seat=seat0 vtnr=2 original_uid=1000 feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Failed to read credential 'shell.prompt.prefix', ignoring: Device o indirizzo non esistente feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Failed to read credential 'shell.prompt.suffix', ignoring: Device o indirizzo non esistente feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Failed to read credential 'shell.welcome', ignoring: Device o indirizzo non esistente feb 12 00:08:07 resolute gdm-authd][3856]: pam_unix(gdm-authd:session): session opened for user marco(uid=1000) by marco(uid=0) feb 12 00:08:07 resolute systemd[3569]: Started gnome-keyring-daemon.service - GNOME Keyring daemon. feb 12 00:08:07 resolute gnome-keyring-daemon[4119]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring feb 12 00:08:07 resolute gdm-authd][3856]: gkr-pam: unlocked login keyring feb 12 00:08:07 resolute kernel: rfkill: input handler enabled feb 12 00:08:07 resolute spice-vdagentd[3446]: closed vdagent virtio channel feb 12 00:08:08 resolute systemd[3569]: Reached target sound.target - Sound Card. feb 12 00:08:08 resolute gsd-media-keys[2168]: Unable to get default source feb 12 00:08:08 resolute gsd-media-keys[2168]: Unable to get default sink feb 12 00:08:08 resolute systemd[1659]: Reached target sound.target - Sound Card. feb 12 00:08:08 resolute gnome-shell[1857]: JS ERROR: TypeError: this._input._stream is null _updatePrivacyIndicator@resource:///org/gnome/shell/ui/status/volume.js:538:27 InputIndicator/<@resource:///org/gnome/shell/ui/status/volume.js:524:18 set stream@resource:///org/gnome/shell/ui/status/volume.js:104:18 _readInput@resource:///org/gnome/shell/ui/status/volume.js:551:44 InputIndicator/<@resource:///org/gnome/shell/ui/status/volume.js:515:50 @resource:///org/gnome/shell/ui/init.js:20:20 feb 12 00:08:08 resolute wireplumber[3627]: spa.bluez5: BlueZ system service is not available feb 12 00:08:08 resolute gnome-session-i[4194]: A graphical session is already running! feb 12 00:08:08 resolute systemd-coredump[4268]: Process 4194 (gnome-session-i) of user 1000 terminated abnormally with signal 6/ABRT, processing... feb 12 00:08:08 resolute systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump. feb 12 00:08:08 resolute systemd[1]: Started systemd-coredump@0-1-4268_4269-0.service - Process Core Dump (PID 4268/UID 0). feb 12 00:08:08 resolute systemd-coredump[4269]: [🡕] Process 4194 (gnome-session-i) of user 1000 dumped core. --- I can then only login again if I do (from SSH) systemctl --user stop graphical-session.target sudo sed "s,BindsTo,PartOf," -i /etc/xdg/systemd/user/snap.snapd-desktop-integration.snapd-desktop-integration.service systemctl --user daemon-reload And then the login works again --- See: https://github.com/canonical/snapd/pull/16586
** Description changed: [SRU] 2.74.1: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2138629 [ Impact ] Upgrading gnome-session causes an abortion due to the fact that the graphical session has been already started + This is a regression in 2.74 that was only released for Resolute, so it + only need to be verified for Resolute. + [ Test Plan ] 1. Reproduce with snapd deb 2.74 - - Upgrading gnome-session - - Confirm this causes an abort and "A graphical session is already running!" - + - Upgrading gnome-session + - Confirm this causes an abort and "A graphical session is already running!" 2. Prove fixed with snapd deb 2.74.1 - - Upgrading gnome-session - - Confirm this does not cause an abort. - - Remove snapd-desktop-integration and prompting-client snaps and reinstall and ensure all is still working. - + - Upgrading gnome-session + - Confirm this does not cause an abort. + - Remove snapd-desktop-integration and prompting-client snaps and reinstall and ensure all is still working. This test run against all targeted Ubuntu releases. - ---original--- Upgrading gnome-session to 50 causes an abortion due to the fact that the graphical session has been already started: - feb 11 21:30:15 resolute gnome-session-i[1755]: A graphical session is already running! Full log https://paste.ubuntu.com/p/tQsH99bpyX/ Removing snapd-desktop-integration and prompting-client snaps, the GDM session is able to start. Installing them again, will crash the session: feb 12 00:08:07 resolute gdm-authd][3856]: gkr-pam: stashed password to try later in open session feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): pam-systemd: initializing... feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Automatically chose session class 'user'. feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Asking logind to create session: uid=1000 pid=3856 service=gdm-authd type=wayland class=user desktop= seat=seat0 vtnr=2 tty=tty2 display= remote=no remote_user= remote_host= feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Session limits: memory_max=n/a tasks_max=n/a cpu_weight=n/a io_weight=n/a runtime_max_sec=n/a feb 12 00:08:07 resolute systemd-logind[1357]: New session '4' of user 'marco' with class 'user' and type 'wayland'. feb 12 00:08:07 resolute snapd-desktop-i[3795]: Detected new session 4 at /org/freedesktop/login1/session/_34 feb 12 00:08:07 resolute snapd-desktop-i[3795]: The new session is of desktop type. Relaunching snapd-desktop-integration. feb 12 00:08:07 resolute snapd-desktop-i[3795]: Loop exited. Forcing reload. feb 12 00:08:07 resolute systemd[1]: Started session-4.scope - Session 4 of User marco. feb 12 00:08:07 resolute systemd[3569]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Consumed 572ms CPU time over 41.191s wall clock time, 75.1M memory peak. feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Reply from logind: id=4 object_path=n/a runtime_path=/run/user/1000 seat=seat0 vtnr=2 original_uid=1000 feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Failed to read credential 'shell.prompt.prefix', ignoring: Device o indirizzo non esistente feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Failed to read credential 'shell.prompt.suffix', ignoring: Device o indirizzo non esistente feb 12 00:08:07 resolute gdm-authd][3856]: pam_systemd(gdm-authd:session): Failed to read credential 'shell.welcome', ignoring: Device o indirizzo non esistente feb 12 00:08:07 resolute gdm-authd][3856]: pam_unix(gdm-authd:session): session opened for user marco(uid=1000) by marco(uid=0) feb 12 00:08:07 resolute systemd[3569]: Started gnome-keyring-daemon.service - GNOME Keyring daemon. feb 12 00:08:07 resolute gnome-keyring-daemon[4119]: GNOME_KEYRING_CONTROL=/run/user/1000/keyring feb 12 00:08:07 resolute gdm-authd][3856]: gkr-pam: unlocked login keyring feb 12 00:08:07 resolute kernel: rfkill: input handler enabled feb 12 00:08:07 resolute spice-vdagentd[3446]: closed vdagent virtio channel feb 12 00:08:08 resolute systemd[3569]: Reached target sound.target - Sound Card. feb 12 00:08:08 resolute gsd-media-keys[2168]: Unable to get default source feb 12 00:08:08 resolute gsd-media-keys[2168]: Unable to get default sink feb 12 00:08:08 resolute systemd[1659]: Reached target sound.target - Sound Card. feb 12 00:08:08 resolute gnome-shell[1857]: JS ERROR: TypeError: this._input._stream is null _updatePrivacyIndicator@resource:///org/gnome/shell/ui/status/volume.js:538:27 InputIndicator/<@resource:///org/gnome/shell/ui/status/volume.js:524:18 set stream@resource:///org/gnome/shell/ui/status/volume.js:104:18 _readInput@resource:///org/gnome/shell/ui/status/volume.js:551:44 InputIndicator/<@resource:///org/gnome/shell/ui/status/volume.js:515:50 @resource:///org/gnome/shell/ui/init.js:20:20 feb 12 00:08:08 resolute wireplumber[3627]: spa.bluez5: BlueZ system service is not available feb 12 00:08:08 resolute gnome-session-i[4194]: A graphical session is already running! feb 12 00:08:08 resolute systemd-coredump[4268]: Process 4194 (gnome-session-i) of user 1000 terminated abnormally with signal 6/ABRT, processing... feb 12 00:08:08 resolute systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump. feb 12 00:08:08 resolute systemd[1]: Started systemd-coredump@0-1-4268_4269-0.service - Process Core Dump (PID 4268/UID 0). feb 12 00:08:08 resolute systemd-coredump[4269]: [🡕] Process 4194 (gnome-session-i) of user 1000 dumped core. --- I can then only login again if I do (from SSH) systemctl --user stop graphical-session.target sudo sed "s,BindsTo,PartOf," -i /etc/xdg/systemd/user/snap.snapd-desktop-integration.snapd-desktop-integration.service systemctl --user daemon-reload And then the login works again --- See: https://github.com/canonical/snapd/pull/16586 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2141607 Title: snapd desktop daemons break gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2141607/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
