gdm3 crash when switching users

Bug #1969516 reported by Hassan El Jacifi
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Hi Guys,

Exactly the same issue as bug #1945061

GDM still crash when switching user.

To reproduce the issue:

Login as user A, keep user A logged in and lock the screen. Try to switch to user B, enter the password and you got back to the user list (loop)

avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) NVIDIA(0): Setting mode "HDMI-1:2560x1440_120+2560+0{ForceCompositionPipeline=On,ForceFullCompositionPipeline=On},DP-0:2560x1440_120+0+0{ForceCompositionPipeline=On,ForceFullCompositionPipeline=On}"
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event2 - Power Button: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event2 - Power Button: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:64
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event0 - Sleep Button: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event0 - Sleep Button: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:71
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event7 - Eee PC WMI hotkeys: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event7 - Eee PC WMI hotkeys: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:70
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event6 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Keyboard: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event6 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Keyboard: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:65
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event1 - Power Button: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event1 - Power Button: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:77
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event13 - Razer Razer Viper Mini: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event13 - Razer Razer Viper Mini: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:69
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event5 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) System Control: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event5 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) System Control: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:74
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event10 - Razer Razer Viper Mini: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event10 - Razer Razer Viper Mini: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:68
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event4 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Consumer Control: is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event4 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB) Consumer Control: device is a keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:72
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event8 - Razer Razer Viper Mini: is tagged by udev as: Mouse
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event8 - Razer Razer Viper Mini: device is a pointer
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) systemd-logind: got resume for 13:67
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event3 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB): is tagged by udev as: Keyboard
avr 19 20:12:25 Jupiter /usr/libexec/gdm-x-session[2478]: (II) event3 - Cooler Master Technology Inc. MasterKeys Lite L Combo Keyboard(KB): device is a keyboard
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: not releasing fd for 13:74, still in use
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: not releasing fd for 13:68, still in use
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:71
avr 19 20:12:36 Jupiter gsd-color[2775]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Samsung_Electric_Company_LC49G95T_H4ZR200280_gdm_120
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:77
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:74
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:72
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:70
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:69
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:68
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:67
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:64
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:65
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) UnloadModule: "libinput"
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) systemd-logind: releasing fd for 13:66
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) NVIDIA(GPU-0): Deleting GPU-0
avr 19 20:12:36 Jupiter /usr/libexec/gdm-x-session[4351]: (II) Server terminated successfully (0). Closing log file.
avr 19 20:12:36 Jupiter gdm-launch-environment][4343]: pam_unix(gdm-launch-environment:session): session closed for user gdm
avr 19 20:12:36 Jupiter gdm-launch-environment][4343]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
avr 19 20:12:36 Jupiter gdm3[1801]: Gdm: Child process -4349 was already dead.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu6
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Apr 19 20:13:06 2022
InstallationDate: Installed on 2018-01-01 (1569 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
SourcePackage: gdm3
UpgradeStatus: Upgraded to jammy on 2022-04-06 (13 days ago)
mtime.conffile..etc.gdm3.custom.conf: 2018-11-01T14:01:52.647430

Revision history for this message
Hassan El Jacifi (waver) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gdm3 (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

In order to confirm this is the same issue as bug 1945061 we will need a stack trace so...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

Changed in gdm3 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Hassan El Jacifi (waver) wrote (last edit ):
Download full text (8.4 KiB)

Hi Daniel,

No crash file was generated. It's simply fail to login as a second user if the first session is still open.

I can only provide logs if you need them.

Apr 20 15:19:59 Jupiter gsd-color[26758]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Samsung_Electric_Company_LC49G95T_H4ZR200280_gdm_120
Apr 20 15:20:00 Jupiter gdm-launch-environment]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Apr 20 15:20:00 Jupiter gdm3: Gdm: Child process -16722 was already dead.
Apr 20 15:20:54 Jupiter gdm3: GLib-GObject: g_object_set_is_valid_property: object class 'GdmLocalDisplay' has no property named 'supported-session-tyes'
Apr 20 15:20:55 Jupiter systemd[1]: Started Session c5 of User gdm.
Apr 20 15:20:56 Jupiter org.gnome.Shell.desktop[29533]: Window manager warning: Failed to parse saved session file: L’ouverture du fichier « /var/lib/gdm3/.config/mutter/sessions/10edbd1855b7ffec6f165046085575987900000295180000.ms » a échoué : Aucun fichier ou dossier de ce type
Apr 20 15:21:03 Jupiter gdm3: Gdm: GdmDisplay: Session never registered, failing
Apr 20 15:21:11 Jupiter gdm3: GLib: Source ID 229 was not found when attempting to remove it
Apr 20 15:21:22 Jupiter gsd-color[26758]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_Samsung_Electric_Company_LC49G95T_H4ZR200280_gdm_120
Apr 20 15:21:22 Jupiter gdm-launch-environment]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Apr 20 15:21:22 Jupiter gdm3: Gdm: Child process -29500 was already dead.

● gdm.service - GNOME Display Manager
     Loaded: loaded (/lib/systemd/system/gdm.service; static)
     Active: active (running) since Wed 2022-04-20 15:38:25 CEST; 15min ago
    Process: 1753 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
   Main PID: 1789 (gdm3)
      Tasks: 3 (limit: 38360)
     Memory: 6.8M
        CPU: 315ms
     CGroup: /system.slice/gdm.service
             └─1789 /usr/sbin/gdm3

avr 20 15:47:58 Jupiter gdm-password][5233]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
avr 20 15:47:59 Jupiter gdm-password][5233]: pam_unix(gdm-password:session): session closed for user XX
avr 20 15:47:59 Jupiter gdm3[1789]: Gdm: GdmDisplay: Session never registered, failing
avr 20 15:49:07 Jupiter gdm-password][5515]: gkr-pam: unable to locate daemon control file
avr 20 15:49:07 Jupiter gdm-password][5515]: gkr-pam: stashed password to try later in open session
avr 20 15:49:07 Jupiter gdm-password][5515]: pam_unix(gdm-password:session): session opened for user XX(uid=1001) by (uid=0)
avr 20 15:49:07 Jupiter gdm-password][5515]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
avr 20 15:49:08 Jupiter gdm-password][5515]: pam_unix(gdm-password:session): session closed for user XX
avr 20 15:49:08 Jupiter gdm3[1789]: Gdm: GdmDisplay: Session never registered, failing
avr 20 15:50:16 Jupiter gdm3[1789]: Gdm: Child process -4988 was already dead.

avr 20 16:04:19 Jupiter gdm3[1789]: GLib-GObject: g_object_set_is_valid_property: object class 'GdmLocalDisplay' ...

Read more...

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

[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]

Changed in gdm3 (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.