Re: gdm3 stalled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



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.




[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux