Tooks 2m47s from the time I enter password in GDM to see dekstop backg

kolana · 2022-03-24 23:44:09

Hi, I noticed recently that arch tooks exactly 2 minutes and 47 secondes (tested 3 times) from the time I enter password in GDM to see dekstop background.

When I hibernate my PC this issues doesn't happen at all. Only when shutdown/restart.

It happens only with xorg (wayland works fine)

This is systemd-analyze output. I know it doesn't calculate the time from entering password in GDM to see dekstop background, but just in case you need it.

Startup finished in 8.783s (firmware) + 998ms (loader) + 13.753s (kernel) + 56.007s (userspace) = 1min 19.543s 
graphical.target reached after 56.007s in userspace

This is output of journalct -xb -p 0..3

Mar 24 21:14:06  kernel: snd_hda_intel 0000:08:00.1: no codecs found!
Mar 24 21:14:06  kernel: leds dell::kbd_backlight: Setting an LED's brightness failed (-5)
Mar 24 21:14:06  kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
Mar 24 21:13:44  systemd-modules-load[325]: Failed to find module 'vboxdrv\nvboxnetflt\nvboxnetadp\nvboxpci'
Mar 24 21:14:18  kernel: usb 2-3: Device is not authorized for usage
Mar 24 21:14:31  kernel: snd_hda_intel 0000:08:00.1: can't change power state from D3cold to D0 (config space inaccessible)
Mar 24 21:14:31  kernel: snd_hda_intel 0000:08:00.1: can't change power state from D3cold to D0 (config space inaccessible)
Mar 24 21:14:32  kernel: snd_hda_intel 0000:08:00.1: can't change power state from D3cold to D0 (config space inaccessible)
Mar 24 21:14:32  libvirtd[917]: internal error:  PCI header type '127' for device '0000:08:00.1'
Mar 24 21:14:32  kernel: snd_hda_intel 0000:08:00.1: can't change power state from D3cold to D0 (config space inaccessible)
Mar 24 21:14:33  kernel: snd_hda_intel 0000:08:00.1: can't change power state from D3cold to D0 (config space inaccessible)
Mar 24 21:14:40  gnome-session-binary[3824]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Mar 24 21:14:40  gnome-session-binary[3824]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Mar 24 21:15:28  bluetoothd[592]: Failed to set mode: Blocked through rfkill (0x12)
Mar 24 21:16:37  gdm-password][4541]: gkr-pam: unable to locate daemon control file
Mar 24 21:19:23  gdm-launch-environment][2833]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

I noticed weired thing:

In xorg notice the long time between these 2 entries:

Mar 24 21:16:37  gdm-password][4541]: gkr-pam: unable to locate daemon control file
Mar 24 21:19:23  gdm-launch-environment][2833]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

In wayland notice the small time between these 2 entries:

Mar 24 23:08:39 Unknown gdm-password][4526]: gkr-pam: unable to locate daemon control file
Mar 24 23:08:51 Unknown gdm-launch-environment][2042]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

If you need anything else tell me !

seth · 2022-03-25 07:12:30

This is output of journalct -xb -p 0..3

"sudo journalctl -b", no -x, no filter.

It happens only with xorg (wayland works fine)

https://wiki.archlinux.org/title/GDM#Use_Xorg_backend ?

dekstop background … dekstop background

"desktop" - the top of your desk, not the stop of your (misspelled) deck…

kolana · 2022-03-25 15:09:57

any solution ?

V1del · 2022-03-25 15:18:06

You got asked for more telling log information and a config change you could try that might have an influence. You didn't do either, why not?

kolana · 2022-03-25 22:21:20

What are you talking about ??

V1del · 2022-03-25 22:29:58

seth wrote:

This is output of journalct -xb -p 0..3
"sudo journalctl -b", no -x, no filter.
It happens only with xorg (wayland works fine)
https://wiki.archlinux.org/title/GDM#Use_Xorg_backend ?

you didn't post the log nor mentioned whether you tried to configure GDM to explicitly start a xorg session itself.

Last edited by V1del (2022-03-25 22:30:22)

kolana · 2022-03-30 10:16:15

Yeah, It tried to configure GDM to explicitly to start a xorg session itself with no luck.

Here is full log https://pastebin.com/t2GSuP8t (sorry if been late)

Last edited by kolana (2022-03-30 10:16:29)

seth · 2022-03-30 10:51:55

seth wrote:

no -x

…

Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [13] INFO: # Xorg post-start hook
Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [90] INFO: Running /etc/optimus-manager/xsetup-integrated.sh
Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [118] INFO: Writing state {'type': 'done', 'switch_id': '20220324T211426', 'current_mode': 'integrated'}
Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [119] INFO: Xorg post-start hook completed successfully.
Mar 24 21:16:43  /usr/lib/gdm-x-session[4619]: /etc/gdm/Xsession: Beginning session setup...
Mar 24 21:16:44  /usr/lib/gdm-x-session[4627]: localuser:user being added to access control list

Mar 24 21:17:44  xbrlapi.desktop[4505]: openConnection: connect: No such file or directory
Mar 24 21:17:44  xbrlapi.desktop[4505]: cannot connect to braille devices daemon brltty at :0
Mar 24 21:18:54  /usr/lib/gdm-x-session[4619]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session
Mar 24 21:18:54  dbus-daemon[4610]: [session uid=1000 pid=4610] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.4' (uid=1000 pid=4791 comm="/usr/lib/gnome-session-check-accelerated")
Mar 24 21:18:54  dbus-daemon[4610]: [session uid=1000 pid=4610] Successfully activated service 'org.a11y.Bus'
Mar 24 21:18:54  systemd[4564]: Starting Accessibility services bus...
Mar 24 21:18:54  systemd[4564]: Started Accessibility services bus.
Mar 24 21:18:55  systemd[4564]: Created slice Slice /app/gnome-session-manager.
Mar 24 21:18:55  systemd[4564]: Reached target GNOME X11 Session.
Mar 24 21:18:55  systemd[4564]: Reached target Session services which should run early before the graphical session is brought up.
Mar 24 21:18:55  systemd[4564]: Reached target GNOME Shell.
Mar 24 21:18:55  systemd[4564]: Starting Monitor Session leader for GNOME Session...
Mar 24 21:18:55  systemd[4564]: Started Monitor Session leader for GNOME Session.
Mar 24 21:18:55  systemd[4564]: Reached target Tasks to be run before GNOME Session starts.
Mar 24 21:18:55  systemd[4564]: Starting GNOME Session Manager (session: gnome)...
Mar 24 21:18:55  gnome-session[4814]: gnome-session-binary[4814]: WARNING: Could not parse desktop file Tom.desktop or it references a not found TryExec binary
Mar 24 21:18:55  gnome-session-binary[4814]: WARNING: Could not parse desktop file Tom.desktop or it references a not found TryExec binary
Mar 24 21:18:55  gnome-keyring-d[4823]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  gnome-keyring-daemon[4823]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  gnome-keyring-d[4826]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  gnome-keyring-daemon[4826]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  systemd[4564]: Started Application launched by gnome-session-binary.
Mar 24 21:18:55  systemd[4564]: Started Application launched by gnome-session-binary.
Mar 24 21:18:55  systemd[4564]: Started Application launched by gnome-session-binary.
Mar 24 21:18:55  gnome-keyring-secrets.desktop[4826]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Mar 24 21:18:55  systemd[4564]: Started GNOME Session Manager (session: gnome).
Mar 24 21:18:55  systemd[4564]: Reached target GNOME Session Manager is ready.
Mar 24 21:18:55  gnome-keyring-ssh.desktop[4829]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Mar 24 21:18:55  systemd[4564]: Starting GNOME Shell on Wayland...
Mar 24 21:18:55  systemd[4564]: Starting GNOME Shell on X11...
Mar 24 21:18:55  systemd[4564]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
Mar 24 21:18:55  systemd[4564]: Condition check resulted in GNOME Shell on Wayland being skipped.
Mar 24 21:18:55  gnome-shell[4835]: Running GNOME Shell (using mutter 41.4) as a X11 window and compositing manager

I'm gonna blame

Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [90] INFO: Running /etc/optimus-manager/xsetup-integrated.sh

- why is that executed *after* the X11 server starts?

V1del · 2022-03-30 10:56:31

Probably https://github.com/Askannz/optimus-mana … -gdm-users and thus lacking the relevant proper hooking spots?

kolana · 2022-03-30 22:42:03

V1del wrote:

Probably https://github.com/Askannz/optimus-mana … -gdm-users and thus lacking the relevant proper hooking spots?

Optimus manager was working fine for a long period of time with gdm-prime...

kolana · 2022-03-30 22:43:47

seth wrote:

no -x

…

Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [13] INFO: # Xorg post-start hook
Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [90] INFO: Running /etc/optimus-manager/xsetup-integrated.sh
Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [118] INFO: Writing state {'type': 'done', 'switch_id': '20220324T211426', 'current_mode': 'integrated'}
Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [119] INFO: Xorg post-start hook completed successfully.
Mar 24 21:16:43  /usr/lib/gdm-x-session[4619]: /etc/gdm/Xsession: Beginning session setup...
Mar 24 21:16:44  /usr/lib/gdm-x-session[4627]: localuser:user being added to access control list

Mar 24 21:17:44  xbrlapi.desktop[4505]: openConnection: connect: No such file or directory
Mar 24 21:17:44  xbrlapi.desktop[4505]: cannot connect to braille devices daemon brltty at :0
Mar 24 21:18:54  /usr/lib/gdm-x-session[4619]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session
Mar 24 21:18:54  dbus-daemon[4610]: [session uid=1000 pid=4610] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.4' (uid=1000 pid=4791 comm="/usr/lib/gnome-session-check-accelerated")
Mar 24 21:18:54  dbus-daemon[4610]: [session uid=1000 pid=4610] Successfully activated service 'org.a11y.Bus'
Mar 24 21:18:54  systemd[4564]: Starting Accessibility services bus...
Mar 24 21:18:54  systemd[4564]: Started Accessibility services bus.
Mar 24 21:18:55  systemd[4564]: Created slice Slice /app/gnome-session-manager.
Mar 24 21:18:55  systemd[4564]: Reached target GNOME X11 Session.
Mar 24 21:18:55  systemd[4564]: Reached target Session services which should run early before the graphical session is brought up.
Mar 24 21:18:55  systemd[4564]: Reached target GNOME Shell.
Mar 24 21:18:55  systemd[4564]: Starting Monitor Session leader for GNOME Session...
Mar 24 21:18:55  systemd[4564]: Started Monitor Session leader for GNOME Session.
Mar 24 21:18:55  systemd[4564]: Reached target Tasks to be run before GNOME Session starts.
Mar 24 21:18:55  systemd[4564]: Starting GNOME Session Manager (session: gnome)...
Mar 24 21:18:55  gnome-session[4814]: gnome-session-binary[4814]: WARNING: Could not parse desktop file Tom.desktop or it references a not found TryExec binary
Mar 24 21:18:55  gnome-session-binary[4814]: WARNING: Could not parse desktop file Tom.desktop or it references a not found TryExec binary
Mar 24 21:18:55  gnome-keyring-d[4823]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  gnome-keyring-daemon[4823]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  gnome-keyring-d[4826]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  gnome-keyring-daemon[4826]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Mar 24 21:18:55  systemd[4564]: Started Application launched by gnome-session-binary.
Mar 24 21:18:55  systemd[4564]: Started Application launched by gnome-session-binary.
Mar 24 21:18:55  systemd[4564]: Started Application launched by gnome-session-binary.
Mar 24 21:18:55  gnome-keyring-secrets.desktop[4826]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Mar 24 21:18:55  systemd[4564]: Started GNOME Session Manager (session: gnome).
Mar 24 21:18:55  systemd[4564]: Reached target GNOME Session Manager is ready.
Mar 24 21:18:55  gnome-keyring-ssh.desktop[4829]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Mar 24 21:18:55  systemd[4564]: Starting GNOME Shell on Wayland...
Mar 24 21:18:55  systemd[4564]: Starting GNOME Shell on X11...
Mar 24 21:18:55  systemd[4564]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'.
Mar 24 21:18:55  systemd[4564]: Condition check resulted in GNOME Shell on Wayland being skipped.
Mar 24 21:18:55  gnome-shell[4835]: Running GNOME Shell (using mutter 41.4) as a X11 window and compositing manager

I'm gonna blame

Mar 24 21:16:43  /usr/lib/gdm-x-session[4613]: [90] INFO: Running /etc/optimus-manager/xsetup-integrated.sh

- why is that executed *after* the X11 server starts?

I really have no idea..

kolana · 2022-03-30 22:45:00

Also recently I got "The login keyring did not get unlocked when you logged into your computer" message frequently on Gnome.

This message and this topic problem came out along.

EDIT: I removed optimus manager and gdm-prime with no luck too.

Last edited by kolana (2022-03-30 23:03:01)

seth · 2022-03-31 07:16:02

Post an updated system journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st
journalctl --user -b | curl -F 'file=@-' 0x0.st # session journal for isolating filter

iqwoo · 2022-03-31 08:08:32

I've the same problem, GDM is taking long to login (more or less a minute).
I also noticed the gkr-pam and gdm-launch-enviroment errors.

seth · 2022-03-31 08:17:47

#1 illustrates the difference in delay between those two messages, but they both appear in the ("good") wayland context as well, so they're not indicative of the problem, but merely markers around the delay.

See and post the output for #13

kolana · 2022-03-31 13:11:17

seth wrote:

Post an updated system journal

sudo journalctl -b | curl -F 'file=@-' 0x0.st
journalctl --user -b | curl -F 'file=@-' 0x0.st # session journal for isolating filter

1st one https://pastebin.com/H8gdqMCh
2nd one https://pastebin.com/imSpUCVd

I Uploaded here for expiration...

Last edited by kolana (2022-03-31 13:12:27)

kolana · 2022-03-31 13:11:48

iqwoo wrote:

I've the same problem, GDM is taking long to login (more or less a minute).
I also noticed the gkr-pam and gdm-launch-enviroment errors.

Is you drive SSD ?

seth · 2022-03-31 13:44:07

EDIT: I removed optimus manager and gdm-prime with no luck too.

Mar 31 13:51:24 Unknown /usr/lib/gdm-x-session[4674]: [88] INFO: Running /etc/optimus-manager/xsetup-integrated.sh

…

Mar 31 13:51:24 Unknown /usr/lib/gdm-x-session[4680]: /etc/gdm/Xsession: Beginning session setup...
Mar 31 13:51:24 Unknown /usr/lib/gdm-x-session[4688]: localuser:user being added to access control list

Mar 31 13:51:26 Unknown systemd[4625]: espanso.service: Scheduled restart job, restart counter is at 1.
Mar 31 13:51:26 Unknown systemd[4625]: Stopped espanso daemon.
Mar 31 13:51:26 Unknown systemd[4625]: Started espanso daemon.
Mar 31 13:51:26 Unknown espanso[4692]: 13:51:26 [daemon(4692)] [INFO] reading configs from: "/home/user/.config/espanso"
…
Mar 31 13:51:26 Unknown espanso[4700]: 13:51:26 [worker(4700)] [ERROR] Unable to show notification: The name org.freedesktop.Notifications was not provided by any .service files

Mar 31 13:51:40 Unknown systemd[1]: systemd-localed.service: Deactivated successfully.
Mar 31 13:51:40 Unknown systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Mar 31 13:51:40 Unknown kernel: kauditd_printk_skb: 5 callbacks suppressed
…
Mar 31 13:52:02 Unknown geoclue[4449]: Service not used for 60 seconds. Shutting down..
Mar 31 13:52:02 Unknown systemd[1]: geoclue.service: Deactivated successfully.
…
Mar 31 13:52:03 Unknown kernel: audit: type=1131 audit(1648731123.892:243): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 13:53:19 Unknown xbrlapi.desktop[4584]: openConnection: connect: No such file or directory
Mar 31 13:53:19 Unknown xbrlapi.desktop[4584]: cannot connect to braille devices daemon brltty at :0

Mar 31 13:53:34 Unknown /usr/lib/gdm-x-session[4680]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session

So there's a massive gap before the xbrlapi.desktop error (whichi is an X11 exclusive service) and also some unaccounted gaps, but the espanse error makes me nervous (since it might be prone to trigger a 25s dbus timeout) which also looks like there's no wayland support.

=> Disable/remove those two services (from autostart) and monitor the impact.

iqwoo · 2022-03-31 13:55:42

kolana wrote:

iqwoo wrote:
I've the same problem, GDM is taking long to login (more or less a minute).
I also noticed the gkr-pam and gdm-launch-enviroment errors.
Is you drive SSD ?

Boot ("/boot") root ("/") and home ("/home") are on two different partiotion on a nvme drive.
I also have two HDD with some partitions mounted on /mnt/something

Last edited by iqwoo (2022-03-31 13:55:56)

kolana · 2022-03-31 20:06:43

seth wrote:

EDIT: I removed optimus manager and gdm-prime with no luck too.

Mar 31 13:51:24 Unknown /usr/lib/gdm-x-session[4674]: [88] INFO: Running /etc/optimus-manager/xsetup-integrated.sh

…

Mar 31 13:51:24 Unknown /usr/lib/gdm-x-session[4680]: /etc/gdm/Xsession: Beginning session setup...
Mar 31 13:51:24 Unknown /usr/lib/gdm-x-session[4688]: localuser:user being added to access control list

Mar 31 13:51:26 Unknown systemd[4625]: espanso.service: Scheduled restart job, restart counter is at 1.
Mar 31 13:51:26 Unknown systemd[4625]: Stopped espanso daemon.
Mar 31 13:51:26 Unknown systemd[4625]: Started espanso daemon.
Mar 31 13:51:26 Unknown espanso[4692]: 13:51:26 [daemon(4692)] [INFO] reading configs from: "/home/user/.config/espanso"
…
Mar 31 13:51:26 Unknown espanso[4700]: 13:51:26 [worker(4700)] [ERROR] Unable to show notification: The name org.freedesktop.Notifications was not provided by any .service files

Mar 31 13:51:40 Unknown systemd[1]: systemd-localed.service: Deactivated successfully.
Mar 31 13:51:40 Unknown systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Mar 31 13:51:40 Unknown kernel: kauditd_printk_skb: 5 callbacks suppressed
…
Mar 31 13:52:02 Unknown geoclue[4449]: Service not used for 60 seconds. Shutting down..
Mar 31 13:52:02 Unknown systemd[1]: geoclue.service: Deactivated successfully.
…
Mar 31 13:52:03 Unknown kernel: audit: type=1131 audit(1648731123.892:243): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg='unit=libvirtd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 31 13:53:19 Unknown xbrlapi.desktop[4584]: openConnection: connect: No such file or directory
Mar 31 13:53:19 Unknown xbrlapi.desktop[4584]: cannot connect to braille devices daemon brltty at :0

Mar 31 13:53:34 Unknown /usr/lib/gdm-x-session[4680]: /etc/gdm/Xsession: Setup done, will execute: /usr/bin/gnome-session

So there's a massive gap before the xbrlapi.desktop error (whichi is an X11 exclusive service) and also some unaccounted gaps, but the espanse error makes me nervous (since it might be prone to trigger a 25s dbus timeout) which also looks like there's no wayland support.

=> Disable/remove those two services (from autostart) and monitor the impact.

For optimus-manager, I removed and tested it then I reinstalled it again that's why it's on log there.

What is the other service other than espanso to disable ?? xbrlapi doesn't have any service..

kolana · 2022-03-31 20:07:52

iqwoo wrote:

kolana wrote:
iqwoo wrote:
I've the same problem, GDM is taking long to login (more or less a minute).
I also noticed the gkr-pam and gdm-launch-enviroment errors.
Is you drive SSD ?
Boot ("/boot") root ("/") and home ("/home") are on two different partiotion on a nvme drive.
I also have two HDD with some partitions mounted on /mnt/something

Ok, thanks just wondered why it took me 2m47s and you more or less a minute.

seth · 2022-03-31 20:39:41

What is the other service other than espanso to disable ?? xbrlapi doesn't have any service..

https://wiki.archlinux.org/title/Autost … nt_startup

kolana · 2022-03-31 20:56:25

seth wrote:

What is the other service other than espanso to disable ?? xbrlapi doesn't have any service..
https://wiki.archlinux.org/title/Autost … nt_startup

I know that stuff. I asked for what service name to disable ??

seth · 2022-03-31 21:06:42

xbrlapi ??

Edit: sanity check. Since there's no package in the repos and none that I can find in the AUR: how did you install xbrlapi ?

Last edited by seth (2022-03-31 21:08:29)

kolana · 2022-03-31 21:14:00

seth wrote:

xbrlapi ??
Edit: sanity check. Since there's no package in the repos and none that I can find in the AUR: how did you install xbrlapi ?

There is no service named xbrlapi

/usr/bin/xbrlapi is owned by brltty 6.4-9

Arch Linux

#1 2022-03-24 23:44:09

Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#2 2022-03-25 07:12:30

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#3 2022-03-25 15:09:57

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#4 2022-03-25 15:18:06

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#5 2022-03-25 22:21:20

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#6 2022-03-25 22:29:58

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#7 2022-03-30 10:16:15

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#8 2022-03-30 10:51:55

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#9 2022-03-30 10:56:31

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#10 2022-03-30 22:42:03

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#11 2022-03-30 22:43:47

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#12 2022-03-30 22:45:00

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#13 2022-03-31 07:16:02

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#14 2022-03-31 08:08:32

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#15 2022-03-31 08:17:47

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#16 2022-03-31 13:11:17

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#17 2022-03-31 13:11:48

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#18 2022-03-31 13:44:07

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#19 2022-03-31 13:55:42

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#20 2022-03-31 20:06:43

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#21 2022-03-31 20:07:52

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#22 2022-03-31 20:39:41

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#23 2022-03-31 20:56:25

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#24 2022-03-31 21:06:42

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

#25 2022-03-31 21:14:00

Re: Tooks 2m47s from the time I enter password in GDM to see dekstop backg

Board footer