Arch Linux

otacmilutin

Member

Registered: 2017-05-15

Posts: 25

Re: Troubles after update Arch.

echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

otacmilutin

Member

Registered: 2017-05-15

Posts: 25

Re: Troubles after update Arch.

MOZ_ENABLE_WAYLAND=0 firefox opened FF immediately! (Cached?)

MOZ_ENABLE_WAYLAND=1 firefox also almost immediately opened FF (but a bit slower).

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,157

Re: Troubles after update Arch.

Why? That's from september 20th - we want to know what's wrong w/ the system *now*

---

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

otacmilutin

Member

Registered: 2017-05-15

Posts: 25

Re: Troubles after update Arch.

Due to comparison.

I already sent journal slice of now:
I'm sending again latest slice:

sudo journalctl -b | curl -F 'file=@-' 0x0.st
http://0x0.st/KBQ4.txt

otacmilutin

Member

Registered: 2017-05-15

Posts: 25

Re: Troubles after update Arch.

VS Code looks a little odd, but works fine.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,157

Re: Troubles after update Arch.

Sep 28 19:34:43 asus-laptop bash[517]: + for i in /usr/lib/modules/[0-9]*
Sep 28 19:34:43 asus-laptop bash[517]: + [[ 6.12.49-1-lts = 6\.16\.8\-arch3\-1 ]]
Sep 28 19:34:43 asus-laptop bash[517]: + pacman -Qo /usr/lib/modules/6.12.49-1-lts

What is that?
It's gonna take a moment for sure and in the older boot runs much later.
The boot is pretty slow (~30s) but was so on September 12th as well

Sep 28 19:34:57 asus-laptop systemd-logind[520]: New session '1' of user 'gdm-greeter' with class 'greeter' and type 'wayland'.
Sep 28 19:35:01 asus-laptop systemd-logind[520]: New session '2' of user 'gdm-greeter' with class 'manager-early' and type 'unspecified'.
Sep 28 19:38:01 asus-laptop systemd[1]: Reached target Multi-User System.
Sep 28 19:38:01 asus-laptop systemd[1]: Reached target Graphical Interface.
Sep 28 19:38:27 asus-laptop systemd-logind[520]: New session '3' of user 'atodorovic' with class 'user' and type 'wayland'.
Sep 28 19:38:27 asus-laptop systemd-logind[520]: New session '4' of user 'atodorovic' with class 'manager' and type 'unspecified'.

It's however 3½ minutes from the GDM start to your login which, again

Sep 12 10:25:43 asus-laptop systemd-logind[536]: New session 1 of user gdm.
Sep 12 10:25:46 asus-laptop systemd-logind[536]: New session 2 of user gdm.
Sep 12 10:29:25 asus-laptop systemd[1]: Reached target Multi-User System.
Sep 12 10:29:25 asus-laptop systemd[1]: Reached target Graphical Interface.
Sep 12 10:28:06 asus-laptop systemd-logind[536]: New session 3 of user atodorovic.
Sep 12 10:28:06 asus-laptop systemd-logind[536]: New session 4 of user atodorovic.

nothing different back then.

=> https://wiki.archlinux.org/title/Improv … ot_process

When testing firefox, "firefox" by default will only spawn a new window when there's a running instance.
You'll either have to "killall firefox" or run "firefox -no-remote"

---

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

otacmilutin

Member

Registered: 2017-05-15

Posts: 25

Re: Troubles after update Arch.

Thanks so much for hints and for your time.

Obviously something odd happens with my computer. Before after turn on laptop (arch linux) black screen with blinking cursor took not longer than few. Now I can count 20s during nothing happens before black screen with cursor (terminal on startup) even start blinking. I looked in journal before (even years before and there was a lot of errors - usually after updates what asked "manual interventions", but I succeed to manage it somehow.
Wayland is something I used newer before. (Zero experience).
I have no idea how and why when I count during system up, now tool longer time than before even journal shows different.

Can you help me to make decision: Reinstall arch on current laptop or install arch on much stronger desktop computer which is now under Windows).

Device name	DESKTOP-XXXXXX
Processor	AMD Ryzen 9 3900X 12-Core Processor             (3.80 GHz)
Installed RAM	64.0 GB
Device ID	XXXXXXXXXX
Product ID	XXXXXXXXXX
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display


Edition	Windows 11 Pro
Version	24H2
Installed on	13/12/2024
OS build	26100.4946
Experience	Windows Feature Experience Pack 1000.26100.197.0

I need a both OS on separate machines. So, I can switch Win on laptop and Arch on desktop but I'm a little confused will be win even be able to work on so old hardware I have on laptop?

For now I will run again system update to check if something new updated in arch packages.

Thanks again for your help. I'm going step by step again trough your hints and links you sent me and will try to figure out what happening exactly, (but slow load is not so big problem for me because I usually using both Win and Arch for coding (not gaming at all). Much important is: apps works fine now as before).

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,157

Re: Troubles after update Arch.

I'd suggest to check systemd-analyze to figure what's stalling the boot.
I don't think the problem is your HW being too weak and while uncomposited X11 will typically perform better (require less battery) than any wayland compositor, gnome/wayland should™ outperform gnome/x11

---

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

otacmilutin

Member

Registered: 2017-05-15

Posts: 25

Re: Troubles after update Arch.

It seems you are right.
Something makes startup very slow. (slower than numbers shows).
Today appeared popup after system up:

Fcitx it is recommended to install input Method Panel Gnome Shell extension

yay -S fcitx fcitx-mozc
Sync Explicit (2): fcitx-4.2.9.9-4, fcitx-mozc-2.26.4360.102.gca82d39-2
resolving dependencies...
looking for conflicting packages...
:: fcitx-4.2.9.9-4 and fcitx5-5.1.14-1 are in conflict. Remove fcitx5? [y/N] ^C

systemd-analyze
Startup finished in 2.688s (firmware) + 21.079s (loader) + 3.349s (kernel) + 4min 43.520s (userspace) = 5min 10.638s 
graphical.target reached after 4min 43.520s in userspace.

systemd-analyze blame
3min 48.193s docker.service
3min 24.335s linux-modules-cleanup.service
     26.711s containerd.service
     21.135s php-fpm.service
     12.917s systemd-journal-flush.service
     10.477s dev-sdb2.device
      8.943s postgresql.service
      8.774s NetworkManager-wait-online.service
      4.957s network-restart.service
      4.917s NetworkManager.service
      4.712s systemd-modules-load.service
      3.545s accounts-daemon.service
      3.476s systemd-resolved.service
      3.248s systemd-tmpfiles-setup-dev-early.service
      2.889s ntpd.service
      2.693s udisks2.service
      2.634s upower.service
lines 1-17...skipping...
3min 48.193s docker.service
3min 24.335s linux-modules-cleanup.service
     26.711s containerd.service
     21.135s php-fpm.service
     12.917s systemd-journal-flush.service
     10.477s dev-sdb2.device
      8.943s postgresql.service
      8.774s NetworkManager-wait-online.service
      4.957s network-restart.service
      4.917s NetworkManager.service
      4.712s systemd-modules-load.service
      3.545s accounts-daemon.service
      3.476s systemd-resolved.service
      3.248s systemd-tmpfiles-setup-dev-early.service
      2.889s ntpd.service
      2.693s udisks2.service
      2.634s upower.service
      2.503s systemd-vconsole-setup.service
lines 1-18...skipping...
3min 48.193s docker.service
3min 24.335s linux-modules-cleanup.service
     26.711s containerd.service
     21.135s php-fpm.service
     12.917s systemd-journal-flush.service
     10.477s dev-sdb2.device
      8.943s postgresql.service
      8.774s NetworkManager-wait-online.service
      4.957s network-restart.service
      4.917s NetworkManager.service
      4.712s systemd-modules-load.service
      3.545s accounts-daemon.service
      3.476s systemd-resolved.service
      3.248s systemd-tmpfiles-setup-dev-early.service
      2.889s ntpd.service
      2.693s udisks2.service
      2.634s upower.service
      2.503s systemd-vconsole-setup.service
      2.225s redis.service
lines 1-19...skipping...
3min 48.193s docker.service
3min 24.335s linux-modules-cleanup.service
     26.711s containerd.service
     21.135s php-fpm.service
     12.917s systemd-journal-flush.service
     10.477s dev-sdb2.device
      8.943s postgresql.service
      8.774s NetworkManager-wait-online.service
      4.957s network-restart.service
      4.917s NetworkManager.service
      4.712s systemd-modules-load.service
      3.545s accounts-daemon.service
      3.476s systemd-resolved.service
      3.248s systemd-tmpfiles-setup-dev-early.service
      2.889s ntpd.service
      2.693s udisks2.service
      2.634s upower.service
      2.503s systemd-vconsole-setup.service
      2.225s redis.service
      2.167s polkit.service
lines 1-20...skipping...
3min 48.193s docker.service
3min 24.335s linux-modules-cleanup.service
     26.711s containerd.service
     21.135s php-fpm.service
     12.917s systemd-journal-flush.service
     10.477s dev-sdb2.device
      8.943s postgresql.service
      8.774s NetworkManager-wait-online.service
      4.957s network-restart.service
      4.917s NetworkManager.service
      4.712s systemd-modules-load.service
      3.545s accounts-daemon.service
      3.476s systemd-resolved.service
      3.248s systemd-tmpfiles-setup-dev-early.service
      2.889s ntpd.service
      2.693s udisks2.service
      2.634s upower.service
      2.503s systemd-vconsole-setup.service
      2.225s redis.service
      2.167s polkit.service
      2.025s systemd-udevd.service
lines 1-21...skipping...
3min 48.193s docker.service
3min 24.335s linux-modules-cleanup.service
     26.711s containerd.service
     21.135s php-fpm.service
     12.917s systemd-journal-flush.service
     10.477s dev-sdb2.device
      8.943s postgresql.service
      8.774s NetworkManager-wait-online.service
      4.957s network-restart.service
      4.917s NetworkManager.service
      4.712s systemd-modules-load.service
      3.545s accounts-daemon.service
      3.476s systemd-resolved.service
      3.248s systemd-tmpfiles-setup-dev-early.service
      2.889s ntpd.service
      2.693s udisks2.service
      2.634s upower.service
      2.503s systemd-vconsole-setup.service
      2.225s redis.service
      2.167s polkit.service
      2.025s systemd-udevd.service
      1.445s systemd-backlight@leds:asus::kbd_backlight.service
lines 1-22

No big deal, arch still working.

Thanks!

Last edited by otacmilutin (2025-09-30 07:19:35)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,157

Re: Troubles after update Arch.

Seems to be https://archlinux.org/packages/extra/an … ules-hook/ ?
Also please don't copy and paste out of the pager

systemd-analyze blame --no-pager

and oc

systemd-analyze plot | curl -F 'file=@-' 0x0.st

will give fancy graphics

---

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

otacmilutin

Member

Registered: 2017-05-15

Posts: 25

Re: Troubles after update Arch.

Huh, it seems nginx must be for this?!

systemd-analyze plot | curl -F 'file=@-' 0x0.st
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 69,157

Re: Troubles after update Arch.

No, good god
502 is a server error message from 0x0.st
Try again - if it doesn't work, "systemd-analyze plot > some.svg" and upload that wherever you can.

---

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