Varen

joined 6 months ago
[–] [email protected] 1 points 2 weeks ago

It is related to the Samsung screen. There‘s a kde bug since Plasma 6.2 where this is happening. Long story short: disable ddc (look up your plasma-powerdevil.service file (mine was in /usr/lib/systemd/user) and add Environment="POWERDEVIL_NO_DDCUTIL=1" to it. Save, restart powerdevil (or reboot) and it shouldn‘t happen anymore.)

See https://bugs.kde.org/show_bug.cgi?id=494522 for reference. Hope it works

[–] [email protected] 10 points 3 months ago

Had something similar with ASUS…never again

[–] [email protected] 2 points 4 months ago* (last edited 4 months ago)

@[email protected] i found today 3-4 other persons having same or similar issues (one on the bugtracker github of systemd and 3 others on the archlinux forums) starting around the same time (in the last 2-3 weeks).

I dont think its Plasma related (which comes in later on boot I think) but maybe Kernel based - since others started having similar issue around the same time?

Might be related to some usb devices, but if i‘m not alone having it!?

[–] [email protected] 1 points 4 months ago

@[email protected] Did exactly that before posting and posted the output:

systemd-analyze critical-chain systemd-journald.service:

systemd-journald.service +7.853s └─systemd-journald.socket @428ms

[–] [email protected] 2 points 4 months ago (4 children)

@[email protected] so I was able to perform the test, and if I restart it manually it is fast (30-34ms), its just while booting where it takes that long

[–] [email protected] 2 points 4 months ago

@[email protected] great hint, will try this, thanks!

 

Since upgrading from Plasma 6.0 to Plasma 6.1 my journald.service takes a longtime to boot.
systemd-journald.service takes 7-8 seconds. Even on a freshly installed system.

systemd-analyze:

Startup finished in 9.534s (firmware) + 6.112s (loader) + 3.281s (kernel) + 9.271s (userspace) = 28.200s

systemd-analyze critical-chain systemd-journald.service:

systemd-journald.service +7.853s └─systemd-journald.socket @428ms

systemd-analyze blame:

7.853s systemd-journald.service 2.152s systemd-modules-load.service 1.147s \x2esnapshots.mount 715ms NetworkManager.service 229ms dev-nvme1n1p2.device

how can I now further troubleshoot and maybe find a solution? has someone experienced same/similar? I can provide further info if needed, would appreciate very much if someone has an idea...

Edit: after working through it I came to the conclusion, that maybe Plasma isn‘t the issue here (since the „error“ happens way before graphical ui shows up), but more kernel related. Trying right now to get an older kernel running to see, if it confirms my assumption, but failed yet to do so…