[Solved] Gnome freezes sometimes after typing password after login

freewick · 2024-03-15 02:26:16

Hi, I have this problem for quite a while but started to live with it but just want to know if this can be fixed.

Sometimes when I try to login in to gnome session be it wayland or x11 immediately after login. The entire session freezes. I have KDE and Hypland as alternatives too but it only happens with gnome session. Hoever the freeze is different from wayland to gnome. It started happening at gnome 44. Initally I thought it was the extensions fault and disabled them and it still happened. The freeze happens differs from x11 and wayland.

When I try to login in Gnome x11 session, The login screen freezes however I can move my cursor and enter into tty. After entering tty by pressing ctrl+alt+f3, I login and logout using

sudo pkill -u user

and then if I login back again using sddm which is my login manager, I can login.

However when I try to login wayland gnome session, sometimes the screen freezes fully I cant move mouse cursor and cant use tty at all . I have to use powerbutton to reboot.

I dont know why buy if I login to gnome x11 first and even if freeze happens and If I do the work around I mentioned above, I can logout from x11 gnome and login to wayland gnome without any errors. Means once i login to gnome x11 I can login to gnome wayland without any problem.

I have the journal log for the case where gnome freeze happened when I tried to login into x11 and I used tty a mentioned above and then logged into wayland session but cant read it and debug it.

Here is the link to journal https://0x0.st/HF8-.txt.

Please tell me what is creating this issue. Any help is appreciated.

Last edited by freewick (2024-03-20 22:49:08)

seth · 2024-03-15 08:55:12

You've two AMD GPUs and they flip order because of the simplydumb device, try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters and in doubt post the xorg log of a failed attempt, https://wiki.archlinux.org/title/Xorg#General

freewick · 2024-03-16 11:22:58

seth wrote:

You've two AMD GPUs and they flip order because of the simplydumb device, try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters and in doubt post the xorg log of a failed attempt, https://wiki.archlinux.org/title/Xorg#General

Thanks for the answer. I edited /etc/default/grub as below

GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet initcall_blacklist=simpledrm_platform_driver_init"

and then regenerated the grub with

sudo grub-mkconfig -o /boot/grub/grub.cfg

.

I will see if it fixes the problem and if not I will post the update.

Edit: I just rebooted thrice and in the second attempt to wayland gnome session, it froze like before which means it didn't work . Any other things I can try??

The journal https://0x0.st/HF8-.txt I linked in the first post is when I had that freeze when I tried to login to xorg gnome session. I will try to boot again and when the freeze comes I will upload the journal again if u want

Last edited by freewick (2024-03-16 11:32:28)

freewick · 2024-03-16 11:41:19

seth wrote:

You've two AMD GPUs and they flip order because of the simplydumb device, try to add "initcall_blacklist=simpledrm_platform_driver_init" to the https://wiki.archlinux.org/title/Kernel_parameters and in doubt post the xorg log of a failed attempt, https://wiki.archlinux.org/title/Xorg#General

I think the kernel parameter solution didnt work or did I do something wrong trying to applying your solution as mentioned in above post?

I just rebooted and tried to login into xorg gnome and got freeze. I enter into tty using ctrl_alt_f3 and logged in as me and then logged out using "sudo pkill -u username". Then I went back to sddm login screen again and then this time when I logged in to xorg gnome it didn't freeze. Here is the journal of this process https://0x0.st/HFwW.txt

Last edited by freewick (2024-03-16 11:41:37)

seth · 2024-03-16 14:58:18

The journal has only one login:

Mar 16 17:03:54 sanganaka systemd-logind[702]: New session 2 of user wick.

Do you actually have to re-login etc.?
https://bbs.archlinux.org/viewtopic.php?id=292649 (though suppsingly fixed in 6.7.9)

What if you boot up to SDDM, get a cup of coffee and then log into gnome (ie. simply delay the process a bit)?

freewick · 2024-03-16 17:10:02

seth wrote:

The journal has only one login:
Mar 16 17:03:54 sanganaka systemd-logind[702]: New session 2 of user wick.
Do you actually have to re-login etc.?
https://bbs.archlinux.org/viewtopic.php?id=292649 (though suppsingly fixed in 6.7.9)
What if you boot up to SDDM, get a cup of coffee and then log into gnome (ie. simply delay the process a bit)?

I dont know if I am logging in first time cause screen is freezing. When I first start the laptop and sddm first appears I selected gnome xorg and then typed the pasword and pressed enter. The screen froze and I can move my mouse cursor. I am considering this a login as I dont know what journal considers login.

After that scren freeze I entered tty and the entered my username and password and then logged out using pkill. After that sddm reappeared again. From that I type password again and then I was able to use xor gnome and access all apps. I am considering this as a second login.

Immediately after this I uploaded the journal. I will try to wait for a minute next time in the sddm section and see if it changes anything.

while freezing is happening in xorg gnome I cant even move my cursor or enter tty in wayland gnome. It only happens to gnome. KDe and hyprland are fine. So I think its a gnome bug??
Any other things I can try?

seth · 2024-03-16 17:21:58

I am considering this as a second login.

Yeah, but that's not in the journal of https://0x0.st/HFwW.txt
Not even the TTY login is.

Let's see whether it's time sensitive.
Also try to just switch the TTY and back, not killing or restarting anything.

freewick · 2024-03-16 22:31:57

seth wrote:

I am considering this as a second login.
Yeah, but that's not in the journal of https://0x0.st/HFwW.txt
Not even the TTY login is.
Let's see whether it's time sensitive.
Also try to just switch the TTY and back, not killing or restarting anything.

I used this command immediately after I login into the gnome session.

journalctl -D /var/log/journal -b -1 | curl -F 'file=@-' 0x0.st

which I got it from you when my system broke and made a post here. Is this the correct way to upload the journal or am I doing something wrong?

Also I waited 5 mins after sddm login screen appears and tried to login to gnome wayland session but unfortunately it froze. I did the tty change back and forth and nothing really changed one freeze screen where I can move my cursor and other one with the option to enter login .

I want to mention that in the sddm login screen options I have 2 wayland gnome options available. One is called Gnome on wayland and other is Gnome(wayland). Both causes the freeze and also both works. Also there is just Gnome option which for some reason always using xorg session and there is specific Gnome on Xorg session. There are other options too like Gnome classic on xorg and wayland but I never used them. Are these source of these issues cause kde only has 2 options, wayland and x11.

seth · 2024-03-16 22:45:35

That's from the previous boot (the "-1")

You've apparently copies of some sessions in /usr/local

Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome-classic-wayland.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome-classic.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome-wayland.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/hyprland.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/plasma.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome-classic-xorg.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome-classic.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome-xorg.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/plasmax11.desktop"

pacman -Qo /usr/local/share/xsessions/gnome.desktop

(probably nothing) - any idea where those are coming from?
You might be loading more stuff from there but unless you're magically choosing the proper session on every second login (only) I don't see how this could explain those freezes.

freewick · 2024-03-16 23:30:25

seth wrote:

That's from the previous boot (the "-1")

You've apparently copies of some sessions in /usr/local

Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome-classic-wayland.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome-classic.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome-wayland.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/gnome.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/hyprland.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/wayland-sessions/plasma.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome-classic-xorg.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome-classic.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome-xorg.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/gnome.desktop"
Mar 16 17:03:30 sanganaka sddm-greeter-qt6[887]: Reading from "/usr/local/share/xsessions/plasmax11.desktop"

pacman -Qo /usr/local/share/xsessions/gnome.desktop

(probably nothing) - any idea where those are coming from?
You might be loading more stuff from there but unless you're magically choosing the proper session on every second login (only) I don't see how this could explain those freezes.

I see so they might not be the issue. I just tried to login to th Gnome session which by default uses X11 and had a freeze again. Instead of using tty to login and using pkill and logout and login, I tried different ttys and tried to switch between them and then rebooted using ctrl+alt+del and in the second attempt I did the same and in the third attempt I logged in to Gnome session and here is the journal link

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

I didnt try to login to tty this time but only rebooted using keys. will this help to debug?

seth · 2024-03-16 23:41:44

The plan would have been to login, fail, re-login, succeed and post a journal of that boot so one can look out for the differences between the sessions…

Edit:

Mar 17 04:52:35 sanganaka gnome-keyring-pkcs11.desktop[1288]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope: PID 1281 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope', skipping: No such process
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope: No PIDs left to attach to the scope's control group, refusing.
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope: Failed with result 'resources'.
Mar 17 04:52:35 sanganaka systemd[1192]: Failed to start Application launched by gnome-session-binary.
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dssh-1277.scope: PID 1277 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1277.scope', skipping: No such process
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dssh-1277.scope: No PIDs left to attach to the scope's control group, refusing.
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dssh-1277.scope: Failed with result 'resources'.
Mar 17 04:52:35 sanganaka systemd[1192]: Failed to start Application launched by gnome-session-binary.

Just a hunch

pacman -Qs portal

https://archlinux.org/packages/extra/x8 … tal-gnome/

Last edited by seth (2024-03-16 23:45:54)

freewick · 2024-03-17 00:04:48

seth wrote:

The plan would have been to login, fail, re-login, succeed and post a journal of that boot so one can look out for the differences between the sessions…

Edit:

Mar 17 04:52:35 sanganaka gnome-keyring-pkcs11.desktop[1288]: discover_other_daemon: 1GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope: PID 1281 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope', skipping: No such process
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope: No PIDs left to attach to the scope's control group, refusing.
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dpkcs11-1281.scope: Failed with result 'resources'.
Mar 17 04:52:35 sanganaka systemd[1192]: Failed to start Application launched by gnome-session-binary.
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dssh-1277.scope: PID 1277 vanished before we could move it to target cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-gnome\x2dkeyring\x2dssh-1277.scope', skipping: No such process
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dssh-1277.scope: No PIDs left to attach to the scope's control group, refusing.
Mar 17 04:52:35 sanganaka systemd[1192]: app-gnome-gnome\x2dkeyring\x2dssh-1277.scope: Failed with result 'resources'.
Mar 17 04:52:35 sanganaka systemd[1192]: Failed to start Application launched by gnome-session-binary.

Just a hunch

pacman -Qs portal

https://archlinux.org/packages/extra/x8 … tal-gnome/

I tried login via tty and uploaded it before but as u mentioned the journal only says I am logging in once which for some reason I don't understand as I tried to login and failed and used tty and logged in and logged out using pkill and then login back again and posted journal. I don't know what mistake I am doing here cause as u said journal sees I am only logging once.

I dont know any other way to login other than using tty once freeze happens anf the logout using pkill. Is there any other ways you recommend logging in and logging out via tty?

Also here is the output for the portal command.

pacman -Qs portal
local/libportal 0.7.1-2
    GIO-style async APIs for most Flatpak portals
local/libportal-gtk3 0.7.1-2
    GIO-style async APIs for most Flatpak portals - GTK 3 backend
local/libportal-gtk4 0.7.1-2
    GIO-style async APIs for most Flatpak portals - GTK 4 backend
local/xdg-desktop-portal 1.18.2-1
    Desktop integration portals for sandboxed apps
local/xdg-desktop-portal-gnome 45.1-1 (gnome)
    A backend implementation for xdg-desktop-portal for the GNOME desktop environment
local/xdg-desktop-portal-gtk 1.15.1-1
    A backend implementation for xdg-desktop-portal using GTK
local/xdg-desktop-portal-hyprland 1.3.1-5
    xdg-desktop-portal backend for hyprland
local/xdg-desktop-portal-kde 6.0.2-3 (plasma)
    A backend implementation for xdg-desktop-portal using Qt/KF5

seth · 2024-03-17 00:23:43

for some reason I don't understand

Because

seth wrote:

That's [been] from the previous boot (the "-1")

You can still access earlier boots this way (increase the digit, eg. "-b -4") - one of them likely has several "New session ? of user wick" lines - that's gonna be the interesting one.

freewick · 2024-03-17 00:33:44

seth wrote:

for some reason I don't understand
Because
seth wrote:
That's [been] from the previous boot (the "-1")
You can still access earlier boots this way (increase the digit, eg. "-b -4") - one of them likely has several "New session ? of user wick" lines - that's gonna be the interesting one.

So should I just do

journalctl -D /var/log/journal  | curl -F 'file=@-' 0x0.st

after login fail tty and login successful?

freewick · 2024-03-17 00:53:57

seth wrote:

for some reason I don't understand
Because
seth wrote:
That's [been] from the previous boot (the "-1")
You can still access earlier boots this way (increase the digit, eg. "-b -4") - one of them likely has several "New session ? of user wick" lines - that's gonna be the interesting one.

I just rebooted and successfully logged in 2 times into gnome xorg session and failed 3 time. At third time the screen froze and I went into tty and logged in and used pkill and came back to sddm login screen and entered password and I logged in properly.

I immediately opened console and here is journal with possible all commands

❯ journalctl -D /var/log/journal -b  | curl -F 'file=@-' 0x0.st
http://0x0.st/HC7I.txt
❯ journalctl -D /var/log/journal  | curl -F 'file=@-' 0x0.st
http://0x0.st/HC7U.txt
❯ journalctl -D /var/log/journal -b -1 | curl -F 'file=@-' 0x0.st
http://0x0.st/HC70.txt

http://0x0.st/HC7I.txt with -b flag and http://0x0.st/HC7U.txt without any flags and http://0x0.st/HC70.txt with -b and -1 flags.

So I think I hopefully gave you and posted what you need this time properly. Please let me know If I made any mistake this time.

freewick · 2024-03-17 12:24:13

seth wrote:

for some reason I don't understand
Because
seth wrote:
That's [been] from the previous boot (the "-1")
You can still access earlier boots this way (increase the digit, eg. "-b -4") - one of them likely has several "New session ? of user wick" lines - that's gonna be the interesting one.

Should I send even more previous journals and post links or the above ones which I posted earlier fine for debugging?

seth · 2024-03-17 14:36:28

Mar 17 06:15:25 sanganaka xdg-desktop-por[3213]: Unknown key gtk-modules in /home/wick/.config/gtk-4.0/settings.ini
Mar 17 06:15:25 sanganaka xdg-desktop-por[3213]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

doesn't show up in the "bad" session.

Before the first session starts there's

Mar 17 06:13:58 sanganaka dbus-daemon[867]: [session uid=954 pid=867] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.2' (uid=954 pid=895 comm="/usr/lib/xdg-desktop-portal")
Mar 17 06:13:58 sanganaka xdg-desktop-por[915]: cannot open display: 
Mar 17 06:13:58 sanganaka systemd[850]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Mar 17 06:13:58 sanganaka systemd[850]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.

There's no attempt to start a portal service during your 1st login, htere're two failing ones during the TTY3 login and finally in the second GUI login xdg-desktop-portal-gnome (not! GTK) is started and succeeds.
So the reason is -possibly- that xdg-desktop-portal-gnome isn't started during the first run of gnome - it's not even tried (despite the session running for a good while and it probably should™ be) although portal gets triggered

Mar 17 06:14:10 sanganaka dbus-daemon[1194]: [session uid=1000 pid=1194] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gnome' unit='xdg-desktop-portal-gnome.service' requested by ':1.48' (uid=1000 pid=1574 comm="/usr/lib/xdg-desktop-portal")

There're ultimately

Mar 17 06:15:00 sanganaka gsd-power[1486]: Could not create GnomeRRScreen: Timeout was reached
Mar 17 06:15:00 sanganaka gsd-xsettings[1522]: Failed to get current display configuration state: Timeout was reached
Mar 17 06:15:00 sanganaka xdg-desktop-por[1574]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached

And before that

Mar 17 06:14:35 sanganaka gnome-session[1246]: gnome-session-binary[1246]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
Mar 17 06:14:35 sanganaka gnome-session-binary[1246]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
Mar 17 06:14:35 sanganaka gsd-xsettings[1522]: Failed to get current display configuration state: Timeout was reached

It's unfortunately not clear how much of that is simply down to the TTY3 switch.
=> Let's clean up a bit
1. You've NM and dhcpcd enabled => disable dhcpcd
2. remove passim and by inference avahi-daemon
3. remove docker, flatpak, containerd (are you actually using *all* those container systems in parallel) and all xdg-desktop-portal-* implementations but the gtk one (or gnome, but the latter will fail on other environments)
4. reboot, log into gnome. If it's still black, get a cup of coffee. Walk your dog. 5 minutes to 5h later (depending on the dog) switch the VT, kill your session and re-login to gnome
5. Post the journal of that boot.

freewick · 2024-03-17 15:34:30

seth wrote:

Mar 17 06:15:25 sanganaka xdg-desktop-por[3213]: Unknown key gtk-modules in /home/wick/.config/gtk-4.0/settings.ini
Mar 17 06:15:25 sanganaka xdg-desktop-por[3213]: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.
doesn't show up in the "bad" session.
Before the first session starts there's
Mar 17 06:13:58 sanganaka dbus-daemon[867]: [session uid=954 pid=867] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gtk' unit='xdg-desktop-portal-gtk.service' requested by ':1.2' (uid=954 pid=895 comm="/usr/lib/xdg-desktop-portal")
Mar 17 06:13:58 sanganaka xdg-desktop-por[915]: cannot open display: 
Mar 17 06:13:58 sanganaka systemd[850]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Mar 17 06:13:58 sanganaka systemd[850]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
There's no attempt to start a portal service during your 1st login, htere're two failing ones during the TTY3 login and finally in the second GUI login xdg-desktop-portal-gnome (not! GTK) is started and succeeds.
So the reason is -possibly- that xdg-desktop-portal-gnome isn't started during the first run of gnome - it's not even tried (despite the session running for a good while and it probably should™ be) although portal gets triggered
Mar 17 06:14:10 sanganaka dbus-daemon[1194]: [session uid=1000 pid=1194] Activating via systemd: service name='org.freedesktop.impl.portal.desktop.gnome' unit='xdg-desktop-portal-gnome.service' requested by ':1.48' (uid=1000 pid=1574 comm="/usr/lib/xdg-desktop-portal")
There're ultimately
Mar 17 06:15:00 sanganaka gsd-power[1486]: Could not create GnomeRRScreen: Timeout was reached
Mar 17 06:15:00 sanganaka gsd-xsettings[1522]: Failed to get current display configuration state: Timeout was reached
Mar 17 06:15:00 sanganaka xdg-desktop-por[1574]: Failed to create settings proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.gnome: Timeout was reached
And before that
Mar 17 06:14:35 sanganaka gnome-session[1246]: gnome-session-binary[1246]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
Mar 17 06:14:35 sanganaka gnome-session-binary[1246]: GnomeDesktop-WARNING: Failed to acquire idle monitor proxy: Timeout was reached
Mar 17 06:14:35 sanganaka gsd-xsettings[1522]: Failed to get current display configuration state: Timeout was reached
It's unfortunately not clear how much of that is simply down to the TTY3 switch.
=> Let's clean up a bit
1. You've NM and dhcpcd enabled => disable dhcpcd
2. remove passim and by inference avahi-daemon
3. remove docker, flatpak, containerd (are you actually using *all* those container systems in parallel) and all xdg-desktop-portal-* implementations but the gtk one (or gnome, but the latter will fail on other environments)
4. reboot, log into gnome. If it's still black, get a cup of coffee. Walk your dog. 5 minutes to 5h later (depending on the dog) switch the VT, kill your session and re-login to gnome
5. Post the journal of that boot.

By remove you mean uninstall? Cause I have a lot of flatpak apps installed that I use. Is it ok if I just unistall docker and thi containerd and do ass u say cause I fear will loose data of those applications.

seth · 2024-03-17 15:43:31

Please don't post full quotes w/o reason - you're bloating the thread.
The main purpose is to simplify the system as much as possible to reduce the variables and cut out the noise - you can therefore keep flatpak (and you'll have to keep one portal implementation anyway)

hlechner · 2024-03-17 22:16:19

Can you try to use GDM (https://wiki.archlinux.org/title/GDM) and see if the issue still remains?

Explaining:
I was searching for how to solve my issue, very similar to yours but

initcall_blacklist=simpledrm_platform_driver_init

was enough (thanks seth for that)

Looking at your logs I find the those:

Mar 17 06:14:10 sanganaka gnome-session[1246]: gnome-session-binary[1246]: WARNING: Could not retrieve current screensaver active state: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files
Mar 17 06:14:10 sanganaka gnome-session-binary[1246]: WARNING: Could not retrieve current screensaver active state: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files
Mar 17 06:14:10 sanganaka gsd-usb-protect[1504]: Failed to get screen saver status: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files

Very similar messages the ones I had but Instead of timeout you have a "Error.ServiceUnknown: The name org.gnome.Shell.ScreenShield was not provided by any .service files", looking for that error this topic seems interesting: https://bbs.archlinux.org/viewtopic.php?id=289934

Not same issue you're having but same error messages and it solved by change from SDDM to GDM.

Since I'm using GDM already, I've noticed that GDM starts a process "/usr/bin/gjs -m /usr/share/gnome-shell/org.gnome.ScreenSaver" and if I kill this process before I login in GDM it most of the time freezes even with the initcall_blacklist.

So, some chances that with GDM it will work out of the box.

seth · 2024-03-17 22:25:55

I was actually hoping that this wasn't absolutely true and the other thread has so far remained an isolated incident and condition and symptoms are different… except… @freewick do you usually log into a locked session?

freewick · 2024-03-17 23:26:22

seth wrote:

Please don't post full quotes w/o reason - you're bloating the thread.

Sorry. I thought by quoting you will get specific notification and I will do as little as possible. Also while doing things u asked I felt sleepy and slept and just wokeup

seth wrote:

The main purpose is to simplify the system as much as possible to reduce the variables and cut out the noise - you can therefore keep flatpak (and you'll have to keep one portal implementation anyway)

I tried to do as you asked and here is what I did. I disabled dhcpd using systemd. Then I uninstalled containerd, docker a well as passim. I am unable to uninstall avahi as it is a dependency for ostree and multiple things but disabled its service using systemd. I then uninstalled xdg-desktop-portal-gnome and hyprland but didnt remove kde one as it is a dependency for some kde things.

❯ systemctl status dhcpcd.service
○ dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; preset: disabled)
     Active: inactive (dead)
❯ systemctl disable dhcpcd.service
❯ paru -R containerd docker passim
[sudo] password for wick:
error: target not found: containerd
error: target not found: docker
error: target not found: passim
❯ systemctl disable avahi-daemon.service
❯ paru -R xdg-desktop-portal-kde xdg-desktop-portal-hyprland xdg-desktop-porta
❯ systemctl status dhcpcd.service
○ dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; preset: disabled)
     Active: inactive (dead)
❯ systemctl disable dhcpcd.service
❯ paru -R containerd docker passim
error: target not found: containerd
error: target not found: docker
error: target not found: passim
❯ systemctl status avahi-daemon.service
○ avahi-daemon.service - Avahi mDNS/DNS-SD Stack
     Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; disabled; preset: disabled)
     Active: inactive (dead)
TriggeredBy: ○ avahi-daemon.socket
❯ paru -R containerd docker passim
error: target not found: containerd
error: target not found: docker
error: target not found: passim
❯ paru -R xdg-desktop-portal-hyprland xdg-desktop-portal-gnome
error: target not found: xdg-desktop-portal-hyprland
error: target not found: xdg-desktop-portal-gnome
❯ paru -R xdg-desktop-portal-kde
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing xdg-desktop-portal-kde breaks dependency 'xdg-desktop-portal-kde' required by plasma-integration
:: removing xdg-desktop-portal-kde breaks dependency 'xdg-desktop-portal-kde' required by plasma-meta

Here I found interesting things. After doing all this when I rebooted and logged into gnome xorg session I never got a crash! which means something you suggested is affecting. Also before in xorg gnome session I see weird rectangular patches of of application over another which never happened after this. For example when I first opened firefox there is a portion of middle screen where pixels are frozen to firefox ui and even if I open another application, they still dont refresh and show firefox ui. Its gone now. I think its mainly because I removed xdg-desktop-portal-gnome

Unfortunately gnome wayland has freezes like before and also I found a weird solution as to how to dodge it. After booting and sddm appears instead of typing correct password and then pressing enter which causes freezing sometimes I just press login which gives me login failed prompt and then when I enter correct password, wayland login works without any freeze. I booted and testing for like 10 times and everytime in worked and before that I get freezes like one in three times so I dont know why.

I am guessing its because of xdg-desktop-portal-gnome mainly and I will try to install those uninstalled things and uninstall only xdg-desktop-portal-gnome and see if the situation is same.

Meanwhile here is is the log which I generated using

sudo journalctl -D /var/log/journal -b | curl -F 'file=@-' 0x0.st
http://0x0.st/XrZ4.txt

0x0.st/XrZ4.txt

freewick · 2024-03-17 23:35:06

@hlechner. Thanks for the info. I initially started having this issue when I upgraded from gnome 43 to gnome 44 and unable to completely login.

At that time I used GDM as my login manager but still had freezes 100% of time. Then I installed KDE without SDDM and then after that I used KDE as my main DE and then for some reason Gnome started working again may be after 45 update. So I think may be login screen is not the solution? I will install GDM and see if It fixes my problem.

freewick · 2024-03-18 00:01:22

Update:

Omg I just switched to gdm and logged in and rebooted like 10 times not even once the login froze. I even installed all the uninstall application which @seth sugggested and even installed xdg-desktop-portal-gnome and not a single freeze. I dont know why. @hlechner thank you so much.

So the problem is SDDM or uninstalling and reinstalling packages? I dont know. For now I didnt get any freezes and I will use it for a day or two and then update the post and mark it as solved. But why I still dont know. Also the GDM shows less options compared to SDDM like no duplicates of DEs. So is SDDM the issue?

seth · 2024-03-18 00:08:05

If. Iff. IFFF gnome requires to be started by GDM then the only problem here is gnome.
It'd be peak gnome condition, but structurally insane.

One huge difference wrt your findings in #22 is that GDM defaults to wayland while SDDM defaults to X11. You could try to change the latter https://wiki.archlinux.org/title/SDDM#Wayland or the former https://wiki.archlinux.org/title/GDM#Use_Xorg_backend to see whether that's any relevant.

Have you tried SDDM after restoring the system?
The colliding network services might have been an issue.

Arch Linux

#1 2024-03-15 02:26:16

[Solved] Gnome freezes sometimes after typing password after login

#2 2024-03-15 08:55:12

Re: [Solved] Gnome freezes sometimes after typing password after login

#3 2024-03-16 11:22:58

Re: [Solved] Gnome freezes sometimes after typing password after login

#4 2024-03-16 11:41:19

Re: [Solved] Gnome freezes sometimes after typing password after login

#5 2024-03-16 14:58:18

Re: [Solved] Gnome freezes sometimes after typing password after login

#6 2024-03-16 17:10:02

Re: [Solved] Gnome freezes sometimes after typing password after login

#7 2024-03-16 17:21:58

Re: [Solved] Gnome freezes sometimes after typing password after login

#8 2024-03-16 22:31:57

Re: [Solved] Gnome freezes sometimes after typing password after login

#9 2024-03-16 22:45:35

Re: [Solved] Gnome freezes sometimes after typing password after login

#10 2024-03-16 23:30:25

Re: [Solved] Gnome freezes sometimes after typing password after login

#11 2024-03-16 23:41:44

Re: [Solved] Gnome freezes sometimes after typing password after login

#12 2024-03-17 00:04:48

Re: [Solved] Gnome freezes sometimes after typing password after login

#13 2024-03-17 00:23:43

Re: [Solved] Gnome freezes sometimes after typing password after login

#14 2024-03-17 00:33:44

Re: [Solved] Gnome freezes sometimes after typing password after login

#15 2024-03-17 00:53:57

Re: [Solved] Gnome freezes sometimes after typing password after login

#16 2024-03-17 12:24:13

Re: [Solved] Gnome freezes sometimes after typing password after login

#17 2024-03-17 14:36:28

Re: [Solved] Gnome freezes sometimes after typing password after login

#18 2024-03-17 15:34:30

Re: [Solved] Gnome freezes sometimes after typing password after login

#19 2024-03-17 15:43:31

Re: [Solved] Gnome freezes sometimes after typing password after login

#20 2024-03-17 22:16:19

Re: [Solved] Gnome freezes sometimes after typing password after login

#21 2024-03-17 22:25:55

Re: [Solved] Gnome freezes sometimes after typing password after login

#22 2024-03-17 23:26:22

Re: [Solved] Gnome freezes sometimes after typing password after login

#23 2024-03-17 23:35:06

Re: [Solved] Gnome freezes sometimes after typing password after login

#24 2024-03-18 00:01:22

Re: [Solved] Gnome freezes sometimes after typing password after login

#25 2024-03-18 00:08:05

Re: [Solved] Gnome freezes sometimes after typing password after login

Board footer