- Arch-general - lists.archlinux.org

Python-nbxmpp needs updating -> Gajim broken without it
by Polarian 19 Mar '23

19 Mar '23

Hello, https://archlinux.org/packages/community/any/python-nbxmpp/ Needs to be updated, otherwise the gajim version which was released into the testing repository will constantly throw errors. Just a heads up for the testers out there :P -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

3 3

Fwd: bio_check_ro @ blk-core.c
by Pascal 19 Mar '23

19 Mar '23

hi, I come to you for lack of feedback (I think the Linux kernel developers have other cats to whip :-)) would one of you have the answer or a track to follow concerning the question below ? the encountered compilation error is behind the forwarded email. regards, lacsaP. ---------- Forwarded message --------- De : Pascal <patatetom(a)gmail.com> Date: mer. 8 mars 2023 à 14:09 Subject: bio_check_ro @ blk-core.c hi, I'm addressing you because you intervened (commit <https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/blo…>) in the function bio_check_ro @ blk-core.c @ Linux-LTS-6.1.15. the last time I intervened on this file (@ Linux-LTS-5.10.19 for personal use), it was to replace "return false;" by "return true;", which theoretically should prevent the possible writing on a device locked in read-only mode (see here <https://github.com/vitaly-kamluk/Linux-write-blocker/tree/master/kernel> or here <https://github.com/msuhanov/Linux-write-blocker>). with @ Linux-LTS-6.1.15, if I insert "return true;", I now have a compilation error. in your opinion, is there still a need to "fix" blk-core.c to prevent writing to a read-only locked device and if so, can you help me implement this fix? regards, lacsaP. ---------- End forwarded message --------- SYNC include/config/auto.conf CC arch/x86/kernel/asm-offsets.s CALL scripts/checksyscalls.sh DESCEND objtool DESCEND bpf/resolve_btfids CC block/bdev.o CC block/fops.o CC block/bio.o CC block/elevator.o CC block/blk-core.o block/blk-core.c: In function 'bio_check_ro': block/blk-core.c:496:24: error: 'return' with a value, in function returning void [-Werror=return-type] 496 | return true; | ^~~~ block/blk-core.c:488:20: note: declared here 488 | static inline void bio_check_ro(struct bio *bio) | ^~~~~~~~~~~~ cc1: some warnings being treated as errors make[2]: *** [scripts/Makefile.build:250: block/blk-core.o] Error 1 make[1]: *** [scripts/Makefile.build:500: block] Error 2 make: *** [Makefile:2005: .] Error 2

3 9

Driver for Nvidia Geforce GTX 760
by Andy Pieters 18 Mar '23

18 Mar '23

Hi I'm trying to upgrade my 5.18.10 system and the DKMS build is failing for my NVIDIA driver. To debug it I have tried to compile the driver separately out of DKMS, but the issue that keeps coming up with the new kernel (6.2.6) is [1] Sadly, though, my card cannot run a more recent version of the driver. When I compile e.g. the 5xx driver I get a message: NVRM: The NVIDIA GeForce GTX 760 GPU installed in this system is NVRM: supported through the NVIDIA 470.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more So it seems that I am stuck on having to use the 470x drivers, the latest one available from Nvidia is 470.161.03, which fails to compile on Kernel >=6 So what can I do? Stay on Kernel 5.18.10 or is it likely that NVidia or the community will provide a fix for the issue in [1]? Many thanks [1] CC [M] /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-p2p.o /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-acpi.c:84:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] 84 | .remove = nv_acpi_remove_two_args, | ^~~~~~~~~~~~~~~~~~~~~~~ /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-acpi.c:84:19: note: (near initialization for ‘nv_acpi_driver_template.ops.remove’) /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-dma.c:963: warning: "IMPORT_SGT_STUBS_NEEDED" redefined 963 | #define IMPORT_SGT_STUBS_NEEDED 0 | /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-dma.c:957: note: this is the location of the previous definition 957 | #define IMPORT_SGT_STUBS_NEEDED 1 | /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-mmap.c: In function ‘nv_encode_caching’: /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-mmap.c:348:16: warning: this statement may fall through [-Wimplicit-fallthrough=] 348 | if (NV_ALLOW_CACHING(memory_type)) | ^ /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-mmap.c:351:9: note: here 351 | default: | ^~~~~~~ CC [M] /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-pat.o CC [M] /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-procfs.o CC [M] /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-procfs-utils.o CC [M] /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-usermap.o CC [M] /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-vm.o cc1: some warnings being treated as errors CC [M] /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-vtophys.o make[2]: *** [scripts/Makefile.build:252: /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build/nvidia/nv-acpi.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [Makefile:2021: /some/where/sources/nvidia/trunk/src/nvidia/470.161.03/build] Error

2 2

5.19 archinstall script
by Jude DaShiell 17 Mar '23

17 Mar '23

I tried using that script and couldn't get off the language line. The arrow keys didn't work and espeak didn't indicate what keys to use to move down the list of configuration options. Has archinstall been improved since then? 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 (Author, 1940) .

1 0

zenity notifications not available in latest PKGBUILD 3.44.0-2
by Piscium 17 Mar '23

17 Mar '23

As a result of the change below zenity notifications are not available anymore. I am using them in a script. This change was just in the PKGBUILD which is still using the same upstream source. https://github.com/archlinux/svntogit-packages/commit/9b3aff4f5b8c189f2b0dd… The commit message points to this: https://bugs.archlinux.org/task/77607 If webkit is not desired, can't notifications be built some other way? yad has notifications too though they are of a different type, for my use case I preferred the zenity ones.

2 3

Re: Orphaning packages
by Genes Lists 17 Mar '23

17 Mar '23

On 3/14/23 12:50, Tobias Powalowski wrote: > Hi guys, > early spring cleanup on my adopted packages: .. > - mdadm Thanks for all the work you've put into Arch Tobias - it is very much appreciated. Of the packages you listed, I sure hope mdadm will be picked up - this quite obviously is a very important one. I'm sure many of us use RAID in various forms. I use MD for RAID-5/6. Be good if someone were to pick this up and keep it in the official repos and not let it drop to AUR. thank you to all those contributing to Arch. regards, gene

1 0

Systems unbootable
by nihilistzsche 16 Mar '23

16 Mar '23

Since I updated a few days ago with kernels 6.2.6 and lts 6.1.19 all of my systems (a pc acting as a headless server with normal kernel, a server with lts kernel, and a laptop with normal kernel) refuse to boot. While trying to diagnose the server, it gets stuck on “Attempting to mount root”, which is a btrfs partition on an lvm volume. If I boot into a rescue usb, all of my partitions mount successfully. I’ve tried downgrading the kernel inside the rescue environment with no change, so I don’t believe it to be a kernel problem. Journalctl holds no answers. I can’t boot into rescuemode without usb either as it gets stuck trying to mount the root. Any clue what could possibly be causing this? It’s not a problem with impatience I left the server running for thirteen hours a day or so ago with it being unable to mount root. Sent from my iPhone

3 5

[ibus][st] ibus 28 to 26 downgrade tip on st
by Rasmus Liland 16 Mar '23

16 Mar '23

Hello! To arch people using suckless st with ibus and vim like myself: I found that upgrading to ibus 1.5.28 causes _something_ to break when using st, which can be solved by downgrading to e.g. 1.4.26 [1]. I find it hard to debug/provide insight on what is different now ... ibus worked in firefox but not in st, similar to what Vofan described back in 2021 [2]. I thought this might be caused by (1) upgrading from st-0.8.5 to st-0.9.0, (2) st-font2-20190416-ba72400.diff failing on st-0.9.0 ... A separate problem showing up at the same time: chinese characters does not display, for which the ttf-arphic-ukai package has been sufficent before. Solution: install noto-fonts-cjk ... I'm not satisfied with this solution, and I'm not sure this is why it worked, because my *font2 looks like, i.e. I define the ttf-arphic-ukai font from ukai.ttc ... Also, I added the -R flag in the .xinitrc exports [5], and somehow after reading some other thread than [2] decided to export the same to zsh in .zshrc.local [4] ... Also github does not work in suckless surf anymore ... and surf-2.0 works better than the new surf-2.1, which makes me feel dumb. Why can't I get the patches working right ... This might seem like mulitiple issues occurring at the same time, or a mix of separate issues ... I'm happy the old downgrading mentality still works somehow on these many random upgrade problems since I've used arch since way over ten years. Best, Rasmus 👍🏻 [1] doas pacman -U /var/cache/pacman/pkg/ibus-m17n-1.4.18-1-x86_64.pkg.tar.zst /var/cache/pacman/pkg/ibus-sunpinyin-3.0.0rc1+32+gf39c195-2-x86_64.pkg.tar.zst /var/cache/pacman/pkg/ibus-1.5.26-2-x86_64.pkg.tar.zst /var/cache/pacman/pkg/libibus-1.5.26-2-x86_64.pkg.tar.zst [2] https://bbs.archlinux.org/viewtopic.php?id=263381 [3] static char *font2[] = { "Liberation Mono:style=Bold:pixelsize=18:antialias=true:autohint=true", "AR PL UKai CN:style=Book:pixelsize=18:antialias=true:autohint=true", "JoyPixels:style=Regular:pixelsize=18:antialias=true:autohint=true", "NotoEmoji Nerd Font Mono:style=Book:pixelsize=18:antialias=true:autohint=true" }; [5] ibus-daemon -rxR & export GTK_IM_MODULE=ibus export QT_IM_MODULE=ibus export XMODIFIERS=@im=ibus export XIM_PROGRAM="/usr/bin/ibus-daemon -rxR" [4] export GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus XIM_PROGRAM="/usr/bin/ibus-daemon -rxR"

1 0

NVIDIA issues with laptops and external monitors
by Giovanni Santini 14 Mar '23

14 Mar '23

Hi all, I've decided to fix my Xorg issue today and I solved as per my message here: https://bbs.archlinux.org/viewtopic.php?pid=2090064#p2090064 Meanwhile, I did some web searching and found all of these: - https://forums.developer.nvidia.com/t/error-gpu-idling-display-engine-timed… - https://groups.google.com/g/linux.debian.bugs.dist/c/NmUU4ck8k1E - https://github.com/NVIDIA/open-gpu-kernel-modules/issues/419 I am curious where we can "open a bug" towards NVIDIA, if anyone did that already. Also, should I link it to an Arch bug report so that maintainers can track it? Bests, Giovanni

1 0

Wifi Networking Regression in linux-6.2.3
by David Bohman 14 Mar '23

14 Mar '23

There is a fairly serious regression in linux-6.2.3 that kills wifi: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?…

4 5