- Arch-general - lists.archlinux.org

Nextcloud 29 update, web server cannot resolve /.well-known/webfinger
by David C. Rankin 20 May '24

20 May '24

The following new error/warning is received in the Admin settings after upgrade: Your web server is not properly set up to resolve `.well-known` URLs, failed on: `/.well-known/webfinger` For more details see the documentation ↗. The documentation suggests adding rewrite rules, e.g. <IfModule mod_rewrite.c> RewriteEngine on RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav [R=301,L] RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav [R=301,L] RewriteRule ^\.well-known/webfinger /nextcloud/index.php/.well-known/webfinger [R=301,L] RewriteRule ^\.well-known/nodeinfo /nextcloud/index.php/.well-known/nodeinfo [R=301,L] </IfModule> https://docs.nextcloud.com/server/29/admin_manual/issues/general_troublesho… However, adding the settings to httpd-local.conf and reloading makes no difference. Note: caldav and carddav are handled in /etc/webapps/nextcloud/.htaccess Why isn't webfinger handled there? This has to be set by the package as modifying the file manually triggers a hash violation on the modified file. (that can be worked around, but it's a hack) Is this something that needs to be raised as a bug? -- David C. Rankin, J.D.,P.E.

1 0

ipset v7.21 update - package stop / start exits with failure - but ipset is still running?
by David C. Rankin 20 May '24

20 May '24

Devs, ipset was updated after a recent minor bug with save was fixed. The updated package was installed today. Restarting fails with an error code due to: May 16 14:14:31 valkyrie ipset[62200]: ipset v7.21: Set cannot be destroyed: it is in use by a kernel component May 16 14:14:31 valkyrie systemd[1]: ipset.service: Control process exited, code=exited, status=1/FAILURE The start process then fails: May 16 14:14:31 valkyrie ipset[62203]: ipset v7.21: Error in line 1: Set cannot be created: set with the same name already exists May 16 14:14:31 valkyrie systemd[1]: ipset.service: Main process exited, code=exited, status=1/FAILURE The result is fail2ban is left shutdown after the attempted stop of ipset and its failure to start. Is this a new bug, or is something else wrong? -- David C. Rankin, J.D.,P.E.

2 2

1) No documentation for pacman --ask option 2) pacman gitlab page refers to a 404
by u34＠net9.cf 07 May '24

07 May '24

1) Any point opening a bug about pacman --ask option not documented? [https://bbs.archlinux.org/viewtopic.php?id=35901](https://bbs.archlinux.org… is from 2007. 2) Quoting https://gitlab.archlinux.org/pacman/pacman Please also check open issues in our [historical bug tracker](https://bugs.archlinux.org/index.php?project=3) before opening a new issue here. Shouldn't the url point to the new archive? -- u34

2 2

hibernation stopped working
by Frank 04 May '24

04 May '24

Good evening, I have an up-to-date (daily updates) Arch system running Hyprland and since yesterday or the day before yesterday hibernation stopped working. Kernel version is 6.8.8-arch1-1 I have the following line in my hypridle.conf: listener { timeout = 1800 # 30min on-timeout = systemctl suspend-then-hibernate # suspend pc } This used to work flawlessly. When system is hibernating now it's crashing. This is the journal output: 9:27:11 systemd: Stopped target Bluetooth Support. 09:27:11 kernel: PM: hibernation: hibernation entry 09:27:11 systemd-sleep: Performing sleep operation 'hibernate'... 09:27:11 bluetoothd: Battery Provider Manager destroyed 09:27:11 systemd-sleep: System returned from sleep operation 'suspend- then-hibernate'. 09:27:11 bluetoothd: Endpoint unregistered: sender=:1.41 path=/MediaEndpoint/A2DPSink/aptx_hd 09:27:11 dbus-broker: A security policy denied :1.5 to send method call /midi/profile:org.blue z.GattProfile1.Release to :1.42. 09:27:11 bluetoothd: Endpoint unregistered: sender=:1.41 path=/MediaEndpoint/A2DPSource/ldac 09:27:11 kernel: PM: suspend exit 09:27:11 kernel: Bluetooth: hci0: Firmware Version: 132-3.24 09:27:11 kernel: done. 09:27:11 kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 09:27:11 kernel: Restarting tasks ... 09:27:11 kernel: OOM killer enabled. 09:27:11 kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8 09:27:11 kernel: [drm] JPEG decode initialized successfully. 09:27:11 kernel: amdgpu 0000:04:00.0: amdgpu: SMU is resumed successfully! 09:27:11 kernel: [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR 09:27:11 kernel: usb 1-4.4: reset full-speed USB device number 5 using xhci_hcd 09:27:11 kernel: ata2: SATA link down (SStatus 0 SControl 300) 09:27:11 kernel: ata1: SATA link down (SStatus 0 SControl 300) 09:27:11 kernel: nvme nvme0: 12/0/0 default/read/poll queues 09:27:11 kernel: [drm] PSP is resuming... 09:27:11 kernel: ACPI: EC: event unblocked 09:27:11 kernel: CPU15 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf 09:27:11 kernel: CPU14 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe 09:27:11 kernel: CPU13 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd 09:27:11 kernel: CPU12 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc 09:27:11 kernel: CPU11 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb 09:27:11 kernel: CPU10 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa 09:27:11 kernel: CPU9 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9 9:27:11 kernel: CPU9 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9 09:27:11 kernel: CPU8 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8 09:27:11 kernel: CPU7 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7 09:27:11 kernel: CPU6 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6 09:27:11 kernel: CPU5 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5 09:27:11 kernel: CPU4 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4 09:27:11 kernel: CPU3 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3 09:27:11 kernel: CPU2 is up 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2 09:27:11 kernel: CPU1 is up 09:27:11 kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on 09:27:11 kernel: ACPI: FW issue: working around C-state latencies out of order 09:27:11 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1 09:27:11 kernel: Enabling non-boot CPUs ... 09:27:11 kernel: LVT offset 0 assigned for vector 0x400 09:27:11 kernel: AMD-Vi: Virtual APIC enabled 09:27:11 kernel: ACPI: PM: Restoring platform NVS memory 09:27:11 kernel: smpboot: CPU 15 is now offline 09:27:11 kernel: Spectre V2 : Update user space SMT mitigation: STIBP off 09:27:11 kernel: smpboot: CPU 14 is now offline 09:27:11 kernel: Disabling non-boot CPUs ... 09:27:11 kernel: ACPI: PM: Saving platform NVS memory 09:27:11 kernel: [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) 09:27:11 kernel: printk: Suspending console(s) (use no_console_suspend to debug) 09:27:11 kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds) 09:27:11 kernel: OOM killer disabled. 09:27:11 kernel: Freezing user space processes completed (elapsed 0.001 seconds) 08:57:09 kernel: Filesystems sync: 0.006 seconds 08:57:09 kernel: PM: suspend entry (deep) 08:57:09 systemd-sleep: Performing sleep operation 'suspend'... 08:57:09 systemd: Starting System Suspend then Hibernate... Any idea what's going wrong here? THX Frank

3 5

Why is apt in the Repo?
by Chime Hart 03 May '24

03 May '24

Hi All: I was sure surprised to be able to install apt, however, in /etc/apt/sources.list is empty. The man-page only seems to make references to Debian versions. So, inquiring minds wanna know. Right this second I don't remember which I used, pacman or yay? Thanks so much in advance Chime

2 1

re/fwd: Archlinux Newsfeeds Broken -- Or am I just lucky?
by David C. Rankin 02 May '24

02 May '24

> All, > > The Arch newsfeeds for Arch Linux Recent news and Arch Linux Recent > packages (e.g. https://archlinux.org/feeds/packages/) are no longer > delivering to me. Is there are problem with the news feeds or is there > something that would just stop Thunderbird from getting them? > > I haven't changed anything and clicking on the "Validate" in the account > config in tbird brings up the page showing they are valid, but I am not > getting anything anymore? > > Is it just me? I check the archlinux.org site, but found no notices? Feed is working fine. It looks like it was just me. My feed was out from 4/29/24 at 14:42 (last message from feed) until 5/1/24 at 1:34. (which missed the 6.8.8 kernel going into core I was waiting on) I'll chock this up to a CSOK issue. I've got no other explanation. ** CSOK (cat stepping on keyboard...) -- David C. Rankin, J.D.,P.E.

1 0

Issue related to the file system hierarchy for operating systems using the systemd service manager
by Ralf Mardorf 01 May '24

01 May '24

Hi, when running extra/audacity from command line it runs into issues, but doesn't provide any output and it seems not to start. When running extra/tenacity from command line it shows that there is an issue with duplicated plugins. It ignores the duplicated plugins and after a while it does start. The culprit is a link. $ /bin/ls -ld /usr/lib{,64} drwxr-xr-x 460 root root 524288 May 1 17:37 /usr/lib lrwxrwxrwx 1 root root 3 Apr 7 20:02 /usr/lib64 -> lib "1.5 Does Arch follow the Linux Foundation's Filesystem Hierarchy Standard (FHS)? Arch Linux follows the file system hierarchy for operating systems using the systemd service manager. See file-hierarchy(7) for an explanation of each directory along with their designations. In particular, /bin, /sbin, and /usr/sbin are symbolic links to /usr/bin, and /lib and /lib64 are symbolic links to /usr/lib." - https://wiki.archlinux.org/title/Frequently_asked_questions#Does_Arch_follo…'s_Filesystem_Hierarchy_Standard_(FHS)? What should I do? Report a bug against a package or something else? Regards, Ralf

2 2

Archlinux Newsfeeds Broken -- Or am I just lucky?
by David C. Rankin 01 May '24

01 May '24

All, The Arch newsfeeds for Arch Linux Recent news and Arch Linux Recent packages (e.g. https://archlinux.org/feeds/packages/) are no longer delivering to me. Is there are problem with the news feeds or is there something that would just stop Thunderbird from getting them? I haven't changed anything and clicking on the "Validate" in the account config in tbird brings up the page showing they are valid, but I am not getting anything anymore? Is it just me? I check the archlinux.org site, but found no notices? -- David C. Rankin, J.D.,P.E.

1 0

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