- Arch-general - lists.archlinux.org

[arch-general] [aur] cctag build error
by Peter Nabbefeld 31 Jul '21

31 Jul '21

Hello, when I try to build "cctag" as a new dependency of alice-vision-git, I get "~/.cache/pikaur/build/cctag/src" does not appear to contain CMakeLists.txt". I could find it in ~/.cache/pikaur/build/cctag/src/CCTag-1.0.0/src, so the repository snapshot is probably handled incorrectly. I'm not sure if cctag should reside in it's own project, as it seems to be part of and only used by alice-vision. However, even when I modify PKGBUILD to point to ~/.cache/pikaur/build/cctag/src/CCTag-1.0.0/src, CMakeLists.txt isn't found, with the same incorrect path shown in the error message; it seems, the -S option is ignored. :-O After insertion of "cd" I could start the build, but now the following error message is provided: CMake Error at CMakeLists.txt:172 (CUDA_ADD_LIBRARY): Unknown CMake command "CUDA_ADD_LIBRARY". How can I fix this? Kind regards P.

2 3

[arch-general] udev complaint and USB malfunction
by set＠nmset.info 31 Jul '21

31 Jul '21

This message appears in /var/log/errors.log (using syslog-ng) (don't know since when): systemd-udevd[424]: /usr/lib/udev/rules.d/99-indi_auxiliary.rules:5 Invalid value "/bin/sh -c 'test -f /sys/module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/parameters/usbfs_memory_mb'" for RUN (char 76: invalid substitution type), ignoring, but please fix it. I don't have a clue about an appropriate fix, apart from deleting 99- indi_auxiliary.rules, and don't know how valid it would be to delete this file. I'm having this strange USB behaviour on 2 machines : Plugging a USB stick may not trigger the 'New device' popup in KDE, while lsblk does list the USB stick. The latter may be connected directly to the machine, or via extension cable or a USB hub. It works half of the time as expected. An this one on one recent host : A USB 3 hub (tried 2 hubs) may not always list its devices, with these errors on resume from a *long* suspend, or on reboot : Jul 31 12:24:22 localhost.localdomain kernel: usb 5-3: device descriptor read/ 64, error -71 Jul 31 12:24:22 localhost.localdomain kernel: usb 5-3: device descriptor read/ 64, error -71 Jul 31 12:24:22 localhost.localdomain systemd-udevd[408]: /usr/lib/udev/ rules.d/99-indi_auxiliary.rules:5 Invalid value "/bin/sh -c 'test -f /sys/ module/usbcore/parameters/usbfs_memory_mb && test $(cat /sys/module/usbcore/ parameters/usbfs_memory_mb) -lt 256 && echo 256 > /sys/module/usbcore/ parameters/usbfs_memory_mb'" for RUN (char 76: invalid substitution type), ignoring. Jul 31 12:24:22 localhost.localdomain kernel: usb 5-3: device descriptor read/ 64, error -71 Jul 31 12:24:22 localhost.localdomain kernel: usb 5-3: device descriptor read/ 64, error -71 Jul 31 12:24:23 localhost.localdomain kernel: usb 5-3: device not accepting address 5, error -71 Jul 31 12:24:24 localhost.localdomain kernel: usb 5-3: device not accepting address 6, error -71 Jul 31 12:24:24 localhost.localdomain kernel: usb usb5-port3: unable to enumerate USB device I can't know if all these are related. I am requesting help in search of an easy fix. Thanks and regards.

3 2

[arch-general] pacman error
by Jude DaShiell 27 Jul '21

27 Jul '21

Installation path was archinstall along with some post-install configuration needed to enable accessibility among other things. Successful boot with speech coming up. Then as root pacman -Syu I get back an error saying pacman cannot lock data bases and pacman fails. pacman-key --populate ran before the pacman command and finished with no problems. What did I do wrong?

2 1

[arch-general] Rescue mode stopped working
by David Rosenstrauch 27 Jul '21

27 Jul '21

I'm not sure what changed, but for some reason I'm no longer able to drop into rescue mode on my laptop (i.e. using "systemctl rescue") - or to boot directly into single user mode. When I try either of these, the kernel loads, and then looks like it's entering single user mode, prompting me to enter my root password to proceed (as it should). But when I do enter the root password at the prompt - or even just press enter - the system quickly displays "Reloading system manager configuration", followed by something about switching to default target, and then switches into full interactive mode complete with graphical login prompt. I tried downgrading down to several earlier versions of systemd (back to 248), as well as trying to boot using the LTS kernel in single user mode, but I still get the issue. This behavior has definitely changed very recently (i.e., within a few days to a week) as I use single user mode often, and only just noticed this today. I'd file a bug about this but I have no idea what package might be at fault. Any pointers appreciated! Thanks, DR

1 1

[arch-general] Angband package flagged out-of-date since months
by Tim Schumacher 26 Jul '21

26 Jul '21

Hello there, I just wanted to ask if anyone knows where the holdup on updating the angband package [1] comes from. The newest version, 4.2.2, has been released on the 7th of March [2], and the package was subsequently flagged out-of-date, but there hasn't been any activity since then. Thanks, Tim [1] https://archlinux.org/packages/community/x86_64/angband/ [2] https://angband.github.io/angband/release/4.2.2

2 1

[arch-general] Community git repository
by LuKaRo 23 Jul '21

23 Jul '21

Hi everyone, is GitHub the only source for the Community git repository at the moment, or am I missing something? I prefer to avoid GitHub, and therefore used git.archlinux.org instead. However, this seems to be defunct now, redirecting to gitlab.archlinux.org. However, I can't find any community-related project there. Thanks a lot in advance, LuKaRo

4 4

[arch-general] systemd not mounting some filesystems on boot?
by CJ Kucera 19 Jul '21

19 Jul '21

Hello all! tl;dr version: I've got some local filesystems, all within the same LVM LV, some of which will fail to mount on boot, requiring me to do so by hand instead. Which filesystems don't mount can vary from boot to boot (and sometimes they all work), and the ones that *don't* mount aren't even mentioned anywhere by systemctl/journalctl -- I would expect that if the mount was *attempted* but failed, I'd see some logs. Anyone have a clue about this? Many details follow: So I've got some admittedly-improperly-placed filesystems that I mount into /usr/local, specifically: /usr/local/dv, /usr/local/winex, and /usr/local/vmware (in addition to /usr/local itself being its own filesystem). I've got them all in /etc/fstab basically identical to each other: > # grep /usr/local /etc/fstab > /dev/mapper/arrakis-local /usr/local ext4 noatime 1 2 > /dev/mapper/arrakis-winex /usr/local/winex ext4 noatime 1 2 > /dev/mapper/arrakis-vmware /usr/local/vmware ext4 noatime 1 2 > /dev/mapper/arrakis-dv /usr/local/dv ext4 noatime 1 2 Those all exist inside the same LVM LV, as you might guess from the device paths. I've noticed that on initial boot, I don't always get all of them properly mounted, and I've got to manually mount them myself. For instance, after a reboot just now, /usr/local/dv did not get mounted: > # mount | grep /usr/local > /dev/mapper/arrakis-local on /usr/local type ext4 (rw,noatime) > /dev/mapper/arrakis-vmware on /usr/local/vmware type ext4 (rw,noatime) > /dev/mapper/arrakis-winex on /usr/local/winex type ext4 (rw,noatime,stripe=27879) Or, looking at it via systemctl: > # systemctl list-units --all | grep usr-local > usr-local-dv.mount loaded inactive dead /usr/local/dv > usr-local-vmware.mount loaded active mounted /usr/local/vmware > usr-local-winex.mount loaded active mounted /usr/local/winex > usr-local.mount loaded active mounted /usr/local Querying the usr-local-dv unit directly, I don't see anything particularly telling: > # systemctl status usr-local-dv.mount > ○ usr-local-dv.mount - /usr/local/dv > Loaded: loaded (/etc/fstab; generated) > Active: inactive (dead) > Where: /usr/local/dv > What: /dev/mapper/arrakis-dv > Docs: man:fstab(5) > man:systemd-fstab-generator(8) And there's no mention of the "dv" mount in journalctl either: > # journalctl -b 0 | grep -E '(usr-local|/usr/local)' > Jul 19 14:03:13 arrakis systemd[1]: usr-local.mount: Directory /usr/local to mount over is not empty, mounting anyway. > Jul 19 14:03:13 arrakis systemd[1]: Mounting /usr/local... > Jul 19 14:03:13 arrakis systemd[1]: Mounted /usr/local. > Jul 19 14:03:13 arrakis systemd[1]: Mounting /usr/local/vmware... > Jul 19 14:03:13 arrakis systemd[1]: Mounting /usr/local/winex... > Jul 19 14:03:13 arrakis systemd[1]: Mounted /usr/local/vmware. > Jul 19 14:03:13 arrakis systemd[1]: Mounted /usr/local/winex. (Obvs. I've got some data in /usr/local on the root filesystem which gets mounted over, but that doesn't interfere with the /usr/local mount at all.) I even checked the device creation times, to see if maybe /dev/mapper/arrakis-dv was created too "late" or something, but it seems as though it was actually the first of that bunch: > # ls -lrt --full-time /dev/mapper/arrakis-{local,dv,vmware,winex} > lrwxrwxrwx 1 root root 7 2021-07-19 14:03:12.406271238 -0500 /dev/mapper/arrakis-dv -> ../dm-4 > lrwxrwxrwx 1 root root 7 2021-07-19 14:03:13.649604518 -0500 /dev/mapper/arrakis-winex -> ../dm-5 > lrwxrwxrwx 1 root root 7 2021-07-19 14:03:13.696271181 -0500 /dev/mapper/arrakis-local -> ../dm-0 > lrwxrwxrwx 1 root root 7 2021-07-19 14:03:13.809604509 -0500 /dev/mapper/arrakis-vmware -> ../dm-3 As I mentioned above, I can mount it just fine manually, either with `mount` or `systemctl`. Here's me mounting it w/ `mount`, and confirming its status w/ `systemctl`: > # mount /usr/local/dv > # mount | grep /usr/local/dv > /dev/mapper/arrakis-dv on /usr/local/dv type ext4 (rw,noatime) > # systemctl status usr-local-dv.mount > ● usr-local-dv.mount - /usr/local/dv > Loaded: loaded (/etc/fstab; generated) > Active: active (mounted) since Mon 2021-07-19 14:31:22 CDT; 10s ago > Where: /usr/local/dv > What: /dev/mapper/arrakis-dv > Docs: man:fstab(5) > man:systemd-fstab-generator(8) The specific filesystem that fails to mount changes from boot to boot, and sometimes I do get all of them mounted as I'd expect. I've got a few other non-/usr/local filesystems as well, and sometimes *those* fail to mount too. (For instance, on this particular boot, I just noticed that /games, a root-level filesystem, had failed to mount.) Anyway, I'm at a loss. If systemd were *trying* to mount the filesystem but failing, I'd expect to see some log entries somewhere to that effect. Instead, it's just like they don't even exist at boot time. This has actually been happening for quite awhile now; I've gotten in the habit of just doing a `mount -a` after booting, to get everything mounted properly. It'd be nice to not have to do that, though. If anyone has any ideas, I'm all ears! Thx, CJ

1 0

[arch-general] lvm2-monitor and packagekit seem to give long boot times
by Mike Cloaked 18 Jul '21

18 Jul '21

On a laptop which was previously booting acceptably fast, in recent days it has been booting very slowly. I ran the boot analysis: $ sudo systemd-analyze blame 6.216s packagekit.service 5.664s lvm2-monitor.service 4.532s initrd-switch-root.service 3.694s cups.service 3.016s ldconfig.service 2.744s systemd-logind.service 2.507s systemd-hwdb-update.service Has anyone else seen packagekit and lvm2-monitor services causing slow boot times? There were threads from a couple of years ago where people had problems with lvm2-monitor, and if lvm was not being used, masking that service helped boot times improve (and shutdown times too. So I masked the lvm2-monitor service and the boot time is significantly improved: $ sudo systemd-analyze blame 1.722s cups.service 941ms initrd-switch-root.service 586ms systemd-journal-flush.service 529ms systemd-udevd.service 364ms packagekit.service I also found past threads that suggested that pacman 6 possibly causes some issues with packagekit, so I followed a suggestion to do: $ sudo rm -fr /var/lib/PackageKit/alpm $ sudo systemctl restart packagekit The shutdown time was taking over a minute prior to this, but seems to be improved after cleaning up the packagekit alpm directory. If anyone else has found similar issues and has any workaround to clean things up it would be useful to know about how it was done. These issues have occurred on two old laptops, but not on a relatively new laptop, so possibly some old files from previous versions of packages may have been underlying these issues. Are there any other cleanup suggestions that are needed to completely resolve this slow boot and shutdown issues that anyone is aware of? -- mike c

1 0

[arch-general] google-chrome/chromium and youtube "app"?
by Andy Pieters 16 Jul '21

16 Jul '21

Hi all Every so often, when a notification pops up from youtube and I click on it in the plasma's notification area, a separate youtube player window opens. This separate window looks like a chrome app. However, I cannot find this app in my list of chrome apps. No youtube extension or youtube app or similarly named stuff to be found. I find it difficult to get information about in search because of the generic keywords. Anybody know any thing of this and how to disable it? Many thanks Andy "Aethalides" Pieters

3 3

[arch-general] Xorg segfault when using electron application and second monitor
by LuKaRo 12 Jul '21

12 Jul '21

Hi everyone, since yesterday's update, my Xorg crashes with a segmentation fault as soon as I start an electron application and have a second monitor activated. This is reproducible, a minimum working example looks like this: $ rocketchat-desktop $ xrandr --output DP-1-1 --auto --above eDP-1 --rotate normal $ rocketchat-desktop --disable-gpu $ rocketchat-desktop Starting rocketchat-desktop before activating the external screen works without error, as does starting rocketchat-desktop without GPU acceleration after activating the external screen. However, as soon as I start rocketchat-desktop normally (e.g. with GPU acceleration) Xorg immediately crashes, tty1 appears for a moment, and then my lightdm-gtk-greeter returns, allowing me to log in again. The same thing happens for example with signal-desktop or element-desktop. An example Xorg.log ends like this: [ 16805.080] (II) modeset(0): Allocate new frame buffer 1920x2160 stride [ 16805.230] (II) NVIDIA(G0): Setting mode "DP-1-1: nvidia-auto-select @1920x1080 +0+0 {AllowGSYNC=Off, ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}" [ 16808.392] (EE) [ 16808.392] (EE) Backtrace: [ 16808.392] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x5b) [0x55c4bab6457b] [ 16808.392] (EE) 1: /usr/lib/Xorg (0x55c4baa1e000+0x1511d5) [0x55c4bab6f1d5] [ 16808.392] (EE) 2: /usr/lib/libc.so.6 (0x7f8962b82000+0x3cda0) [0x7f8962bbeda0] [ 16808.392] (EE) 3: /usr/lib/Xorg (0x55c4baa1e000+0xd81f2) [0x55c4baaf61f2] [ 16808.392] (EE) 4: /usr/lib/Xorg (0x55c4baa1e000+0xd9d1c) [0x55c4baaf7d1c] [ 16808.392] (EE) 5: /usr/lib/Xorg (0x55c4baa1e000+0xd8dc6) [0x55c4baaf6dc6] [ 16808.392] (EE) 6: /usr/lib/Xorg (0x55c4baa1e000+0x398ac) [0x55c4baa578ac] [ 16808.392] (EE) 7: /usr/lib/libc.so.6 (__libc_start_main+0xd5) [0x7f8962ba9b25] [ 16808.392] (EE) 8: /usr/lib/Xorg (_start+0x2e) [0x55c4baa57cee] [ 16808.392] (EE) [ 16808.392] (EE) Segmentation fault at address 0x68 [ 16808.393] (EE) Fatal server error: [ 16808.393] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 16808.393] (EE) [ 16808.393] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 16808.393] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 16808.393] (EE) [ 16808.393] (II) AIGLX: Suspending AIGLX clients for VT switch [ 16808.450] (EE) Server terminated with error (1). Closing log file. Hardware is a Lenovo ThinkPad P53 notebook with dual graphics: $ lspci|grep -i vga 00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] 01:00.0 VGA compatible controller: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] (rev a1) Kernel is the latest Linux: $ uname -a Linux 5.12.15-arch1-1 #1 SMP PREEMPT Wed, 07 Jul 2021 23:35:29 +0000 x86_64 GNU/Linux And I'm using the NVIDIA driver: $ pacman -Qe|grep nvidia nvidia 465.31-14 nvidia-lts 1:465.31-12 nvidia-prime 1.0-4 nvidia-settings 465.31-1 I also downgraded to the earliest kernel and nvidia versions I had available from late May: [2021-07-12T18:25:56+0200] [ALPM] downgraded linux-lts (5.10.42-1 -> 5.10.39-1) [2021-07-12T18:25:59+0200] [ALPM] downgraded linux-lts-headers (5.10.42-1 -> 5.10.39-1) [2021-07-12T18:26:00+0200] [ALPM] downgraded linux (5.12.9.arch1-1 -> 5.12.6.arch1-1) [2021-07-12T18:26:02+0200] [ALPM] downgraded linux-headers (5.12.9.arch1-1 -> 5.12.6.arch1-1) [2021-07-12T18:26:03+0200] [ALPM] downgraded linux-hardened (5.12.14.hardened1-1 -> 5.11.22.hardened1-1) [2021-07-12T18:26:06+0200] [ALPM] downgraded linux-hardened-headers (5.12.14.hardened1-1 -> 5.11.22.hardened1-1) [2021-07-12T18:26:06+0200] [ALPM] downgraded nvidia-lts (1:465.31-7 -> 1:465.31-3) [2021-07-12T18:26:06+0200] [ALPM] downgraded nvidia (465.31-7 -> 465.31-4) However, the issue still persits. Any ideas on how to further diagnose this issue? I can provide more information, if needed. I'll try switching Also, is anyone having a similar issue? Kind regards, Lukas

4 4