You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been experiencing an issue where the systemd process for cleaning up temporary files occasionally hangs on my system. When it happens, one CPU core is fully utilized at 100% for an indefinite period, without any sign of completion.
Around the same time, I also started seeing a message about a duplicate configuration option during each package installation:
(3/4) Creating temporary files...
/usr/lib/tmpfiles.d/systemd.conf:35: Duplicate line for path "/var/lib/systemd/coredump", ignoring.
After checking the config files, it appears that there are two conflicting definitions for /var/lib/systemd/coredump:
These definitions come from two different packages:
❯ pacman -F usr/lib/tmpfiles.d/coredump.conf
usr/lib/tmpfiles.d/coredump.conf is owned by cachyos/cachyos-settings 1:1.1.3-1
❯ pacman -F /usr/lib/tmpfiles.d/systemd.conf
usr/lib/tmpfiles.d/systemd.conf is owned by core/systemd 256.7-1
It seems one of these packages recently introduced this conflicting configuration, which may be linked to the CPU hang issue, though I can’t confirm if it’s the direct cause.
Just wanted to flag this as a potential packaging conflict. Thanks for taking a look!
The text was updated successfully, but these errors were encountered:
(3/4) Creating temporary files...
/usr/lib/tmpfiles.d/systemd.conf:35: Duplicate line for path "/var/lib/systemd/coredump", ignoring.
This is ignoring the duration set by us, and is not the cause of whatever hang you're experiencing. With that in mind, our setting is in fact useless here since what get used is systemd's settings instead. I'm not reading that wrong right? cc @ventureoo
Hi there!
I've been experiencing an issue where the systemd process for cleaning up temporary files occasionally hangs on my system. When it happens, one CPU core is fully utilized at 100% for an indefinite period, without any sign of completion.
Around the same time, I also started seeing a message about a duplicate configuration option during each package installation:
After checking the config files, it appears that there are two conflicting definitions for
/var/lib/systemd/coredump
:These definitions come from two different packages:
It seems one of these packages recently introduced this conflicting configuration, which may be linked to the CPU hang issue, though I can’t confirm if it’s the direct cause.
Just wanted to flag this as a potential packaging conflict. Thanks for taking a look!
The text was updated successfully, but these errors were encountered: