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

the archlinux torrent
by Jude DaShiell 03 Jul '24

03 Jul '24

Having downloaded the torrent and burned the iso to a dvd I verified the torrent using sha256sum but apparently that wasn't enough since the installation broke part of the way through which means I ought to have used the gpg verification that is available online. What is done with those asc files to verify a download? I used lftp with no options on the command line and maybe that was also a mistake on my part. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940.

3 18

JDK/JRE and older Java versions
by Peter Nabbefeld 01 Jul '24

01 Jul '24

Hello, as a Java developer, I sometimes need to do compatibility checking using older versions, often using JRE, while I need a JDK for development. When I tried to update arch linux now, I found I cannot start any update because the update is blocked by setting JRE and JDK as conflicting packages. I tried to only install JDK 21, but the update is still being blocked because of my older versions of the JRE. Why do You block any software installation? I don't like the idea to enforce me to use any specific software, or to remove any specific one. Is there any possibility to remove the lock-in? Kind regards, Peter

5 12

virtualbox 7.0.16 and Windows 11 guest
by Ralf Mardorf 05 Jun '24

05 Jun '24

Hi, today I removed virtualbox6.1-bin 6.1.50 and installed virtualbox 7.0.16, because 6.1.50 doesn't work anymore [1] and I got rid of fixing virtualbox 6+ again and again. Doing a first short test a Windows 10 guest seems to run, but a Windows 11 guest seems to cause issues, at least a shutdown of the Windows 11 guest with _not_ updated guest additions didn't finish and locked the host or rather it was possible to push Ctrl+Alt+F2 and to run pkill VirtualBoxVM to get back a responding Arch Linux host. For other reasons I'm restoring another backup of Windows 11, which will take more than an hour, since the the vdi's size is > 700 GiB, so in the meantime I want to gather information. I will take a look at the settings mentioned by the Arch Wiki [2], [3]. Are there more settings I can check? It's an Intel CPU wit integrated GPU. • rocketmouse@archlinux ~ $ hwinfo --cpu | sort -u | grep Model Model: 6.191.5 "13th Gen Intel(R) Core(TM) i3-13100" • rocketmouse@archlinux ~ $ hwinfo --memory | grep Size Memory Size: 32 GB Regards, Ralf [1] "Could you still start Windows guests with virtualbox6.1-bin 6.1.50-1 or do you also experience guru meditations? I'm currently trying extra/virtualbox 7.0.16-1, which gets rid of the gurus, but so far a Windows 11 guest is not doing well." - https://aur.archlinux.org/pkgbase/virtualbox6.1-bin#comment-968033 [2] "4.11.1 Creating the virtual machine A VirtualBox virtual machine must be manually created. As of now do not add any storage device any disk to the virtual machine, it will be done manually later. Configure the virtual machine with the following settings (settings panel can be opened by clicking the "Settings" button in the main toolbar): View: System: Tab: Motherboard: mark Enable I/O APIC; mark Enable EFI; mark Hardware Clock in UTC Time if is your case. Tab: Processor: mark Enable PAE/NX; mark Enable Nested VT-x/AMD-V; Tab: Acceleration: Choose the paravirtualization interface Hyper-V from the drop down menu; mark Enable Nested Paging. Optionally you can enable also the following settings: View: Display Tab: Screen mark Enable 3D Acceleration. Note that it could cause glitches. Note: The Hyper-V setting is not required in order for the system to operate correctly, but it may help avoid licensing issues." - https://wiki.archlinux.org/title/VirtualBox#Creating_the_virtual_machine [3] "5.22 Random freezing in guests with Intel GPU With Intel CPU and graphics, allocating more processors for the guest can lower render performance, thus cause random freezing. Allocating less processors can help." - https://wiki.archlinux.org/title/VirtualBox#Random_freezing_in_guests_with_…

3 8

What's with the kernels that seem to stay stuck in core-testing longer than they used to?
by David C. Rankin 27 Apr '24

27 Apr '24

Devs, I've noticed kernels stay stuck in core-testing longer than they used to. In the past (unless there was some minor version change), they usually stayed in testing a day or less. The past couple have lingered nearly a week and linux 6.8.7.arch1-2 x86_64 has been there a few days? That's great to ensure there are no issue with other packages that depend on building drivers from the kernel, but does raise the question for the curios -- "What's up?" I ask for scheduling purposes. I monitor the newsfeeds from the package repos and when I see a new kernel coming, I try and set aside a convenient time for the update/reboot. Past few kernels, I've done that only to find - they are still in testing. Not a complaint, just a curiosity. -- David C. Rankin, J.D.,P.E.

3 5

Building Rust kernel modules - target.json missing
by L. Rose 23 Apr '24

23 Apr '24

Hello everyone, I'm trying to build the example Rust kernel modules from kernel source [1] on Arch Linux. I use a simple Makefile to build them out of tree: obj-m += rust_minimal.o all: make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules However, the build can't find some Rust metadata: make -C /lib/modules/6.8.7-arch1-1/build M=/home/lukas/Downloads/linux-6.8.7-arch1/samples/rust modules make[1]: Entering directory '/usr/lib/modules/6.8.7-arch1-1/build' RUSTC [M] /home/lukas/Downloads/linux-6.8.7-arch1/samples/rust/rust_minimal.o error: target file "./scripts/target.json" does not exist Indeed, there is no target.json in /lib/modules/$(uname -r)/build/scripts/, so I thought, maybe I need to use a special kernel with Rust support. But building linux-rust from the AUR fails with the same error message: Installing Rust files... install: cannot stat 'scripts/target.json': No such file or directory ==> ERROR: A failure occurred in package_linux-rust-headers(). Aborting... And even the default kernel is passing the Linux kernel Rust support check script as suggested in the kernel docs [2]: lukas@Lukas-AMD:rust$ make -C /lib/modules/$(uname -r)/build rustavailable make: Entering directory '/usr/lib/modules/6.8.7-arch1-1/build' Rust is available! make: Leaving directory '/usr/lib/modules/6.8.7-arch1-1/build' So what am I doing wrong? Is the Arch Linux kernel currently missing Rust metadata required for Rust support, like target.json? Or am I missing some important prerequisites here? Any suggestions welcome! Thanks, lukaro [1] https://github.com/Rust-for-Linux/linux/tree/rust-next/samples/rust [2] https://docs.kernel.org/6.8/rust/quick-start.html

1 0

PKGBUILD: nodejs
by Pocket 17 Apr '24

17 Apr '24

I am trying to build nodejs in a chroot using pkgctl repo clone --protocol=https nodejs pushd nodejs makechrootpkg -c -u -r "$CHROOT" -- --skippgpcheck popd It fails at this point ==> Entering fakeroot environment... chmod: cannot access '/startdir/pkg': No such file or directory I don't have startdir defined in the makepkg.conf file nor have I defined it anywhere Why is this failing? -- Hindi madali ang maging ako

3 3

building plasma-wayland-protocols
by Pocket 13 Apr '24

13 Apr '24

Trying to build plasma-wayland-protocols This is the error I am getting What executable is it looking for? I have built the entire qt5/qt6 stack except for qt5-ukui-platformtheme plasma-wayland-protocols is a dependency of qt5-ukui-platformtheme So I am stuck here Can anyone shed light on this issue? ==> Starting build()... -- The C compiler identification is GNU 12.1.0 -- The CXX compiler identification is GNU 12.1.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- -- No executable found. Can't check QT_INSTALL_PREFIX -- Installing in the same prefix as Qt, adopting their path scheme. -- No executable found. Can't check QT_INSTALL_PREFIX CMake Error at /usr/share/ECM/modules/ECMQueryQt.cmake:84 (message): No executable found. Can't check QT_INSTALL_PLUGINS as required Call Stack (most recent call first): /usr/share/ECM/kde-modules/KDEInstallDirs5.cmake:255 (ecm_query_qt) /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:15 (include) CMakeLists.txt:17 (include) -- Configuring incomplete, errors occurred! ==> ERROR: A failure occurred in build(). -- Hindi madali ang maging ako

1 0

pam 1.6.1-2 breaks sudo password
by Frederic Bezies 13 Apr '24

13 Apr '24

Hello. I noticed that pam 1.6.1-2 breaks sudo. Every time I tried to enter my password with a sudo command, it tells me my password is incorrect. Of course, it is not. The "fix" was to downgrade to pam 1.6.1-1. Hope it helps! -- Frederic Bezies fredbezies(a)gmail.com Blog: https://fredericbezies-ep.fr/blog/

9 13

Re: [arch-announce] Increasing the default vm.max_map_count value
by Genes Lists 12 Apr '24

12 Apr '24

On Sun, 2024-04-07 at 18:12 +0000, Arch Linux: Recent news updates: Robin Candau wrote: > The [vm.max_map_count][1] paramater will be increased from the > default `65530` value to `1048576`. > > This change should help address performance, crash or start-up issues > for a number of memory intensive applications, Performance improvement is unlikely but could allow something to run that otherwise would not. The lkml comment [1] is worth a read and includes : "To be clear, what you are doing here is akin to adding more memory to your system when there is a memory leak. This is not the solution you should be pushing. Ironically, this is using more memory and performing worse than it should. At best, the limit increase is a workaround for buggy programs." As Robin said, setting the max higher is probably benign - and only impacts a system running the problematic software (games). Nonetheless, it is very simple to change it to whatever value you want with your own prefs dropped into /etc/sysctl.d/xxx.conf gene [1] https://lore.kernel.org/lkml/566168554.272637693.1710968734203.Jav aMail.root@zimbra54- e10.priv.proxad.net/T/#m1905a48f415bc6e8069a8fe53dec44bc311571f2 -- Gene

1 0