October 2022 - Arch-general - lists.archlinux.org

[arch-general] System terribly slow
by riveravaldez 27 Oct '25

27 Oct '25

Hi, I'm looking for some advice trying to pinpoint why or where my system has becoming almost unusable slow. Searching the web I've found some hints but nothing precise enough. Maybe it's a failing HDD, but I'm first posting what I have until now in the hope someone can give some advice. Superficial symptoms are a general slowness. I'm using just IceWM and `startx` to initialize the GUI, and even logging into my account previous to that takes almost a minute to get done. Then any application I launch takes minutes to just start (from IceWM to firefox, from qtox to pcmanfm or geany, etc.). Even navigate the folders tree with pcmanfm takes 10 or more seconds just to show any folder content... Hope some of this helps: $ sudo journalctl -b -exp3 -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri 2021-12-03 19:50:29 -03. -- dic 03 00:48:43 arch kernel: sd 0:0:0:0: [sda] Asking for cache data failed dic 03 00:48:43 arch kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through dic 03 00:50:39 arch libvirtd[592]: cannot open directory '/home/dell/Software/VMs/TrisquelMini8': No existe el fichero o el directorio dic 03 00:50:39 arch libvirtd[592]: error interno: Falló al iniciar automáticamente el grupo de almacenamiento 'TrisquelMini8': cannot open directory '/home/dell/Softwar> dic 03 00:50:41 arch libvirtd[592]: No se encontró 'dmidecode' en ruta: No existe el fichero o el directorio dic 03 00:50:57 arch libvirtd[592]: No se encontró 'dmidecode' en ruta: No existe el fichero o el directorio dic 03 00:56:40 arch systemd[1]: Failed to start Disk Manager. Subject: A start job for unit udisks2.service has failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit udisks2.service has finished with a failure. The job identifier is 1072 and the job result is failed. $ systemctl --state=failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. $ systemd-analyze Startup finished in 11.038s (kernel) + 1min 31.352s (userspace) = 1min 42.391s graphical.target reached after 1min 31.352s in userspace $ systemd-analyze blame 37.946s polkit.service 29.248s dev-sda1.device 28.827s systemd-tmpfiles-clean.service 24.692s udisks2.service 15.936s systemd-journal-flush.service 14.228s systemd-hwdb-update.service 13.930s ldconfig.service 13.502s upower.service 12.881s ufw.service 8.830s user(a)1000.service 7.556s systemd-tmpfiles-setup-dev.service 7.280s avahi-daemon.service 7.275s bluetooth.service 7.262s iwd.service 6.067s systemd-logind.service 6.058s systemd-machined.service 5.825s systemd-tmpfiles-setup.service 5.123s systemd-sysusers.service 4.569s systemd-udevd.service 4.511s systemd-resolved.service 4.281s systemd-networkd.service 3.724s systemd-journal-catalog-update.service 3.415s systemd-fsck@dev-disk-by\x2duuid-1d72b82c\x2d9c58\x2d4f57\x2d97a3\x2de29ff35a5632.service 2.959s systemd-modules-load.service 2.557s lm_sensors.service 2.503s systemd-random-seed.service 2.389s systemd-backlight@backlight:acpi_video0.service 1.983s dev-disk-by\x2duuid-84c91978\x2da09c\x2d4087\x2db60d\x2d86730d142f63.swap 1.967s systemd-backlight@leds:dell::kbd_backlight.service 1.563s systemd-timesyncd.service 1.457s systemd-update-utmp.service 1.287s systemd-udev-trigger.service 1.278s systemd-rfkill.service 1.219s alsa-restore.service 1.164s systemd-sysctl.service (...) $ systemctl status polkit.service ● polkit.service - Authorization Manager Loaded: loaded (/usr/lib/systemd/system/polkit.service; static) Active: active (running) since Fri 2021-12-03 00:50:28 -03; 19h ago Docs: man:polkit(8) Main PID: 613 (polkitd) Tasks: 12 (limit: 6993) Memory: 18.9M CPU: 1.032s CGroup: /system.slice/polkit.service └─613 /usr/lib/polkit-1/polkitd --no-debug dic 03 00:49:50 arch systemd[1]: Starting Authorization Manager... dic 03 00:50:05 arch polkitd[613]: Started polkitd version 0.120 dic 03 00:50:26 arch polkitd[613]: Loading rules from directory /etc/polkit-1/rules.d dic 03 00:50:26 arch polkitd[613]: Loading rules from directory /usr/share/polkit-1/rules.d dic 03 00:50:28 arch polkitd[613]: Finished loading, compiling and executing 6 rules dic 03 00:50:28 arch systemd[1]: Started Authorization Manager. dic 03 00:50:28 arch polkitd[613]: Acquired the name org.freedesktop.PolicyKit1 on the system bus $ systemctl status dev-sda1.device ● dev-sda1.device - Hitachi_HTS545025B9A300 ROOT Follows: unit currently follows state of sys-devices-pci0000:00-0000:00:1f.2-ata1-host0-target0:0:0-0:0:0:0-block-sda-sda1.device Loaded: loaded Active: active (plugged) since Fri 2021-12-03 00:49:12 -03; 19h ago Device: /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1 Notice: journal has been rotated since unit was started, output may be incomplete. $ systemctl status systemd-tmpfiles-clean.service ○ systemd-tmpfiles-clean.service - Cleanup of Temporary Directories Loaded: loaded (/usr/lib/systemd/system/systemd-tmpfiles-clean.service; static) Active: inactive (dead) since Fri 2021-12-03 01:03:52 -03; 19h ago TriggeredBy: ● systemd-tmpfiles-clean.timer Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 1473 ExecStart=systemd-tmpfiles --clean (code=exited, status=0/SUCCESS) Main PID: 1473 (code=exited, status=0/SUCCESS) CPU: 185ms dic 03 01:03:23 arch systemd[1]: Starting Cleanup of Temporary Directories... dic 03 01:03:52 arch systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. dic 03 01:03:52 arch systemd[1]: Finished Cleanup of Temporary Directories. $ systemctl status udisks2.service ● udisks2.service - Disk Manager Loaded: loaded (/usr/lib/systemd/system/udisks2.service; disabled; vendor preset: disabled) Active: active (running) since Fri 2021-12-03 00:59:51 -03; 19h ago Docs: man:udisks(8) Main PID: 1129 (udisksd) Tasks: 5 (limit: 6993) Memory: 3.2M CPU: 23.045s CGroup: /system.slice/udisks2.service └─1129 /usr/lib/udisks2/udisksd dic 03 00:59:26 arch systemd[1]: Starting Disk Manager... dic 03 00:59:26 arch udisksd[1129]: udisks daemon version 2.9.4 starting dic 03 00:59:51 arch systemd[1]: Started Disk Manager. dic 03 00:59:54 arch udisksd[1129]: Acquired the name org.freedesktop.UDisks2 on the system message bus $ systemctl status systemd-journal-flush.service ● systemd-journal-flush.service - Flush Journal to Persistent Storage Loaded: loaded (/usr/lib/systemd/system/systemd-journal-flush.service; static) Active: active (exited) since Fri 2021-12-03 00:48:59 -03; 19h ago Docs: man:systemd-journald.service(8) man:journald.conf(5) Process: 283 ExecStart=journalctl --flush (code=exited, status=0/SUCCESS) Main PID: 283 (code=exited, status=0/SUCCESS) CPU: 15ms dic 03 00:48:43 arch systemd[1]: Starting Flush Journal to Persistent Storage... dic 03 00:48:59 arch systemd[1]: Finished Flush Journal to Persistent Storage. $ systemctl status systemd-hwdb-update.service ● systemd-hwdb-update.service - Rebuild Hardware Database Loaded: loaded (/usr/lib/systemd/system/systemd-hwdb-update.service; static) Active: active (exited) since Fri 2021-12-03 00:48:57 -03; 19h ago Docs: man:hwdb(7) man:systemd-hwdb(8) Process: 279 ExecStart=systemd-hwdb update (code=exited, status=0/SUCCESS) Main PID: 279 (code=exited, status=0/SUCCESS) CPU: 1.746s dic 03 00:48:57 arch systemd[1]: Finished Rebuild Hardware Database. $ journalctl -b -u systemd-journald.service -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri 2021-12-03 20:49:18 -03. -- dic 03 00:48:43 arch systemd-journald[271]: Journal started dic 03 00:48:43 arch systemd-journald[271]: Runtime Journal (/run/log/journal/431f639f382e4bad8a43628868f2fc6c) is 8.0M, max 292.4M, 284.4M free. dic 03 00:48:44 arch systemd-journald[271]: Time spent on flushing to /var/log/journal/431f639f382e4bad8a43628868f2fc6c is 7.561088s for 798 entries. dic 03 00:48:44 arch systemd-journald[271]: System Journal (/var/log/journal/431f639f382e4bad8a43628868f2fc6c) is 16.0M, max 2.4G, 2.4G free. $ journalctl -b -u systemd-fsck@dev-disk-by\\x2duuid-1d72b82c\\x2d9c58\\x2d4f57\\x2d97a3\\x2de29ff35a5632.service -- Journal begins at Thu 2021-12-02 23:59:31 -03, ends at Fri 2021-12-03 20:52:36 -03. -- dic 03 00:49:18 arch systemd[1]: Starting File System Check on /dev/disk/by-uuid/1d72b82c-9c58-4f57-97a3-e29ff35a5632... dic 03 00:49:21 arch systemd-fsck[485]: HOME: limpio, 208781/13107200 ficheros, 37165716/52398592 bloques dic 03 00:49:21 arch systemd[1]: Finished File System Check on /dev/disk/by-uuid/1d72b82c-9c58-4f57-97a3-e29ff35a5632. $ journalctl --verify PASS: /var/log/journal/431f639f382e4bad8a43628868f2fc6c/user-1000.journal 3b84d8: Data object's entry array not sorted File corruption detected at /var/log/journal/431f639f382e4bad8a43628868f2fc6c/system.journal:915878 (of 16777216 bytes, 56%). FAIL: /var/log/journal/431f639f382e4bad8a43628868f2fc6c/system.journal (Mensaje erróneo) $ journalctl --disk-usage Archived and active journals take up 24.0M in the file system. Maybe it's pertinent to mention that I've just cleaned up /var/log/journal to rule out storage issues. Any help will be most welcome. Thanks a lot in advance.

6 8

DKIM fail messages
by David Rosenstrauch 14 Nov '22

14 Nov '22

After posting a message to this list earlier today, I immediately received nearly a dozen DKIM fail messages, all being sent by the "OpenDMARC Filter" at various domains, and all saying that the DKIM fail reason was "signature verification failed". I raised this issue with support at my hosting company, who pointed out that a) my domain's DKIM records are set up correctly, and b) one of the headers on my email that got sent to the list indicated that Arch's mailman actually did successfully verify my domain's DKIM record when it received my email, before forwarding it on. Anyone know why these fail messages might be happening? Is this being caused by a misconfiguration in Arch's mailman installation? Or is this a misconfiguration of the individual OpenDMARC software installations at each of those domains? Thanks, DR

6 17

Keeping desktop PC and laptop in sync
by Joel 07 Nov '22

07 Nov '22

Hi, as we have a discussion ongoing about setting up a new PC, I thought I could jump in with my current issue : I have retired my laptop and bought a desktop PC. Gone through the fresh installation process (once every 12 years is OK to declutter a bit), and rsync'ed my home directory (parts of it, mostlyskipped ~/.local and~/.config where I found some 10-20 years old files from programs I used once but never since). Now I still want to use my laptop when I'm on the road, which happens rather seldomly (once every 2 weeks), i.e. have my files, my bookmarks etc available on my laptop. Also not only have to sync my /home/$USER but also /root and some more mountpoints (source code, website stuff, audio, video, pictures), totaling around 1.5TB of data I've been playing around with rsync and adding many many exclude rules to a) limit the amount of files being transferred (eg exclude ~/.cache, browser's cache, thunderbird's imap cache etc) so I can keep an overview if something is getting overwritten that I don't want b) keep certain files (especially XFCE config etc) distinct as eg I have 2 monitors on my PC vs only 1 on the laptop -> different menus, window settings etc Now this is pretty tedious, initial rsync's dry-run showed ~700k files that would be sync'ed, which I brought down to 1k after several iterations and adjustment of exclude settings, and this is so far my first run - currently using my laptop and will sync back when I'm home again... let's see how many files will differ then ! So I'm looking for more easy-to-use alternatives. Most important thing : I want dry-run functionality to prevent unwanted data loss, which means automatic sync tools are not the way to go ! I think synthing is such a candidate, unless I missed the dry-run option somewhere. Have used unison many many years ago, but I think it was also not perfect and had issues handling thousands/millions of files. Heard of some new systemd homesync (?), but didn't have a look at it now, sounds also like it automatically syncs. Any thoughts / recommendations / advices ? Many thanks Joel

6 8

Setting up new computer to be identical to old one
by Spencer Collyer 01 Nov '22

01 Nov '22

I am looking to replace my current desktop PC, which is getting on for 8 years old now, with a more up-to-date one. Ideally I want the new one to be set up the same as my current one, which has been running on Arch since I first got it. I keep my Arch up-to-date by running a full update roughly every four weeks. What is the best way to set up the new one to mirror the existing one? I'd like to have all the same packages installed, with basically the same setup, except for obvious points like the new PC having a different IP address and name on my network. My initial idea was something like the following: 1) Install a basic Arch system on the new computer 2) Get the list of installed packages from the old computer (I think there is a way to do this using Pacman?) 3) Somehow get Pacman to install the same list of packages on the new computer. 4) Tidy up any config files that need changing - e.g. for the aforementioned IP address / computer name stuff. 5) Copy over my /home directory 6) Copy over various data directories/partitions I have -e.g. I have a whole bunch of images stored in a separate partition that I'll want to copy over. The stuff in here is all self-contained so should be easy enough to copy over. I found thread https://bbs.archlinux.org/viewtopic.php?id=171726 which had some ideas as well - the above is sort-of based on stuff I found on there along with my own thoughts. Does that look like a reasonable plan? Anything I might be missing? Thanks for your attention. Regards, Spencer

7 9

Shadowing the boot disk on Arch system
by Spencer Collyer 30 Oct '22

30 Oct '22

Hi, This is sort-of a follow-on to my earlier message regarding how to best set up a new desktop to match the existing one I have running Arch. I'm intending that my new computer will have an M2 drive as the boot disk. As well as the OS it will also hold my /home partition. Because of a bad experience I had with a Windows laptop with an SSD drive installed, where the SSD got completely wiped back to its factory setting, my intention is to have a hard disk that acts as a 'shadow' of the boot disk. The idea is it will also be a bootable drive with exactly the same setup as the M2 drive. That way if the M2 drive dies, I can still boot using this backup drive and the system will look the same. My intention is to have a cron job that periodically (at least daily) synchronises the backup drive so it looks exactly the same as the main drive. Does that sound like a feasible plan? If it is, my question is what is the best way to initially set up the shadow drive? Should I do a full install on it, so almost treating it like I'm setting up a new computer, but making sure I have all the same packages and setup as the main drive. Or should i just use 'dd' to copy the whole main drive over to the backup drive? I'll make sure the two drives are the same size (or rather that the backup is at least as large as the main drive). Or is there another, better, way I haven't thought of or found while trawling the web? Thanks for your attention, Regards, Spencer

2 1

Moving root partition to another drive
by pete 30 Oct '22

30 Oct '22

Hi . Got a bit of a problem i need to move the root partition to another drive my own fault i did not make it big enough to start with but i cant face a complete rebuild of the system i have several 1Tb drives lurking but how do i switch things to a new drive . I remember doing that many many years ago but cant remember how now any help out there would be greatfull Thanks Pete

6 7

Proposal: Do not remove a package from the AUR until it is available in a stable repository
by Óscar García Amor 29 Oct '22

29 Oct '22

Hi all! Recently with the GNOME 43 update I have seen that certain packages are being removed from the AUR to go into the official testing repositories. The problem, in my opinion, is that packages are being removed from the AUR before they go into an official stable repository, which makes the packages "disappear" for a while. Not everyone has the testing repository enabled. In fact using AUR packages is not a condition for having testing, so what a user sees is that suddenly the package he/she was using disappears and he/she can't install it neither with his AUR helper nor with pacman. IMHO, I think it would be better to leave the packages in the AUR until they reach the stable repositories to avoid possible confusion. Greetings. -- Óscar García Amor | ogarcia at moire.org | http://ogarcia.me

4 4

Create ps1 games with Brasero or other programs
by ilpiko2 28 Oct '22

28 Oct '22

Brasero i've always used it for music cds and some PS2 game backups. What I have never tried is using it for PS1 game backups. Searching the web i found some posts but they were old. Is it possible to burn them? is better k3b? Thank you. Marco P.S. sorry for my english.

2 1

Pacman returns error 404
by Zero 27 Oct '22

27 Oct '22

Hi all, Trying to install nodejs with pacman I do experience errors: pacman --sync nodejs Packages (1) nodejs-19.0.0-1 ... :: Proceed with installation? [Y/n] Y :: Retrieving packages... nodejs-19.0.0-1-x86_64.pkg.tar.zst failed to downloaderror: failed retrieving file 'nodejs-19.0.0-1-x86_64.pkg.tar.zst' from geo.mirror.pkgbuild.com : The requested URL returned error: 404 When accessing https://geo.mirror.pkgbuild.com/archlinux with a browser I can download the files nodejs-19.0.0-2-x86_64.pkg.tar.zst and nodejs-19.0.0-2-x86_64.pkg.tar.zst.sig. But when accessing https://mirror.rackspace.com/archlinux with a browser it gives a http error 503 or after a long wait the packages show up. Is there a problem with the pacman mirrors ? ~Zero

4 4

gnome 43 / testing - gnome-shell core dumps
by Genes Lists 27 Oct '22

27 Oct '22

Sharing in case helps others avoid having trouble. Update worked fine - once update completed fresh reboot - gdm starts fine - can login - but after that get a blank desktop - nothing at all works. Will go over logs more carefully but looks like gnome-shell is crashing: Process 1181 (gnome-shell) of user xxxx dumped core. The logs are tricky, as gnome spits a slew of error messages at the best of times (this is not new to 43, for me anyway). All 3 machines are intel i915 based; 2 NUCs and an older laptop. I've downgraded to 42 and all works well again. FYI :) gene

1 2