You are not logged in.

Pages: 1

#1 2024-04-10 06:00:44

hilom
Member
Registered: 2023-10-16
Posts: 19

Gnome freeze at login

I have noticed some strange behaviour of gnome that seem to have started with gnome 45, when i start my computer and sign in to gnome-shell via gdm i am getting a white prompt only, once this happens there is nothing i can do ( not even change tty ) other than press the power button to power off again. it seems to happen intermittently and some days it happens 3 -4 times in a row while other days not at all.

i can see the following in the log

apr 10 09:42:57 archlinux gnome-session-binary[1339]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.2105] dhcp4 (enp4s0): state changed new lease, address=192.168.88.147, acd pending
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.3932] dhcp4 (enp4s0): state changed new lease, address=192.168.88.147
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.3934] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
apr 10 09:42:59 archlinux /usr/lib/gdm-wayland-session[802]: dbus-daemon[802]: [session uid=120 pid=802] Activating service name='org.freedesktop.systemd1' requested by ':1.11' (uid=120 pid=924 comm="/usr/lib/gsd-sharing")
apr 10 09:42:59 archlinux /usr/lib/gdm-wayland-session[802]: dbus-daemon[802]: [session uid=120 pid=802] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
apr 10 09:42:59 archlinux gsd-sharing[924]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
apr 10 09:42:59 archlinux gsd-sharing[924]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
apr 10 09:42:59 archlinux avahi-daemon[685]: Joining mDNS multicast group on interface enp4s0.IPv4 with address 192.168.88.147.
apr 10 09:42:59 archlinux avahi-daemon[685]: New relevant interface enp4s0.IPv4 for mDNS.
apr 10 09:42:59 archlinux avahi-daemon[685]: Registering new address record for 192.168.88.147 on enp4s0.IPv4.
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.4030] device (enp4s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
apr 10 09:42:59 archlinux systemd[1]: Starting Network Manager Script Dispatcher Service...
apr 10 09:42:59 archlinux systemd[1]: Started Network Manager Script Dispatcher Service.
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.4440] device (enp4s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.4441] device (enp4s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.4442] manager: NetworkManager state is now CONNECTED_SITE
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.4443] device (enp4s0): Activation: successful, device activated.
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.4446] manager: startup complete
apr 10 09:42:59 archlinux NetworkManager[684]: <info>  [1712734979.5149] manager: NetworkManager state is now CONNECTED_GLOBAL
apr 10 09:43:01 archlinux systemd-logind[687]: Power key pressed short.
apr 10 09:43:01 archlinux systemd-logind[687]: Powering off...
apr 10 09:43:01 archlinux systemd-logind[687]: System is powering down.
apr 10 09:43:01 archlinux gnome-shell[815]: Shutting down GNOME Shell

my system: 

                `ooo/                    OS: Arch Linux x86_64
               `+oooo:                   Kernel: 6.8.4-arch1-1
              `+oooooo:                  Uptime: 10 mins
              -+oooooo+:                 Packages: 1451 (pacman)
            `/:-:++oooo+:                Shell: bash 5.2.26
           `/++++/+++++++:               Display (P27): 3840x2160 @ 60Hz (as 1920x1080)
          `/++++++++++++++:              Display (32G1WG4): 1920x1080 @ 144Hz
         `/+++ooooooooooooo/`            DE: Gnome 46.0
        ./ooosssso++osssssso+`           WM: Mutter (Wayland)
       .oossssso-````/ossssss+`          WM Theme: Flat-Remix-Blue-Darkest
      -osssssso.      :ssssssso.         Theme: Flat-Remix-GTK-Blue-Darkest-Solid [GTK2/3/4]
     :osssssss/        osssso+++.        Icons: Colloid-dark [GTK2/3/4]
    /ossssssss/        +ssssooo/-        Font: SF Pro Display Medium (12pt) [GTK2/3/4]
  `/ossssso+/:-        -:/+osssso+-      Cursor: Adwaita (24px)
 `+sso+:-`                 `.-/+oso:     Terminal: GNOME Terminal 3.52.0
`++:.                           `-/+/    Terminal Font: Cousine (13pt)
.`                                 `/    CPU: AMD Ryzen 9 5900X (24) @ 4,95 GHz
                                         GPU: NVIDIA GeForce RTX 3080 Ti
                                         Memory: 3,11 GiB / 31,25 GiB (10%)
                                         Swap: 0 B / 64,00 GiB (0%)
                                         Disk (/): 29,87 GiB / 97,87 GiB (31%) - ext4
                                         Disk (/home): 112,98 GiB / 146,59 GiB (77%) - ext4
                                         Local IP (enp4s0): 192.168.88.147/24 *
                                         Locale: en_US.UTF-8

Offline

#3 2024-04-10 09:18:40

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

seth wrote:

I am using gnome 46 but the problem existed in 45 as well before i upgraded.
I'll go through the threads you sent, thanks a lot smile

Offline

#4 2024-04-10 12:58:28

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

The first line in the posted log segment is already the indicator of problems, you'll have to look ahead of that to maybe see what's going wrong - "existed in 45"  might indicate a different problem.
In doubt post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2024-04-10 13:10:00

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

seth wrote:

The first line in the posted log segment is already the indicator of problems, you'll have to look ahead of that to maybe see what's going wrong - "existed in 45"  might indicate a different problem.
In doubt post your complete system journal for the boot: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

I've done some more troubleshooting and i do believe that this has to do with timesync. it does not happen when timesync takes place properly. now i just need to narrow it down to why timesync works sometimes and other times not.
I also need to figure out why having the wrong time would cause gnome to not start.

Offline

#6 2024-04-10 14:15:29

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

If you assume this to be the case and assuming you're usign NM for a wifi connection try to https://wiki.archlinux.org/title/Networ … et_on_boot to hopefully sync the time earlier.
nb. that this theory has been rejected by some users (though it's oc. possible that gnome knows multiple ways to crash the session start wink)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2024-04-17 05:48:51

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

the problem unfortunately continues, i have tried changing timesyncd to openntpd but to no avail. this morning it happened 5 times in a row.
I've attached the log from when it happens:

https://0x0.st/Xosx.txt

together with a log when it does not:

https://0x0.st/XosY.txt

I am starting to run out of ideas here so maybe someone could find something in the logs that i am missing.

this seems to mark the spot for when the problem occurs ( frozen prompt symbol and unable to swtich tty ):
gnome-session[1372]: gnome-session-binary[1372]: WARNING: Could not retrieve current screensaver active state: Timeout was reached

the above line does not seem to exist from the log where i am actually able to sign in.

Last edited by hilom (2024-04-17 05:58:25)

Offline

#8 2024-04-18 09:27:33

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

Yes, that very  much fits the pattern in https://bbs.archlinux.org/viewtopic.php?id=292959

apr 17 07:38:16 archlinux /usr/lib/gdm-wayland-session[824]: dbus-daemon[824]: [session uid=120 pid=824] Activating service name='org.freedesktop.systemd1' requested by ':1.11' (uid=120 pid=945 comm="/usr/lib/gsd-sharing")
apr 17 07:38:16 archlinux /usr/lib/gdm-wayland-session[824]: dbus-daemon[824]: [session uid=120 pid=824] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
apr 17 07:38:16 archlinux gsd-sharing[945]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
apr 17 07:38:16 archlinux gsd-sharing[945]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1

This is GDM again, your session failed before that, the screensaver thing is an indicating symptom, but unlikely the cause.

One thing that sticks out in the diff (below) is

 discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
 discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
-app-gnome-gnome\x2dkeyring\x2dssh-1387.scope: PID 1387 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1387.scope', skipping: No such process
-app-gnome-gnome\x2dkeyring\x2dssh-1387.scope: No PIDs left to attach to the scope's control group, refusing.
-app-gnome-gnome\x2dkeyring\x2dssh-1387.scope: Failed with result 'resources'.
 discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
+app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope: PID 1381 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope', skipping: No such process
+app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope: No PIDs left to attach to the scope's control group, refusing.
+app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope: Failed with result 'resources'.
+app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope: PID 1388 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope', skipping: No such process
+app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope: No PIDs left to attach to the scope's control group, refusing.
+app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope: Failed with result 'resources'.
+app-gnome-gnome\x2dkeyring\x2dssh-1384.scope: PID 1384 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1384.scope', skipping: No such process
+app-gnome-gnome\x2dkeyring\x2dssh-1384.scope: No PIDs left to attach to the scope's control group, refusing.
+app-gnome-gnome\x2dkeyring\x2dssh-1384.scope: Failed with result 'resources'.

Only the failure has the pkcs11 and secrects issues (while both struggle w/ ssh)

@@ -1,6 +1,5 @@
 New session 3 of user hilom.
 Created slice User Slice of UID 1000.
-enp4s0: soliciting a DHCP lease
 Starting User Runtime Directory /run/user/1000...
 Finished User Runtime Directory /run/user/1000.
 Starting User Manager for UID 1000...
@@ -58,20 +57,21 @@ Supervising 5 threads of 3 processes of
+NetworkManager-dispatcher.service: Deactivated successfully.
 [string "alsa.lua"]:178: table index is nil
                                         stack traceback:
                                                 [string "alsa.lua"]:178: in function <[string "alsa.lua"]:172>
@@ -86,27 +86,32 @@ Starting Monitor Session leader for GNOM
 The PKCS#11 component was already initialized
 The PKCS#11 component was already initialized
 discover_other_daemon: 1
 discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
-gnome-session-binary[1371]: GnomeDesktop-WARNING: Could not create transient scope for PID 1383: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
-GnomeDesktop-WARNING: Could not create transient scope for PID 1383: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Failed to set unit properties: No such process
 discover_other_daemon: 1
 discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
-Started Application launched by gnome-session-binary.
-app-gnome-gnome\x2dkeyring\x2dssh-1387.scope: PID 1387 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1387.scope', skipping: No such process
-app-gnome-gnome\x2dkeyring\x2dssh-1387.scope: No PIDs left to attach to the scope's control group, refusing.
-app-gnome-gnome\x2dkeyring\x2dssh-1387.scope: Failed with result 'resources'.
-Failed to start Application launched by gnome-session-binary.
 The Secret Service was already initialized
 The Secret Service was already initialized
 discover_other_daemon: 1
 discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
+app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope: PID 1381 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope', skipping: No such process
+app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope: No PIDs left to attach to the scope's control group, refusing.
+app-gnome-gnome\x2dkeyring\x2dpkcs11-1381.scope: Failed with result 'resources'.
+Failed to start Application launched by gnome-session-binary.
+app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope: PID 1388 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope', skipping: No such process
+app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope: No PIDs left to attach to the scope's control group, refusing.
+app-gnome-gnome\x2dkeyring\x2dsecrets-1388.scope: Failed with result 'resources'.
+Failed to start Application launched by gnome-session-binary.
+app-gnome-gnome\x2dkeyring\x2dssh-1384.scope: PID 1384 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1384.scope', skipping: No such process
+app-gnome-gnome\x2dkeyring\x2dssh-1384.scope: No PIDs left to attach to the scope's control group, refusing.
+app-gnome-gnome\x2dkeyring\x2dssh-1384.scope: Failed with result 'resources'.
+Failed to start Application launched by gnome-session-binary.
 Started GNOME Session Manager (session: gnome).
 Reached target GNOME Session Manager is ready.
 Starting GNOME Shell on Wayland...
@@ -181,15 +186,9 @@ Starting GNOME power management service.
 Starting GNOME printer notifications service...
 Starting GNOME RFKill support service...
 Starting GNOME FreeDesktop screensaver service...
-Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory)
 Starting GNOME file sharing service...
 Starting GNOME smartcard service...
 Starting GNOME sound sample caching service...
-Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUnix.InputStream instead.
-                                        0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8]
-                                        1 InterpretGeneratorResume() ["self-hosted":1455:33]
-                                        2 AsyncFunctionNext() ["self-hosted":852:26]
-                                        3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19]
 Starting GNOME USB protection service...
 Starting GNOME Wacom tablet support service...
 Created slice Slice /app/dbus-:1.4-org.gnome.World.PikaBackup.Monitor.
@@ -197,24 +196,22 @@ Started dbus-:1.4-org.gnome.World.PikaBa
 Entering running state
 Finished Signal initialization done to GNOME Session Manager.
 rfkill: input handler disabled
-Starting Disk Manager...
 Started GNOME FreeDesktop screensaver service.
-Started GNOME USB protection service.
+Started GNOME printer notifications service.
 Started GNOME date & time service.
-Started GNOME accessibility service.
 Started GNOME smartcard service.
-Started GNOME printer notifications service.
-Started GNOME file sharing service.
-Started GNOME RFKill support service.
+Starting Disk Manager...
 Started GNOME maintenance of expirable data service.
-Started GNOME sound sample caching service.
+Started GNOME RFKill support service.
+Started GNOME accessibility service.
+Started GNOME USB protection service.
+Started GNOME file sharing service.
 Started Application launched by gnome-session-binary.
 Started Application launched by gnome-session-binary.
 Started Application launched by gnome-session-binary.
 Started Application launched by gnome-session-binary.
 Started Application launched by gnome-session-binary.
 Started Application launched by gnome-session-binary.
-Created slice Slice /app/dbus-:1.4-org.gnome.ScreenSaver.
 Reached target GNOME accessibility target.
 Reached target GNOME date & time target.
 Reached target GNOME maintenance of expirable data target.
@@ -223,13 +220,13 @@ Reached target GNOME RFKill support targ
 Reached target GNOME FreeDesktop screensaver target.
 Reached target GNOME file sharing target.
 Reached target GNOME smartcard target.
-Reached target GNOME sound sample caching target.
 Reached target GNOME USB protection target.
+Started GNOME sound sample caching service.
+Created slice Slice /app/dbus-:1.4-org.gnome.ScreenSaver.
+Reached target GNOME sound sample caching target.
 Started dbus-:1.4-org.gnome.ScreenSaver@0.service.
 udisks daemon version 2.10.1 starting
 Starting Virtual filesystem service - disk device monitor...
-Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
-Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
 Started Disk Manager.
 Acquired the name org.freedesktop.UDisks2 on the system message bus
 Started Virtual filesystem service - disk device monitor.
@@ -238,184 +235,26 @@ Created slice Slice /app/dbus-:1.4-org.g
 Started dbus-:1.4-org.gnome.OnlineAccounts@0.service.
 Started Virtual filesystem service - Apple File Conduit monitor.
 Starting Virtual filesystem service - digital camera monitor...
+Started Evolution source registry.
+Starting Evolution calendar service...
 goa-daemon version 3.50.1 starting
-Started Virtual filesystem service - digital camera monitor.
 Created slice Slice /app/dbus-:1.4-org.gnome.Identity.
 Started dbus-:1.4-org.gnome.Identity@0.service.
+Started Virtual filesystem service - digital camera monitor.
 Starting Virtual filesystem service - GNOME Online Accounts monitor...
 Started Virtual filesystem service - GNOME Online Accounts monitor.
 Starting Virtual filesystem service - Media Transfer Protocol monitor...
-Started Evolution source registry.
 Started Virtual filesystem service - Media Transfer Protocol monitor.
-Registered Authentication Agent for unix-session:3 (system bus name :1.63 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
-Starting Evolution calendar service...
 Your application does not implement g_application_activate() and has no handlers connected to the 'activate' signal.  It should do one of these.
 Starting Portal service...
-<info>  [1713332341.3152] agent-manager: agent[5461b51c164fc77b,:1.63/org.gnome.Shell.NetworkAgent/1000]: agent registered
 Starting flatpak document portal service...
 Started flatpak document portal service.
 Started Evolution calendar service.
-loading user theme: /usr/share/themes/Flat-Remix-Blue-Darkest/gnome-shell/gnome-shell.css
-Theme parser error: gtk.css:4478:3-22: No property named "-gtk-outline-radius"
-Theme parser error: gtk.css:4595:3-29: No property named "-GtkWidget-window-dragging"
-Theme parser error: gtk.css:4609:9-37: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4611:9-38: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4614:9-40: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4616:9-41: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4619:5-33: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4621:5-34: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4624:5-36: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4626:5-37: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4632:7-36: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4634:7-39: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4637:7-35: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4639:7-38: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4713:23-37: Not a valid image
-Theme parser error: gtk.css:4752:3-31: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4754:3-32: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4761:3-34: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4763:3-35: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:5023:12-17: "shade" is not a valid color name.
-Theme parser error: gtk.css:5083:12-17: "shade" is not a valid color name.
-Theme parser error: gtk.css:5110:12-15: "mix" is not a valid color name.
-Theme parser error: gtk.css:5114:12-15: "mix" is not a valid color name.
-Theme parser warning: gtk.css:5315:3-5316:1: Expected ';' at end of block
-Theme parser error: gtk.css:5346:3-19: No property named "-gtk-icon-effect"
 dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._openssl.abi3.so'
-Starting User preferences database...
-Started GNOME color management service.
-Started GNOME keyboard configuration service.
-Reached target GNOME color management target.
-Reached target GNOME keyboard configuration target.
-Started GNOME keyboard shortcuts service.
-Reached target GNOME keyboard shortcuts target.
-Started User preferences database.
-Started GNOME Wacom tablet support service.
-Reached target GNOME Wacom tablet support target.
-Started GNOME power management service.
-Reached target GNOME power management target.
-Reached target GNOME Session.
-Reached target GNOME Wayland Session (session: gnome).
-Reached target Current graphical user session.
-Starting Portal service (GNOME implementation)...
 dropbox: load fq extension '/opt/dropbox/cryptography.hazmat.bindings._padding.abi3.so'
 dropbox: load fq extension '/opt/dropbox/apex._apex.abi3.so'
-Created slice Slice /app/dbus-:1.4-org.freedesktop.FileManager1.
-Started dbus-:1.4-org.freedesktop.FileManager1@0.service.
-NetworkManager-dispatcher.service: Deactivated successfully.
-Failed to grab accelerator for keybinding settings:hibernate
-Failed to grab accelerator for keybinding settings:playback-repeat
-Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
-Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
-Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
-Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
-Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
-Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
-Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
-Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
-Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
-Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
-Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
-Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
-Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
-Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
-Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
-Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
-Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
-Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
-Update check failed: Error resolving “extensions.gnome.org”: Temporary failure in name resolution
-Starting Evolution address book service...
-Connecting to org.freedesktop.Tracker3.Miner.Files
 dropbox: load fq extension '/opt/dropbox/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so'
 dropbox: load fq extension '/opt/dropbox/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so'
-JS ERROR: TypeError: this._prepareStartupAnimation() is undefined
-                                        _loadBackground/signalId</id<@resource:///org/gnome/shell/ui/layout.js:693:26
-                                        @resource:///org/gnome/shell/ui/init.js:21:20
-Started Evolution address book service.
-[string "alsa.lua"]:178: table index is nil
-                                        stack traceback:
-                                                [string "alsa.lua"]:178: in function <[string "alsa.lua"]:172>
-Theme parser error: gtk.css:4478:3-22: No property named "-gtk-outline-radius"
-Theme parser error: gtk.css:4595:3-29: No property named "-GtkWidget-window-dragging"
-Theme parser error: gtk.css:4609:9-37: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4611:9-38: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4614:9-40: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4616:9-41: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4619:5-33: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4621:5-34: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4624:5-36: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4626:5-37: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4632:7-36: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4634:7-39: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4637:7-35: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4639:7-38: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4713:23-37: Not a valid image
-Theme parser error: gtk.css:4752:3-31: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4754:3-32: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4761:3-34: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4763:3-35: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:5023:12-17: "shade" is not a valid color name.
-Theme parser error: gtk.css:5083:12-17: "shade" is not a valid color name.
-Theme parser error: gtk.css:5110:12-15: "mix" is not a valid color name.
-Theme parser error: gtk.css:5114:12-15: "mix" is not a valid color name.
-Theme parser warning: gtk.css:5315:3-5316:1: Expected ';' at end of block
-Theme parser error: gtk.css:5346:3-19: No property named "-gtk-icon-effect"
-Theme parser error: gtk.css:4478:3-22: No property named "-gtk-outline-radius"
-Theme parser error: gtk.css:4595:3-29: No property named "-GtkWidget-window-dragging"
-Theme parser error: gtk.css:4609:9-37: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4611:9-38: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4614:9-40: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4616:9-41: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4619:5-33: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4621:5-34: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4624:5-36: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4626:5-37: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4632:7-36: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4634:7-39: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:4637:7-35: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4639:7-38: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4713:23-37: Not a valid image
-Theme parser error: gtk.css:4752:3-31: No property named "-gtk-outline-top-left-radius"
-Theme parser error: gtk.css:4754:3-32: No property named "-gtk-outline-top-right-radius"
-Theme parser error: gtk.css:4761:3-34: No property named "-gtk-outline-bottom-left-radius"
-Theme parser error: gtk.css:4763:3-35: No property named "-gtk-outline-bottom-right-radius"
-Theme parser error: gtk.css:5023:12-17: "shade" is not a valid color name.
-Theme parser error: gtk.css:5083:12-17: "shade" is not a valid color name.
-Theme parser error: gtk.css:5110:12-15: "mix" is not a valid color name.
-Theme parser error: gtk.css:5114:12-15: "mix" is not a valid color name.
-Theme parser warning: gtk.css:5315:3-5316:1: Expected ';' at end of block
-Theme parser error: gtk.css:5346:3-19: No property named "-gtk-icon-effect"
-Started Portal service (GNOME implementation).
-Supervising 10 threads of 6 processes of 2 users.
-Supervising 10 threads of 6 processes of 2 users.
-Supervising 10 threads of 6 processes of 2 users.
-Starting Portal service (GTK/GNOME implementation)...
-dropbox: load fq extension '/opt/dropbox/tornado.speedups.cpython-38-x86_64-linux-gnu.so'
-Started Portal service (GTK/GNOME implementation).
-GNOME Shell started at Wed Apr 17 2024 07:39:01 GMT+0200 (Central European Summer Time)
-Registering session with GDM
-Shutting down GNOME Shell
-Started Portal service.
-src/daemon/init.rs:63:0: Error setting background status: Portal(NotAllowed("Only sandboxed applications can set background status"))
-Session 1 logged out. Waiting for processes to exit.
-Unregistered Authentication Agent for unix-session:1 (system bus name :1.17, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
-session-1.scope: Deactivated successfully.
-session-1.scope: Consumed 2.188s CPU time.
-Removed session 1.
-Created slice Slice /app/dbus-:1.4-org.gnome.NautilusPreviewer.
-Created slice User Background Tasks Slice.
-Gdm: Child process -813 was already dead.
-Started dbus-:1.4-org.gnome.NautilusPreviewer@0.service.
-Starting Firmware update daemon...
-Starting Tracker file system data miner...
-Created slice Slice /app/dbus-:1.4-org.gnome.Epiphany.WebAppProvider.
-Started dbus-:1.4-org.gnome.Epiphany.WebAppProvider@0.service.
-Activation request for 'org.bluez' failed: The systemd unit 'dbus-org.bluez.service' could not be found.
-Mounted /dev/nvme0n1p1 at /run/media/root/62E5-4546 on behalf of uid 0
-Cleaning up mount point /run/media/root/62E5-4546 (device 259:1 is not mounted)
-Unmounted /dev/nvme0n1p1 on behalf of uid 0
-run-media-root-62E5\x2d4546.mount: Deactivated successfully.
-<info>  [1713332342.5296] dhcp4 (enp4s0): state changed new lease, address=192.168.88.147, acd pending
-Started Tracker file system data miner.
-<info>  [1713332342.7140] dhcp4 (enp4s0): state changed new lease, address=192.168.88.147
-<info>  [1713332342.7142] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS
+<info>  [1713332296.3427] dhcp4 (enp4s0): state changed new lease, address=192.168.88.147, acd pending
+<info>  [1713332296.4967] dhcp4 (enp4s0): state changed new lease, address=192.168.88.147
+<info>  [1713332296.4969] policy: set 'Wired connection 1' (enp4s0) as default for IPv4 routing and DNS

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#9 2024-04-19 07:37:26

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

Just as in this thread: https://bbs.archlinux.org/viewtopic.php?id=292959&p=2 i have not gotten any more freezes since updating the kernel a couple of days ago. Very strange this problem.
I will continue looking into the keyring problem but if i dont receive any additional freezes the next couple of days i will probably consider this solved

Offline

#10 2024-04-20 10:48:37

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

hilom wrote:

Just as in this thread: https://bbs.archlinux.org/viewtopic.php?id=292959&p=2 i have not gotten any more freezes since updating the kernel a couple of days ago. Very strange this problem.
I will continue looking into the keyring problem but if i dont receive any additional freezes the next couple of days i will probably consider this solved

Not solved unfortunately, this morning it happened again 5 times in a row.
Still showing these: 

apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: PID 1351 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1>
apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: No PIDs left to attach to the scope's control group, refusing.
apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: Failed with result 'resources'.
apr 20 14:30:02 archlinux systemd[1245]: Failed to start Application launched by gnome-session-binary.

I have tried moving the following files from /etc/xdg/autostart to /etc/xdg/autostart/OFF too see if that helps solve it.

rw-r--r-- 1 root root  8803 18 mar 14.39 gnome-keyring-pkcs11.desktop
-rw-r--r-- 1 root root  8274 18 mar 14.39 gnome-keyring-secrets.desktop
-rw-r--r-- 1 root root  6763 18 mar 14.39 gnome-keyring-ssh.desktop
-rw-r--r-- 1 root root 12433  5 jun  2023 user-dirs-update-gtk.desktop

will report back with my findings.

Offline

#11 2024-04-21 10:10:09

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

hilom wrote:
hilom wrote:

Just as in this thread: https://bbs.archlinux.org/viewtopic.php?id=292959&p=2 i have not gotten any more freezes since updating the kernel a couple of days ago. Very strange this problem.
I will continue looking into the keyring problem but if i dont receive any additional freezes the next couple of days i will probably consider this solved

Not solved unfortunately, this morning it happened again 5 times in a row.
Still showing these: 

apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: PID 1351 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1>
apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: No PIDs left to attach to the scope's control group, refusing.
apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: Failed with result 'resources'.
apr 20 14:30:02 archlinux systemd[1245]: Failed to start Application launched by gnome-session-binary.

I have tried moving the following files from /etc/xdg/autostart to /etc/xdg/autostart/OFF too see if that helps solve it.

rw-r--r-- 1 root root  8803 18 mar 14.39 gnome-keyring-pkcs11.desktop
-rw-r--r-- 1 root root  8274 18 mar 14.39 gnome-keyring-secrets.desktop
-rw-r--r-- 1 root root  6763 18 mar 14.39 gnome-keyring-ssh.desktop
-rw-r--r-- 1 root root 12433  5 jun  2023 user-dirs-update-gtk.desktop

will report back with my findings.

This did not make the problem go away unfortunately, i have verified that the issue does not show in the logs anymore and the entrys are indeed gone. Have tried disabling IPv6 now as seen in the other thread regarding this issue.
an update is that it's now worse than ever beofre, had to soft reset around 10 times when starting my computer for the day today before being able to sign in.

Offline

#12 2024-04-21 13:47:00

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

had to soft reset around 10 times

Is this actually necessary?
You can't just eg. restart GDM from another VT?
Do you btw. autologin?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2024-04-21 14:10:16

tekstryder
Member
Registered: 2013-02-14
Posts: 133

Re: Gnome freeze at login

hilom wrote:

Still showing these: 

apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: PID 1351 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1>
apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: No PIDs left to attach to the scope's control group, refusing.
apr 20 14:30:02 archlinux systemd[1245]: app-gnome-gnome\x2dkeyring\x2dsecrets-1351.scope: Failed with result 'resources'.
apr 20 14:30:02 archlinux systemd[1245]: Failed to start Application launched by gnome-session-binary.

Regarding these, see also:
https://gitlab.gnome.org/GNOME/gnome-se … issues/120

EDIT: Ooops, not the same errors.

Last edited by tekstryder (2024-04-21 14:11:48)

Offline

#14 2024-04-22 05:55:50

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

seth wrote:

had to soft reset around 10 times

Is this actually necessary?
You can't just eg. restart GDM from another VT?
Do you btw. autologin?

Yep it is, there is nothing else i can do, once it freezes it doesn't take input at all. even the prompt symbol is frozen, once i press the powerbutton it will start blinking again.
Of course i could change to a different tty before trying to sign in via gdm but then the problem wont be triggered. I have also switching to tty2 for example and then switching back to gdm but that will freeze tty2 as well once i sign in.
No autologin.

I had the problem only once this morning after disabling Ipv6 so it may have improved something smile

Offline

#15 2024-04-22 07:11:24

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

Of course i could change to a different tty before trying to sign in via gdm but then the problem wont be triggered.

So it's some race condition for pretty much sure.
Do you have to
1. login on TTY2
2. only switch there first
3. actually just wait a minute
in order to prevent this?
Since you're on nvidia and run GDM & gnome as a wayland session, do you get the same problems when running GDM on X11 and start a gnome/x11 session from there?
https://wiki.archlinux.org/title/GDM#Use_Xorg_backend

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#16 2024-04-22 07:36:08

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

seth wrote:

https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

Of course i could change to a different tty before trying to sign in via gdm but then the problem wont be triggered.

So it's some race condition for pretty much sure.
Do you have to
1. login on TTY2
2. only switch there first
3. actually just wait a minute
in order to prevent this?
Since you're on nvidia and run GDM & gnome as a wayland session, do you get the same problems when running GDM on X11 and start a gnome/x11 session from there?
https://wiki.archlinux.org/title/GDM#Use_Xorg_backend

1. I can login as long as i didn't try signing in with gdm first. no problem
2. Not sure what you mean ? as long as i dont touch gdm or try to sign in there i will be able to switch to a different tty without any issues
3. tried this yesterday, i waited for like 30 minutes and still had issues.

I have not tried using X11 but i'll give it a try.
Thank you for the tip about SysRq, will definitely use that next time this happens.

Offline

#17 2024-04-22 08:56:10

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

I thought you'd be able to reliably prevent the freeze by logging into TTY2 first.

Just a hunch, what if you disable https://help.gnome.org/admin/system-adm … ts.html.en
Apparently it's being "revitalized", https://discourse.gnome.org/t/removing- … p-46/18624

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#18 2024-04-22 09:07:27

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

seth wrote:

I thought you'd be able to reliably prevent the freeze by logging into TTY2 first.

Just a hunch, what if you disable https://help.gnome.org/admin/system-adm … ts.html.en
Apparently it's being "revitalized", https://discourse.gnome.org/t/removing- … p-46/18624

ah got it, nope that doesn't change the issue at all unfortunately.
I've disabled online accounts now, let's see if that fixes it smile

Offline

#19 2024-04-25 05:54:45

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

hilom wrote:
seth wrote:

I thought you'd be able to reliably prevent the freeze by logging into TTY2 first.

Just a hunch, what if you disable https://help.gnome.org/admin/system-adm … ts.html.en
Apparently it's being "revitalized", https://discourse.gnome.org/t/removing- … p-46/18624

ah got it, nope that doesn't change the issue at all unfortunately.
I've disabled online accounts now, let's see if that fixes it smile

This did not fix the problem, i tried today to sign in with X11 instead and that just shows a black screen and an X as a cursor, does not load. I am able to change tty however. here's a log from that sign in case it helps pinpoint the problem.

http://0x0.st/XHcH.txt

Last edited by hilom (2024-04-25 06:09:49)

Offline

#20 2024-04-25 10:51:48

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

just shows a black screen and an X as a cursor, does not load

ie. the X11 server starts but gnome resp. mutter doesn't.

Some annotated events, pay attention to the timestamps.

# you log into gnome
apr 25 09:37:10 archlinux systemd-logind[691]: New session 3 of user hilom.
…
# gkr gets implicitly unlocked
apr 25 09:37:10 archlinux gdm-password][1221]: gkr-pam: unlocked login keyring
…
# gsd-media-keys complains, probably b/c there's no display server
apr 25 09:37:10 archlinux gsd-media-keys[981]: Unable to get default source
…
# which is however now started and you've to outputs on the only GPU
apr 25 09:37:10 archlinux /usr/lib/gdm-x-session[1346]: (--) NVIDIA(GPU-0): AOC 32G1WG4 (DFP-1): connected
apr 25 09:37:10 archlinux /usr/lib/gdm-x-session[1346]: (--) NVIDIA(GPU-0): Lenovo Group Limited P27 (DFP-3): connected
…
# leading to X11 at 5760 x 2160
apr 25 09:37:10 archlinux /usr/lib/gdm-x-session[1346]: (II) NVIDIA(0): Virtual screen size determined to be 5760 x 2160
…
# "Yay"
apr 25 09:37:11 archlinux systemd[1285]: Reached target GNOME X11 Session.
…
# mutter starts, nb. the warning about the experimental feature
apr 25 09:37:11 archlinux gnome-shell[1436]: Running GNOME Shell (using mutter 46.1) as a X11 window and compositing manager
apr 25 09:37:11 archlinux gnome-shell[1436]: Enabling experimental feature 'scale-monitor-framebuffer'
…
# Your monitor.xml and that extension look like trouble - move away the former and disable the latter?
==== apr 25 09:37:11 archlinux gnome-shell[1436]: Failed to read monitors config file '/home/hilom/.config/monitors.xml': A fractional scale with physical layout mode not allowed
…
==== apr 25 09:37:12 archlinux gnome-shell[1436]: Could not load extension dash-to-dock: Error: uuid "dash-to-dock@micxgx.gmail.com" from metadata.json does not match directory name "dash-to-dock"
…
# infamouse screensaver service starts
apr 25 09:37:12 archlinux systemd[1285]: Started GNOME FreeDesktop screensaver service.
…
# and 1s later, in the midst of DB starting "times out"… :(
apr 25 09:37:13 archlinux dropbox.desktop[1571]: dropbox: load fq extension '/opt/dropbox/tornado.speedups.cpython-38-x86_64-linux-gnu.so'
apr 25 09:37:13 archlinux gnome-session[1428]: gnome-session-binary[1428]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
apr 25 09:37:13 archlinux gnome-session-binary[1428]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
apr 25 09:37:14 archlinux dropbox.desktop[1571]: dropbox: load fq extension '/opt/dropbox/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so'
…
# only then the NTP sync hits (apparently 10s later)
apr 25 07:37:24 archlinux systemd-timesyncd[668]: Contacted time server 192.121.108.99:123 (2.arch.pool.ntp.org).
apr 25 07:37:24 archlinux systemd-journald[394]: Time jumped backwards, rotating.
apr 25 07:37:24 archlinux systemd-timesyncd[668]: Initial clock synchronization to Thu 2024-04-25 07:37:24.492304 CEST.
…
# You're switching to TTY3
apr 25 07:37:26 archlinux systemd[1]: Started Getty on tty3.
…
# Not sure whether those errors occur because you lost the frambuffer?
apr 25 07:37:32 archlinux gsd-media-keys[981]: Unable to get default source
apr 25 07:37:37 archlinux gnome-session[1428]: gnome-session-binary[1428]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
apr 25 07:37:37 archlinux gnome-session-binary[1428]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
apr 25 07:37:37 archlinux gsd-xsettings[1574]: Failed to get current display configuration state: Timeout was reached
apr 25 07:37:37 archlinux gsd-usb-protect[1569]: Failed to get screen saver status: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code24: Timeout was reached
apr 25 07:37:37 archlinux gsd-usb-protect[1569]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
…
# this looks like a re-login?
apr 25 07:37:42 archlinux gdm-password][2203]: gkr-pam: unlocked login keyring
…
# return to X11
apr 25 07:37:43 archlinux /usr/lib/gdm-x-session[1346]: (II) systemd-logind: got resume for 13:65
…
# back to, probably TTY3
apr 25 07:37:47 archlinux /usr/lib/gdm-x-session[1346]: (II) event4  - Keychron Keychron K5 SE: device removed
…
# where you now log in
apr 25 07:37:53 archlinux login[2061]: LOGIN ON tty3 BY hilom

Did you indeed log into a black screen then ~15s later swicth to TTY3, but did not! log in there for ~18s, return to X11, then 4s later back to TTY3 to log in there (and restart GDM, I assume)

When you're logging into a black screen and from there head over to TTY3, is there (still) and active gnome-shell/mutter process (for your UID 1000 - GDM will hold one under UID 120)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#21 2024-04-25 11:08:32

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

seth wrote:

just shows a black screen and an X as a cursor, does not load

ie. the X11 server starts but gnome resp. mutter doesn't.

Some annotated events, pay attention to the timestamps.

# you log into gnome
apr 25 09:37:10 archlinux systemd-logind[691]: New session 3 of user hilom.
…
# gkr gets implicitly unlocked
apr 25 09:37:10 archlinux gdm-password][1221]: gkr-pam: unlocked login keyring
…
# gsd-media-keys complains, probably b/c there's no display server
apr 25 09:37:10 archlinux gsd-media-keys[981]: Unable to get default source
…
# which is however now started and you've to outputs on the only GPU
apr 25 09:37:10 archlinux /usr/lib/gdm-x-session[1346]: (--) NVIDIA(GPU-0): AOC 32G1WG4 (DFP-1): connected
apr 25 09:37:10 archlinux /usr/lib/gdm-x-session[1346]: (--) NVIDIA(GPU-0): Lenovo Group Limited P27 (DFP-3): connected
…
# leading to X11 at 5760 x 2160
apr 25 09:37:10 archlinux /usr/lib/gdm-x-session[1346]: (II) NVIDIA(0): Virtual screen size determined to be 5760 x 2160
…
# "Yay"
apr 25 09:37:11 archlinux systemd[1285]: Reached target GNOME X11 Session.
…
# mutter starts, nb. the warning about the experimental feature
apr 25 09:37:11 archlinux gnome-shell[1436]: Running GNOME Shell (using mutter 46.1) as a X11 window and compositing manager
apr 25 09:37:11 archlinux gnome-shell[1436]: Enabling experimental feature 'scale-monitor-framebuffer'
…
# Your monitor.xml and that extension look like trouble - move away the former and disable the latter?
==== apr 25 09:37:11 archlinux gnome-shell[1436]: Failed to read monitors config file '/home/hilom/.config/monitors.xml': A fractional scale with physical layout mode not allowed
…
==== apr 25 09:37:12 archlinux gnome-shell[1436]: Could not load extension dash-to-dock: Error: uuid "dash-to-dock@micxgx.gmail.com" from metadata.json does not match directory name "dash-to-dock"
…
# infamouse screensaver service starts
apr 25 09:37:12 archlinux systemd[1285]: Started GNOME FreeDesktop screensaver service.
…
# and 1s later, in the midst of DB starting "times out"… :(
apr 25 09:37:13 archlinux dropbox.desktop[1571]: dropbox: load fq extension '/opt/dropbox/tornado.speedups.cpython-38-x86_64-linux-gnu.so'
apr 25 09:37:13 archlinux gnome-session[1428]: gnome-session-binary[1428]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
apr 25 09:37:13 archlinux gnome-session-binary[1428]: WARNING: Could not retrieve current screensaver active state: Timeout was reached
apr 25 09:37:14 archlinux dropbox.desktop[1571]: dropbox: load fq extension '/opt/dropbox/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so'
…
# only then the NTP sync hits (apparently 10s later)
apr 25 07:37:24 archlinux systemd-timesyncd[668]: Contacted time server 192.121.108.99:123 (2.arch.pool.ntp.org).
apr 25 07:37:24 archlinux systemd-journald[394]: Time jumped backwards, rotating.
apr 25 07:37:24 archlinux systemd-timesyncd[668]: Initial clock synchronization to Thu 2024-04-25 07:37:24.492304 CEST.
…
# You're switching to TTY3
apr 25 07:37:26 archlinux systemd[1]: Started Getty on tty3.
…
# Not sure whether those errors occur because you lost the frambuffer?
apr 25 07:37:32 archlinux gsd-media-keys[981]: Unable to get default source
apr 25 07:37:37 archlinux gnome-session[1428]: gnome-session-binary[1428]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
apr 25 07:37:37 archlinux gnome-session-binary[1428]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
apr 25 07:37:37 archlinux gsd-xsettings[1574]: Failed to get current display configuration state: Timeout was reached
apr 25 07:37:37 archlinux gsd-usb-protect[1569]: Failed to get screen saver status: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code24: Timeout was reached
apr 25 07:37:37 archlinux gsd-usb-protect[1569]: Failed to fetch USBGuard parameters: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
…
# this looks like a re-login?
apr 25 07:37:42 archlinux gdm-password][2203]: gkr-pam: unlocked login keyring
…
# return to X11
apr 25 07:37:43 archlinux /usr/lib/gdm-x-session[1346]: (II) systemd-logind: got resume for 13:65
…
# back to, probably TTY3
apr 25 07:37:47 archlinux /usr/lib/gdm-x-session[1346]: (II) event4  - Keychron Keychron K5 SE: device removed
…
# where you now log in
apr 25 07:37:53 archlinux login[2061]: LOGIN ON tty3 BY hilom

Did you indeed log into a black screen then ~15s later swicth to TTY3, but did not! log in there for ~18s, return to X11, then 4s later back to TTY3 to log in there (and restart GDM, I assume)

When you're logging into a black screen and from there head over to TTY3, is there (still) and active gnome-shell/mutter process (for your UID 1000 - GDM will hold one under UID 120)?

Yup that sums it up pretty well i would say. i switched back and forth between TTY3 and X11 to check if it was frozen or not the first time. second time i switched back i did indeed login to check journalctl. I never restarted GDM but did a reset of my computer instead.
I'll check if there is some active process for gnome-shell next time i reboot.

Offline

#22 2024-04-25 15:21:07

seth
Member
Registered: 2012-09-03
Posts: 51,731

Re: Gnome freeze at login

I should probably highlight this:

seth wrote:

…
# Your monitor.xml and that extension look like trouble - move away the former and disable the latter?
==== apr 25 09:37:11 archlinux gnome-shell[1436]: Failed to read monitors config file '/home/hilom/.config/monitors.xml': A fractional scale with physical layout mode not allowed
…
==== apr 25 09:37:12 archlinux gnome-shell[1436]: Could not load extension dash-to-dock: Error: uuid "dash-to-dock@micxgx.gmail.com" from metadata.json does not match directory name "dash-to-dock"
…

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#23 2024-04-27 09:31:43

hilom
Member
Registered: 2023-10-16
Posts: 19

Re: Gnome freeze at login

seth wrote:

I should probably highlight this:

seth wrote:

…
# Your monitor.xml and that extension look like trouble - move away the former and disable the latter?
==== apr 25 09:37:11 archlinux gnome-shell[1436]: Failed to read monitors config file '/home/hilom/.config/monitors.xml': A fractional scale with physical layout mode not allowed
…
==== apr 25 09:37:12 archlinux gnome-shell[1436]: Could not load extension dash-to-dock: Error: uuid "dash-to-dock@micxgx.gmail.com" from metadata.json does not match directory name "dash-to-dock"
…

I am definitely not sure but it seems like removing the monitors.xml actually did the trick. i have not gotten any more freezes since doing that.
It could of course be something else as well ( update, etc ) but this could actually explain why i've had this problem through several different versions of gnome as well.
It does however not explain why this would happen 10 times in a row and then suddenly work.

I will test it out a couple of more days but so far so good.

Last edited by hilom (2024-04-27 09:53:20)

Offline

Pages: 1

Board footer

Powered by FluxBB