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

seth · 2022-03-31 21:17:23

Ah.
See /usr/share/gdm/greeter/autostart/xbrlapi.desktop

Edit: also possibly /etc/X11/xinit/xinitrc.d/90xbrlapi

Last edited by seth (2022-03-31 21:19:15)

kolana · 2022-03-31 21:24:18

/etc/X11/xinit/xinitrc.d/90xbrlapi -->

```
# startup script for /etc/X11/Xsession.d

prefix="/usr"
exec_prefix="${prefix}"
program_directory="${exec_prefix}/bin"
xbrlapi="$program_directory/xbrlapi"
brltty="$program_directory/brltty"

if [ -x "${xbrlapi}" ]; then
if "${xbrlapi}" 2>/dev/null ; then
# xbrlapi could connect to BrlAPI, try to start brltty with AtSpi2 driver.
if [ -x "${brltty}" ]; then
"${brltty}" -b ba -s no -x a2 -N 2>/dev/null
fi
fi
fi
```

/usr/share/gdm/greeter/autostart/xbrlapi.desktop -->
```
[Desktop Entry]
Type=Application
Name=xbrlapi
Exec=xbrlapi -q
NoDisplay=true
X-GNOME-AutoRestart=true
```

kolana · 2022-03-31 21:50:15

There is no systemctl service associated with them..

seth · 2022-04-01 06:27:28

There is no systemctl service associated with them..

No? Why do you think there would?
The idea was to get rid of that stuff…

pacman -Rs brltty

or likeöy

pacman -Rs orca

Also please use code tags, https://bbs.archlinux.org/help.php#bbcode

iqwoo · 2022-04-01 19:57:27

Removing brltty and orca didn't solve the issue.
Here my last system journal:
http://0x0.st/oqGu.txt
http://0x0.st/oqGS.txt

seth · 2022-04-01 20:20:22

apr 01 21:56:21 highgarden systemd[1499]: Queued start job for default target Main User Target.
…
apr 01 21:57:49 highgarden sudo[2878]: enrico : TTY=pts/0 ; PWD=/home/enrico ; USER=root ; COMMAND=/usr/bin/journalctl -b

There's ~90 seconds between the session start and you calling the journal.
What sticks out is obviously

apr 01 21:56:22 highgarden systemd[1499]: Reached target GNOME Session Manager is ready.
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on Wayland...
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on X11...
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Condition check resulted in GNOME Shell on X11 being skipped.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
apr 01 21:56:22 highgarden systemd[1499]: Stopped GNOME Shell on X11.
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on X11...
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Condition check resulted in GNOME Shell on X11 being skipped.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 2.
apr 01 21:56:22 highgarden systemd[1499]: Stopped GNOME Shell on X11.
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on X11...
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Condition check resulted in GNOME Shell on X11 being skipped.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 3.
apr 01 21:56:22 highgarden systemd[1499]: Stopped GNOME Shell on X11.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Start request repeated too quickly.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Started GNOME Shell on X11.
apr 01 21:56:22 highgarden gnome-shell[1582]: Running GNOME Shell (using mutter 41.5) as a Wayland display server

You're starting gnome on X11 and wayland in parallel - and X11 fails.
You're running a wayland session and there's no trace whatsoever of an X11 session in the journal. There's also no X11 log in there, so the server doesn't seem to start at all.
This is *vastly* different from the journal posted by kolana and I'd say you've either a broken xorg-server installation or some bogus xorg config.

=> Start a new thread and try to start X11 w/ startx/xinit from the multi-user.target (2nd link below, if you don't edit the xinitrc - last link below - you'll need xterm and TWM to make "startx" happen) and post the xorg log there.

kolana · 2022-04-02 11:21:26

seth wrote:

There is no systemctl service associated with them..
No? Why do you think there would?
The idea was to get rid of that stuff…
pacman -Rs brltty
or likeöy
pacman -Rs orca
Also please use code tags, https://bbs.archlinux.org/help.php#bbcode

This time it tooks only 33s

https://pastebin.com/337a6QDu
https://pastebin.com/hfASUryP

seth · 2022-04-02 13:13:41

Apr 02 12:12:58  systemd[4555]: Queued start job for default target Main User Target.
…
Apr 02 12:13:03  espanso[4591]: 12:13:03 [worker(4591)] [ERROR] Unable to block the LinuxEventLoop: receiving on an empty and disconnected channel
…
Apr 02 12:13:03  /usr/lib/gdm-x-session[4572]: X.Org X Server 1.21.1.3
…
Apr 02 12:13:06  systemd[4555]: Reached target GNOME X11 Session.
…
Apr 02 12:13:18  systemd[4555]: Reached target GNOME X11 Session (session: gnome).

The 1st 5s seem to go to "espanso" which also keeps yelling errors afterwards. Then X11 takes 3s to start (what's a lot if you're not running on a potato) and then gnome-shell does its thing and 12s after the X11 server is up gnome considers the session to be present.
So the braille thing had a massive impact - I'd now remove espanso (autostart) and see whether that also cuts down the startup time drastically.

iqwoo · 2022-04-03 07:13:30

seth wrote:

apr 01 21:56:21 highgarden systemd[1499]: Queued start job for default target Main User Target.
…
apr 01 21:57:49 highgarden sudo[2878]: enrico : TTY=pts/0 ; PWD=/home/enrico ; USER=root ; COMMAND=/usr/bin/journalctl -b
There's ~90 seconds between the session start and you calling the journal.
What sticks out is obviously
apr 01 21:56:22 highgarden systemd[1499]: Reached target GNOME Session Manager is ready.
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on Wayland...
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on X11...
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Condition check resulted in GNOME Shell on X11 being skipped.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 1.
apr 01 21:56:22 highgarden systemd[1499]: Stopped GNOME Shell on X11.
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on X11...
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Condition check resulted in GNOME Shell on X11 being skipped.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 2.
apr 01 21:56:22 highgarden systemd[1499]: Stopped GNOME Shell on X11.
apr 01 21:56:22 highgarden systemd[1499]: Starting GNOME Shell on X11...
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Condition check resulted in GNOME Shell on X11 being skipped.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 3.
apr 01 21:56:22 highgarden systemd[1499]: Stopped GNOME Shell on X11.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Start request repeated too quickly.
apr 01 21:56:22 highgarden systemd[1499]: org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.
apr 01 21:56:22 highgarden systemd[1499]: Started GNOME Shell on X11.
apr 01 21:56:22 highgarden gnome-shell[1582]: Running GNOME Shell (using mutter 41.5) as a Wayland display server
You're starting gnome on X11 and wayland in parallel - and X11 fails.
You're running a wayland session and there's no trace whatsoever of an X11 session in the journal. There's also no X11 log in there, so the server doesn't seem to start at all.
This is *vastly* different from the journal posted by kolana and I'd say you've either a broken xorg-server installation or some bogus xorg config.
=> Start a new thread and try to start X11 w/ startx/xinit from the multi-user.target (2nd link below, if you don't edit the xinitrc - last link below - you'll need xterm and TWM to make "startx" happen) and post the xorg log there.

ok... I'm not understandi why gnome is starting on X11 and wayland in parallel

kolana · 2022-04-03 10:51:54

seth wrote:

Apr 02 12:12:58  systemd[4555]: Queued start job for default target Main User Target.
…
Apr 02 12:13:03  espanso[4591]: 12:13:03 [worker(4591)] [ERROR] Unable to block the LinuxEventLoop: receiving on an empty and disconnected channel
…
Apr 02 12:13:03  /usr/lib/gdm-x-session[4572]: X.Org X Server 1.21.1.3
…
Apr 02 12:13:06  systemd[4555]: Reached target GNOME X11 Session.
…
Apr 02 12:13:18  systemd[4555]: Reached target GNOME X11 Session (session: gnome).
The 1st 5s seem to go to "espanso" which also keeps yelling errors afterwards. Then X11 takes 3s to start (what's a lot if you're not running on a potato) and then gnome-shell does its thing and 12s after the X11 server is up gnome considers the session to be present.
So the braille thing had a massive impact - I'd now remove espanso (autostart) and see whether that also cuts down the startup time drastically.

The 1st time I tested it tooks only 31s (2s gain). The 2nd time where I captured these 2 logs it's 15s 'cause a systemd error which happens frequently as I test in between.
https://pastebin.com/X9wNDBzc
https://pastebin.com/tHQASCyt

Last edited by kolana (2022-04-03 10:52:42)

iqwoo · 2022-04-03 11:36:42

seth wrote:

=> Start a new thread and try to start X11 w/ startx/xinit from the multi-user.target (2nd link below, if you don't edit the xinitrc - last link below - you'll need xterm and TWM to make "startx" happen) and post the xorg log there.

I started a new thread but it has been closed by a moderator because it's a duplicate of this thread...
Here my xorg log: http://0x0.st/obrX.json

seth · 2022-04-03 12:50:58

Apr 03 11:42:38 systemd-logind[634]: New session 3 of user user.
…
Apr 03 11:42:38 systemd[4542]: Queued start job for default target Main User Target.
…
Apr 03 11:42:42 /usr/lib/gdm-x-session[4558]: X.Org X Server 1.21.1.3
…
Apr 03 11:42:45 systemd[4542]: Reached target GNOME Shell.

It's 7s from your login to the point where gnome says "we started".
Then a bunch of tools start over the next ten seconds

Apr 03 11:42:56 systemd[4542]: Started GNOME FreeDesktop screensaver service.
Apr 03 11:42:56 systemd[4542]: Started GNOME file sharing service.
Apr 03 11:42:56 systemd[4542]: Started GNOME printer notifications service.
Apr 03 11:42:56 systemd[4542]: Started GNOME date & time service.
Apr 03 11:42:56 systemd[4542]: Started GNOME keyboard configuration service.
Apr 03 11:42:56 systemd[4542]: Started GNOME USB protection service.
Apr 03 11:42:56 systemd[4542]: Started GNOME color management service.
Apr 03 11:42:56 systemd[4542]: Started GNOME smartcard service.
Apr 03 11:42:56 systemd[4542]: Started GNOME sound sample caching service.

And

Apr 03 11:43:11 gnome-shell[4633]: Registering session with GDM

There's no outright obvious roadblock, but the system seems to perform rather slow in general?

time echo "scale=5000; a(1)*4" | bc -l

Edit, @iqwoo:
I've appealed your thread for re-opening

Last edited by seth (2022-04-03 12:53:14)

V1del · 2022-04-03 13:30:25

@seth iqwoo

Sorry about that, I reopened the other thread

Arch Linux

#26 2022-03-31 21:17:23

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

#27 2022-03-31 21:24:18

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

#28 2022-03-31 21:50:15

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

#29 2022-04-01 06:27:28

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

#30 2022-04-01 19:57:27

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

#31 2022-04-01 20:20:22

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

#32 2022-04-02 11:21:26

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

#33 2022-04-02 13:13:41

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

#34 2022-04-03 07:13:30

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

#35 2022-04-03 10:51:54

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

#36 2022-04-03 11:36:42

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

#37 2022-04-03 12:50:58

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

#38 2022-04-03 13:30:25

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

Board footer