Re: gdm3 stalled
I tryed to start gdm in Automatic Login mode (adding AutomaticLoginEnable=true AutomaticLogin=user in /etc/gdm/custom.conf ) and in that way gnome start with gdm without any problem and system is fluid. Indeed, a related problem was keybord shortcuts delayed on gnome which I normally (no AutoLogin) can start only after gdm disabling. Why? Could you help me to look into? I need gdm with several user and so I'm just partially solved. Thanks. Il 02/09/23 13:38, Zener ha scritto: After an upgrade several months ago, gdm3 get stalled at each boot and gnome can't run properly. So, I've disabled gdm.service and gnome start properly without gdm. All the upgrade system in these months have not been able to solve. Could you help me to do an useful debug in order to solve? Thanks.
Re: gdm3 stalled
Hi. What's /usr/share/gdm/gdm.schemas? I read it cannot found it! How can solve? set 05 09:13:51 ArchLinux systemd[1]: Starting GNOME Display Manager... set 05 09:13:51 ArchLinux gdm[763]: Gdm: Unable to read schemas file: Apertura del file «/usr/share/gdm/gdm.schemas» non riuscita: File o directory non esistente set 05 09:13:51 ArchLinux gdm[763]: Gdm: Unable to parse schemas set 05 09:13:51 ArchLinux gdm[763]: Gdm: Unable to initialize settings set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Failed with result 'exit-code'. set 05 09:13:51 ArchLinux systemd[1]: Failed to start GNOME Display Manager. set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Triggering OnFailure= dependencies. set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found. set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Scheduled restart job, restart counter is at 5. set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Start request repeated too quickly. set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Failed with result 'exit-code'. set 05 09:13:51 ArchLinux systemd[1]: Failed to start GNOME Display Manager. set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Triggering OnFailure= dependencies. set 05 09:13:51 ArchLinux systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found. Il 06/09/23 21:25, Ralf Mardorf ha scritto: On Sat, 2023-09-02 at 15:13 +0200, Zener wrote: /var/log/gdm is empty , why? Anyway, I use Wayland. Hi, I know, you posted the journal mentioning Wayland. On Wed, 2023-09-06 at 20:06 +0200, Zener wrote: drwx--x--x 1 root gdm0 1 mar 2023 gdm So in March an empty gdm log directory was created? If nobody fromm the mailing list can help, try the Arch forums and/or Upstream. Regards, Ralf
Re: gdm3 stalled
On Sat, 2023-09-02 at 15:13 +0200, Zener wrote: > /var/log/gdm is empty , why? > > Anyway, I use Wayland. Hi, I know, you posted the journal mentioning Wayland. On Wed, 2023-09-06 at 20:06 +0200, Zener wrote: > drwx--x--x 1 root gdm0 1 mar 2023 gdm So in March an empty gdm log directory was created? If nobody fromm the mailing list can help, try the Arch forums and/or Upstream. Regards, Ralf
Re: gdm3 stalled
"If GDM is failing to work properly, it is always a good idea to include debug information. To enable debugging, set the debug/Enable key to "true" in the /gdm/custom.conf file and restart GDM. Then use GDM to the point where it fails, and debug output will be sent to the system log file (/log/messages or /adm/messages depending on your Operating System)." - https://help.gnome.org/admin/gdm/stable/troubleshooting.html.en
Re: gdm3 stalled
Hi, maybe "systemd-analyze blame" shows that a running unit that is expected to start within a few ms actually took several s to initialize. systemd-analyze blame | grep -v "ms " it "gives an impression of the performance of program code, but cannot accurately reflect latency introduced by waiting for hardware and similar events." Regards, Ralf
Re: gdm3 stalled
I'm no expert on gdm startup, but after reviewing the journal entries, nothing immediately jumps out. The only gaps in startup are likely just due to other parts of gnome or the system starting at that time. For what it is worth, the following were the only two delays in startup that caught my eye. On 9/5/23 03:23, Zener wrote: set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmCommon: Found session 1 for PID 794, using set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: display status changed: 2 (27 second delay - may be normal) set 05 10:09:08 ArchLinux gdm[729]: Gdm: GdmCommon: Found session 1 for PID 811, using set 05 10:09:08 ArchLinux gdm[729]: Gdm: GdmManager: trying to register new session on display 0x55b47c22b980 set 05 10:09:08 ArchLinux gdm[729]: Gdm: GdmDisplay: session registered: yes set 05 10:09:08 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: session registered on display, looking for any background displays to kill (15 second delay - may be normal) set 05 10:09:23 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: received VT change event set 05 10:09:23 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: VT changed from 1 to 2 set 05 10:09:23 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: VT of login window is 1 set 05 10:09:23 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: VT switched from login window set 05 10:09:23 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: killing login window once its unused set 05 10:09:23 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: display status changed: 3 set 05 10:09:23 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: active VT is not initial VT, so ignoring (this last entry doesn't make a lot of sense to me, you have VT originally on 1, it changes to 2, the login window is on 1 and then the login window is killed - like you have auto-login or something, an finally the "active VT is not initial VT, so ignoring" is odd looking, but may be 100% normal -- it's gnome after all...) Others will have to chime in with more specifics if they see anything, but from the journal snippets posted, your problem seems to be elsewhere. -- David C. Rankin, J.D.,P.E.
Re: gdm3 stalled
I share below "journalctl -u gdm" output of last boot. I hope it can be helpful to understand the issue. Thanks. -- Boot 862f63cdcc5a4e3c9912a16d1cf4cdfc -- set 05 10:08:41 ArchLinux systemd[1]: Starting GNOME Display Manager... set 05 10:08:41 ArchLinux systemd[1]: Started GNOME Display Manager. set 05 10:08:41 ArchLinux gdm[729]: Gdm: Enabling debugging set 05 10:08:41 ArchLinux gdm[729]: Gdm: Changing user:group to gdm:gdm set 05 10:08:41 ArchLinux gdm[729]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3) set 05 10:08:41 ArchLinux gdm[729]: Gdm: Successfully connected to D-Bus set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmManager: GDM starting to manage displays set 05 10:08:41 ArchLinux gdm[729]: Gdm: Could not ping plymouth: Esecuzione del processo figlio «plymouth» non riuscita (File o directory non esistente) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: enumerating seats from logind set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: display for seat seat0 requested set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: Checking if udev has settled enough to support graphics. set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: Found primary PCI graphics adapter, proceeding. set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: udev has settled enough for graphics. set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: System supports graphics set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: Getting session type (prefers wayland, falling back: no) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: New displays on seat0 will use wayland set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: wayland login display for seat seat0 requested set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLocalDisplayFactory: Adding display on seat seat0 set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: id: (null) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: seat id: (null) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: session class: greeter set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: initial: no set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: allow timed login: yes set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: local: yes set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: supported session types: (null) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: session type: wayland set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: supported session types: wayland:x11 set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: seat id: seat0 set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: initial: yes set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplayStore: Adding display /org/gnome/DisplayManager/Displays/94233665124736 to store set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: Managing display: /org/gnome/DisplayManager/Displays/94233665124736 set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: Preparing display: /org/gnome/DisplayManager/Displays/94233665124736 set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: Checking kernel command buffer BOOT_IMAGE=/vmlinuz-linux root=UUID=268ca439-a0f8-4522-a90a-1ef31d8560a4 rw loglevel=3 resume=/dev/nvme0n1p6 set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: Failed to read kernel commandline: Could not match gnome.initial-setup= in kernel cmdline set 05 10:08:41 ArchLinux gdm[729]: Gdm: doing initial setup? no set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: prepare display set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: Got automatic login details for display: 0 set 05 10:08:41 ArchLinux gdm[729]: GdmDBusUtils: Registered DBus error domain 'gdm-session-worker-error-quark' set 05 10:08:41 ArchLinux gdm[729]: GLib: setenv()/putenv() are not thread-safe and should not be used after threads are created set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmSession: Creating D-Bus server for worker for session set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmSession: D-Bus server for workers listening on unix:path=/tmp/dbus-fkgv1tkJ set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmSession: Creating D-Bus server for greeters and such for session (null) (0x55b47c240210) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmSession: D-Bus server for greeters listening on unix:path=/tmp/dbus-onS0JSXP set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmSession: Setting display device: (null) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmSession: Created user session for user 120 on display /org/gnome/DisplayManager/Displays/94233665124736 (seat seat0) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: Running greeter set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmDisplay: Creating greeter for (null) (null) set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLaunchEnvironment: Starting... set 05 10:08:41 ArchLinux gdm[729]: Gdm: GdmLaunchEnvironment: Setting up run time dir
Re: gdm3 stalled
/var/log/gdm is empty , why? Anyway, I use Wayland. Regards. Il 02/09/23 13:51, Ralf Mardorf ha scritto: On Sat, 2023-09-02 at 13:38 +0200, Zener wrote: [snip] gdm3 get stalled at each boot [snip] Could you help me to do an useful debug in order to solve? Hi, aren't there gdm3 related log files in /var/log? For lightdm I get several log files, for lightdm itself, for its greeter and other. I would take a look at those files + the related Arch Wiki first and if needed continue with Xorg.0.log, journalctl ... https://wiki.archlinux.org/title/GDM#Troubleshooting Regards, Ralf
Re: gdm3 stalled
On Sat, 2023-09-02 at 13:38 +0200, Zener wrote: > [snip] gdm3 get stalled at each boot [snip] > Could you help me to do an useful debug in order to solve? Hi, aren't there gdm3 related log files in /var/log? For lightdm I get several log files, for lightdm itself, for its greeter and other. I would take a look at those files + the related Arch Wiki first and if needed continue with Xorg.0.log, journalctl ... https://wiki.archlinux.org/title/GDM#Troubleshooting Regards, Ralf
