April 2025 - 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

cp from internal SSD via USB 3 to external HDD is very slow
by Ralf Mardorf 26 Aug '25

26 Aug '25

Hi, I am copying from an internal SATA SSD via USB 3 to an external SATA WD Blue, a 3.5" CMR HDD. The first part “cp -ai /mnt/winos7/” (see [*1]) took about 70 minutes for 188 GiB, almost all files are quite small. The second part “cp -ai /mnt/winos10/” (see [*1]) should copy about 100 GiB small files + about 740 GiB for a single vbox vdi file. The about 100 GiB small files were copied and about 310 GiB of the vdi file were also already copied, at 03:30, so for about 410 GiB it took about 9 hours. I think this is taking far too long. Does anyone have an idea? FWIW ^Z was an oversight. I meant to press Ctrl+Alt+T to open a terminal tab, and apparently pressed Ctrl+Z (German QWERTY keyboard). CPU Model: 6.191.5 "13th Gen Intel(R) Core(TM) i3-13100" Memory Size: 32 GB For top see [*2]. • rocketmouse@archlinux ~ $ uname -r; cat /proc/cmdline 6.14.2-arch1-1 BOOT_IMAGE=/boot/vmlinuz-linux root=/dev/disk/by-label/m1.archlinux ro ibt=off ipv6.disable=1 kvm.enable_virt_at_load=0 Regards, Ralf [*1] • root@archlinux /home/rocketmouse # date; cp -ai /mnt/winos7/{*txt,o10_share,winOS_2} /mnt/ua.fantec/w7_ipad_archive-winos7_not_included-2025-apr-14/winos7/; echo $?; date; cp -ai /mnt/winos10/ /mnt/ua.fantec/w10ipad_archive+winos10_is_included-2025-apr-14/; echo $?; date Mon 14 Apr 17:02:20 CEST 2025 0 Mon 14 Apr 18:13:45 CEST 2025 ^Z [1]+ Stopped cp -ai /mnt/winos10/ /mnt/ua.fantec/w10ipad_archive+winos10_is_included-2025-apr-14/ 148 Tue 15 Apr 02:56:03 CEST 2025 • root@archlinux /home/rocketmouse # fg 1 cp -ai /mnt/winos10/ /mnt/ua.fantec/w10ipad_archive+winos10_is_included-2025-apr-14/ [*2] top - 03:38:10 up 2 days, 17:21, 1 user, load average: 1.30, 1.26, 1.30 Tasks: 284 total, 1 running, 281 sleep, 2 d-sleep, 0 stopped, 0 zombie %Cpu(s): 1.8 us, 0.8 sy, 0.0 ni, 84.3 id, 12.9 wa, 0.1 hi, 0.1 si, 0.0 st MiB Mem : 31862.0 total, 316.4 free, 3401.6 used, 29130.6 buff/cache MiB Swap: 16383.0 total, 16382.5 free, 0.5 used. 28460.4 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 82310 rocketm+ 20 0 557740 60108 48756 S 10.3 0.2 0:18.00 roxterm 663 root 20 0 819996 107492 66704 S 7.0 0.3 17:40.51 Xorg 100095 rocketm+ 20 0 2587672 172912 117660 S 1.3 0.5 0:08.42 Isolated Web Co 87583 root 20 0 7440 6136 5516 D 1.0 0.0 14:05.38 cp 2078 rocketm+ 20 0 167504 41148 33812 S 0.3 0.1 4:47.97 parcellite 2697 rocketm+ 20 0 73.9g 806944 168776 S 0.3 2.5 11:00.17 evolution 96948 root 20 0 0 0 0 I 0.3 0.0 0:12.97 kworker/u32:4-events_unbound 100138 root 20 0 0 0 0 I 0.3 0.0 0:00.99 kworker/1:2-events 100195 rocketm+ 20 0 70.5g 163948 142808 S 0.3 0.5 0:00.67 WebKitWebProces 100326 root 20 0 0 0 0 I 0.3 0.0 0:01.75 kworker/u32:1-flush-8:80 100948 rocketm+ 20 0 12372 9836 7660 R 0.3 0.0 0:00.07 top 1 root 20 0 24012 15008 9320 S 0.0 0.0 0:26.64 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.23 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 pool_workqu

2 5

Arch General - is there a problem with posts
by Mike Cloaked 26 Aug '25

26 Aug '25

There have been no posts coming from the arch general mailing list for several months. Is there a problem with the server? -- mike c

5 4

Would it be possible to include sdl3-freerdp3 in the freerdp package?
by Mathieu Lemoine 28 Apr '25

28 Apr '25

Hello, I have been using the sdl-freerdp3 for a few months now (with the wayland driver), as it works better than the wlfreerdp3 client. Lately I've started to see messages saying sdl-freerdp3 (the SDL2 client) is now deprecated and we should switch over to the SDL3 client (sdl3-freerdp, or I guess sdl3-freerdp3). But it's not currently included in the package. What would be the best way to reach out to the package maintainer so this gets included? https://archlinux.org/packages/extra/x86_64/freerdp/flag/ seems like the wrong place, registrations on the GitLab are closed because of SPAM, and I couldn't find an email for the package Maintainers. So I'm basically left with the general ML. Apologies if this is not the right place to ask about this.

2 1

Replaced redis with valkey and nextcloud broke?
by David C Rankin 27 Apr '25

27 Apr '25

All, I replaced redis with valkey tonight on a long-running nextcloud install. I followed the wiki pages exactly: https://wiki.archlinux.org/title/Valkey (I set all options as shown to suppress warnings) and https://wiki.archlinux.org/title/Nextcloud#Valkey_(Redis) (valkey is running on unixsockets per the wiki) However, upon starting/enabling valkey and restarting apache, attempting to reach nextcloud results in: <quote> Internal Server Error The server encountered an internal error and was unable to complete your request. Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report. More details can be found in the server log. </quote> git, http and nextcloud were added to the valkey group: $ grep valkey /etc/group valkey:x:971:git,http,nextcloud valkey is up and happily running and the socket has 0770 permissions per the wiki: $ scs valkey ● valkey.service - Advanced key-value store Loaded: loaded (/usr/lib/systemd/system/valkey.service; enabled; preset: 5:185mdisabled) Active: active (running) since Sat 2025-04-26 21:09:31 CDT; 17min ago Invocation: 5dc6c28081374c00837d5f7f94c38a95 Main PID: 1913 (valkey-server) Status: "Ready to accept connections" Tasks: 6 (limit: 4575) Memory: 3.4M (peak: 3.9M) CPU: 1.100s CGroup: /system.slice/valkey.service └─1913 "/usr/bin/valkey-server 127.0.0.1:6379" Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Running mode=standalone, port=6379. Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Server initialized Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Loading RDB produced by Valkey version 8.1.1 Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * RDB age 784 seconds Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * RDB memory usage when created 0.85 Mb Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Done loading RDB, keys loaded: 0, keys expired: 0. Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * DB loaded from disk: 0.000 seconds Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Ready to accept connections tcp Apr 26 21:09:31 2pi valkey-server[1913]: 1913:M 26 Apr 2025 21:09:31.488 * Ready to accept connections unix Apr 26 21:09:31 2pi systemd[1]: Started Advanced key-value store. $ l /run/valkey/ total 0 drwxr-xr-x 2 valkey valkey 60 Apr 26 21:09 . drwxr-xr-x 46 root root 1100 Apr 26 21:09 .. srwxrwx--- 1 valkey valkey 0 Apr 26 21:09 valkey.sock The config.php was updated per the wiki to use valkey: $ sudo tail /etc/webapps/nextcloud/config/config.php 'filelocking.enabled' => true, 'memcache.distributed' => '\\OC\\Memcache\\Redis', 'memcache.locking' => '\\OC\\Memcache\\Redis', 'redis' => array ( 'host' => '/run/valkey/valkey.sock', 'port' => 0, 'timeout' => 0.0, ), ); Attempting to access the nextcloud instance results in 6 messages in nextcloud.log (they repeat each time nextcloud does its cron update). I've summarized each in pretty-print so they are readable: 1. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 4, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "app_api", "method": "GET", "url": "/nextcloud/login", "message": "Error during app service registration: Permission denied", ... "File": "/usr/share/webapps/nextcloud/lib/private/RedisFactory.php", "Line": 104, "message": "Error during app service registration: Permission denied", "exception": {}, "CustomMessage": "Error during app service registration: Permission denied" } } 2. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 4, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "no app in context", "method": "GET", "url": "/nextcloud/login", "message": "Could not boot webhook_listeners: Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Could not boot webhook_listeners: Redis server went away", "exception": {}, "CustomMessage": "Could not boot webhook_listeners: Redis server went away" } } 3. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 4, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "no app in context", "method": "GET", "url": "/nextcloud/login", "message": "Could not boot workflowengine: Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Could not boot workflowengine: Redis server went away", "exception": {}, "CustomMessage": "Could not boot workflowengine: Redis server went away" } } 4. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 3, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "index", "method": "GET", "url": "/nextcloud/login", "message": "Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Redis server went away", "exception": {}, "CustomMessage": "Redis server went away" } } 5. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 3, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "core", "method": "GET", "url": "/nextcloud/login", "message": "Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Redis server went away", "exception": {}, "CustomMessage": "Redis server went away" } } 6. { "reqId": "Ga2ygrBvnNRsfUk5PSik", "level": 3, "time": "2025-04-27T01:34:11+00:00", "remoteAddr": "192.168.6.196", "user": false, "app": "core", "method": "GET", "url": "/nextcloud/login", "message": "Redis server went away", ... "File": "/usr/share/webapps/nextcloud/lib/private/Memcache/Redis.php", "Line": 59, "message": "Redis server went away", "exception": {}, "CustomMessage": "Redis server went away" } } This has me baffled. Both the valkey(redis) and nextcloud wiki changes make logical sense and seem like that should result in a painless upgrade. I was not so lucky. Is there something else needed to switch nextcloud from redis to valkey? 1. I stopped/disabled redis. 2. Installed valkey removing redis 3. Updated all configs per both wikis 4. started/enabled valkey (all good) 5. restarted httpd (all good) 6. attempted to access nextcloud (failed with the error above) Anybody have any ideas how I can get nextcloud back up and running with valkey? Worst case I'll try disableing redis/valkey altogether in the nextcloud config and run without caching -- not optimal. It was running perfectly with redis before the upgrade, so I'm stuck. -- David C. Rankin, J.D.,P.E.

1 1

Notice that flashed on wiki access today - too fast to read - was it important?
by David C Rankin 27 Apr '25

27 Apr '25

Arch Devs, On access of https://wiki.archlinux.org today, a dialog flashed to the screen immediately before the wiki main page was rendered, but the dialog flashed too quickly to read. Was it important or require any action? May have just been a wiki update note, dark mode looks a bit different? -- David C. Rankin, J.D.,P.E.

8 12

Journal log entries while installing an ISO image
by Friedrich Romstedt 23 Apr '25

23 Apr '25

Hi, Yesterday I prepared an USB stick with the recent version of the Arch Linux installation medium (Release 2025-04-01). This is about some error entries in the system journal, which I encountered during copying this ISO image over. The respective transcripts are provided inline, as well as attached in the form of plain text files. I used initially $ sudo cp <ISO> /dev/sda. After having finished that process, I spotted some error log entries in the system journal: Apr 20 15:30:25 T470p sudo[21475]: friedrich : TTY=pts/2 ; PWD=/home/friedrich/(...) ; USER=root ; COMMAND=/usr/bin/cp archlinux-2025.04.01-x86_64.iso /dev/sda Apr 20 15:30:25 T470p sudo[21475]: pam_unix(sudo:session): session opened for user root(uid=0) by friedrich(uid=1000) Apr 20 15:33:10 T470p systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)! Apr 20 15:33:10 T470p systemd[1]: systemd-udevd.service: Killing process 359 (systemd-udevd) with signal SIGABRT. Apr 20 15:34:40 T470p systemd[1]: systemd-udevd.service: State 'stop-watchdog' timed out. Killing. Apr 20 15:34:40 T470p systemd[1]: systemd-udevd.service: Killing process 359 (systemd-udevd) with signal SIGKILL. Apr 20 15:36:10 T470p systemd[1]: systemd-udevd.service: Processes still around after SIGKILL. Ignoring. Apr 20 15:37:38 T470p kernel: sda: sda1 sda2 Apr 20 15:37:38 T470p sudo[21475]: pam_unix(sudo:session): session closed for user root Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Failed with result 'watchdog'. Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Consumed 4.845s CPU time, 51.6M memory peak. Apr 20 15:37:38 T470p systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 1. Apr 20 15:37:38 T470p systemd[1]: Starting Rule-based Manager for Device Events and Files... Apr 20 15:37:39 T470p systemd-udevd[21582]: Using default interface naming scheme 'v257'. Apr 20 15:37:39 T470p systemd[1]: Started Rule-based Manager for Device Events and Files. Apr 20 15:38:19 T470p kernel: usb 1-1: USB disconnect, device number 7 Because I had doubts about the integrity of the thus prepared USB stick, I repeated the process, this time using $ su - and # dd if=<ISO> of=/dev/sda bs=8M. Here, I encountered similar logs: Apr 20 15:38:53 T470p kernel: sda: sda1 sda2 Apr 20 15:38:53 T470p kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk Apr 20 15:39:07 T470p su[21650]: (to root) friedrich on pts/2 Apr 20 15:39:07 T470p su[21650]: pam_unix(su:session): session opened for user root(uid=0) by friedrich(uid=1000) Apr 20 15:44:05 T470p systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)! Apr 20 15:44:05 T470p systemd[1]: systemd-udevd.service: Killing process 21582 (systemd-udevd) with signal SIGABRT. Apr 20 15:45:35 T470p systemd[1]: systemd-udevd.service: State 'stop-watchdog' timed out. Killing. Apr 20 15:45:35 T470p systemd[1]: systemd-udevd.service: Killing process 21582 (systemd-udevd) with signal SIGKILL. Apr 20 15:47:05 T470p systemd[1]: systemd-udevd.service: Processes still around after SIGKILL. Ignoring. Apr 20 15:48:35 T470p systemd[1]: systemd-udevd.service: State 'final-sigterm' timed out. Killing. Apr 20 15:48:35 T470p systemd[1]: systemd-udevd.service: Killing process 21582 (systemd-udevd) with signal SIGKILL. Apr 20 15:48:56 T470p kernel: sda: sda1 sda2 Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=9/KILL Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Failed with result 'watchdog'. Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Consumed 1.101s CPU time, 7.4M memory peak. Apr 20 15:48:56 T470p systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 2. Apr 20 15:48:56 T470p systemd[1]: Starting Rule-based Manager for Device Events and Files... Apr 20 15:48:56 T470p systemd-udevd[21808]: Using default interface naming scheme 'v257'. Apr 20 15:48:56 T470p systemd[1]: Started Rule-based Manager for Device Events and Files. Apr 20 15:49:13 T470p kernel: usb 1-1: USB disconnect, device number 8 In the second run, where I kept an eye on the journal, I noticed that the error entries were logged a few minutes *before* the copying process completed. There were no errors reported by both of these directly. The pen drive is booting and working just fine. However, I felt this behaviour being worth it to be reported. Maybe someone else can make sense of it. Best, Friedrich

4 7

Building with cmake
by Pocket 21 Apr '25

21 Apr '25

I am building packages following DeveloperWiki:Building in a clean chroot When building packages that are associated with gnome I get the following error: CMake Error at wsrep-lib/CMakeLists.txt:5 (cmake_minimum_required): Compatibility with CMake < 3.5 has been removed from CMake. Update the VERSION argument <min> value. Or, use the <min>...<max> syntax to tell CMake that the project requires at least <min> but has been updated to work with policies introduced by <max> or earlier. Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway. Adding export CMAKE_POLICY_VERSION_MINIMUM=3.5 doesn't correct my problem. Is there another way to get past this without adding -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to the PKGBUILD? -- Hindi madali ang maging ako

2 2

Valkey to replace Redis - Are devs updating configs in dependent packages (Nextcloud, etc..) to use valkey?
by David C Rankin 20 Apr '25

20 Apr '25

Arch devs, The latest news for "Valkey to replace Redis in the [extra] Repository" says: <quote> Users are recommended to begin transitioning their use of Redis to Valkey as soon as possible to avoid possible complications after the 14 day transition window closes. </quote> For other Arch packages that are configured to use redis (or php-legacy-redis), will the maintainers update the configs for the next release within the 14 day transition window? Or does "Users are recommended ..." mean just that, users need to try and make the replacements in all needed config files during the 14 days? I'm referring to packages like Nextcloud that Arch packages and has config files with entries for redis and php-legacy-redis. (with corresponding instructions in the Arch-wiki for Nextcloud) Also will there be corresponding php-valkey and php-legacy-valkey packages to replace the php-redis ones? The valkey docs are fairly clear, valkey is a for of redis 7.2: https://valkey.io/topics/migration/ so other than a name change and change to start valkey instead of redis, is there anything else involved for the likes of Nextcloud? I don't have enough cache to worry about migration files from redis to valkey other than stopping/disabling redis, starting valkey and then reloading with the config file(s) name changed. So if there are no caches a user needs to migrate from redis, other than the redis package changing to valkey, will all other Arch packages that use redis be updated in this 14 day period? -- David C. Rankin, J.D.,P.E.

2 1

arch-nspawn ERROR: chroot is not at version v6. Please rebuild. -- does that mean rm -rf $CHROOT?
by David C Rankin 19 Apr '25

19 Apr '25

Arch folks, My clean chroot will no longer update. Attempting update results in the error: $ arch-nspawn $CHROOT/root pacman -Syu ==> ERROR: chroot '/home/david/arch/pkg/chroot/root' is not at version v6. Please rebuild. I've checked the various devtools man pages and --help and there is nothing about rebuilding, so does this mean I need to: # rm -rf $CHROOT and start over? Or, is there actually a way to "rebuild" the chroot without wiping it all out and starting over? -- David C. Rankin, J.D.,P.E.

4 4