- Arch-general - lists.archlinux.org

TeXLive 2023 update
by Rémy Oudompheng 24 Mar '23

24 Mar '23

Hello Texlive packages have been updated to 2023 version in [testing]. Important caveat: these packages do not include the luametatex program. The 'context' command remains mapped to the standard luatex, meaning that (as far as I understand, Context LMTX will not be usable, but Context MkII and MkIV should be fine). luametatex sources are not included in TeXLive sources (there is an AUR package if you want to try it). Regards, Rémy.

2 1

Keep getting SSL certificate failures
by Polarian 24 Mar '23

24 Mar '23

Hello, I did not notice this issue at first, but reflecting back on it now there seems to be a serious issue with my SSL on my laptop. When I was speaking to Erus about a "rotted link" within the AUR, I could not access the website as it kept throwing TLS errors, he could. I assumed it was just because of more strict firefox settings. I have now realised that this plays more of an issue, I am constantly getting errors such as: SSL_ERROR_ACCESS_DENIED_ALERT on firefox, and ERR_SSL_PROTOCOL_ERROR on chromium. This happens to multiple sites, but only to some, there seems to be no link between them. For example: https://web.archive.org/web/20130824024508/http://www.baycom.org/~tom/ham/s… is one such website I am not able to visit on any browser on my laptop. I assume this is an issue with the certificate verification on my laptop or maybe even openssl? I guess you could consider this karma for using packages within testing :P (but hey at least I am testing) If anyone has any ideas on how to diagnose the issue, on what the issue here is, or links to sources I can look into, please let me know. Have a good night, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

6 14

X application preferences
by lacsaP Patatetom 24 Mar '23

24 Mar '23

hi, I would like the `lxtask` application (LXDE task manager) to open systematically in "always on top" mode : is it possible to do this in the `~/.Xresources` file ? otherwise, where can it be configured ? regards, lacsaP.

5 9

Fwd: Spring cleanup '23
by David C. Rankin 23 Mar '23

23 Mar '23

Just a note, I would be nice if the members of the general list could see which packages are orphaned. Currently a developer sign-in is needed. -------- Forwarded Message -------- Subject: Spring cleanup '23 Date: Wed, 22 Mar 2023 19:08:40 +0100 From: Antonio Rojas <arojas(a)archlinux.org> To: arch-dev-public(a)lists.archlinux.org Hello, It is that time of the year again: time for our yearly orphans cleanup. Please head to https://archlinux.org/devel/reports/unneeded-orphans/ and adopt packages that you'd like to keep in the repos. This is also a good opportunity to disown any packages you no longer want to maintain, so others can adopt them or they can be properly maintained in AUR if nobody is interested. If any non-dev TU wants to maintain some orphan in [extra], reply here and I'll move it to [community]. I will start dropping the leftovers to AUR on April 1st. -- David C. Rankin, J.D.,P.E.

2 1

/dev/stderr in early userspace
by lacsaP Patatetom 23 Mar '23

23 Mar '23

hi, I recently noticed that `/dev/stderr` was not present at the very beginning of the boot, in early userspace. if I add `break` parameter to have control during this step and do a `ls` test, this is what I get: ``` [rootfs ]# ls -l /dev/std* ls: /dev/std*: No such file or directory ``` Is there anything special to add/do to get these special devices ? nothing special in my `mkinitcpio.conf`, `base` and `udev` hooks installed/used. just note that the image is made from a chroot with `arch-chroot` with no error/warning. regards, lacsaP.

2 2

linux headers
by lacsaP Patatetom 21 Mar '23

21 Mar '23

hi, I have some questions about the compilation process which I am not familiar with. #1 using ArchLinux PKGBUILD, I recompiled the LTS kernel with a slight change introduced in the block/blk-core.c file and two files were generated : linux-lts-6.1.15-1-x86_64.pkg.tar.zst and linux-lts-headers-6.1.15-1-x86_64.pkg.tar.zst. on the other hand, I had previously compiled packages that used linux-lts-headers-6.1.15-1-x86_64.pkg.tar.zst : do I have to recompile them after the change ? #2 my host kernel has been upgraded to 6.1.19-1-lts : how do I compile to 6.1.15-1-lts from 6.1.19-1-lts? regards, lacsaP.

5 16

Microphone is not working with Microsoft Teams
by Sadeep Madurange 20 Mar '23

20 Mar '23

This is my office workstation, so I have to use Microsoft Teams... My sound system is setup using ALSA and pipewire-alsa. I use Teams on Chromium web browser. The problem is, the other end can't hear anything I say. When I try to use Slack on the same browser, microphone is working fine. What is odd is that with Slack on Chromium, under microphones, I can see two options: "Default" and "sof-hda-dsp, -Default Audio Device". On Teams I can only see the latter. "Default" is the one working for Slack. The `wpctl status` yields the following output: PipeWire 'pipewire-0' [0.3.66, sadeep@quix, cookie:3671373507] └─ Clients: 33. WirePlumber [0.3.66, sadeep@quix, pid:2279] 34. WirePlumber [export] [0.3.66, sadeep@quix, pid:2279] 84. wpctl [0.3.66, sadeep@quix, pid:19873] 98. PipeWire ALSA [chromium] [0.3.66, sadeep@quix, pid:9213] Audio ├─ Devices: │ 46. Tiger Lake-LP Smart Sound Technology Audio Controller [alsa] │ ├─ Sinks: │ 55. Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / DisplayPort 3 Output [vol: 1.00] │ 56. Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / DisplayPort 2 Output [vol: 1.00] │ 57. Tiger Lake-LP Smart Sound Technology Audio Controller HDMI / DisplayPort 1 Output [vol: 1.00] │ * 58. Tiger Lake-LP Smart Sound Technology Audio Controller Speaker + Headphones [vol: 0.50] │ ├─ Sink endpoints: │ ├─ Sources: │ 59. Tiger Lake-LP Smart Sound Technology Audio Controller Headphones Stereo Microphone [vol: 1.00] │ * 60. Tiger Lake-LP Smart Sound Technology Audio Controller Digital Microphone [vol: 0.61] │ ├─ Source endpoints: │ └─ Streams: 96. PipeWire ALSA [chromium] 31. output_FL > Speaker + Headphones:playback_FL [active] 105. output_FR > Speaker + Headphones:playback_FR [active] Video ├─ Devices: │ 40. Integrated Camera [v4l2] │ 41. Integrated Camera [v4l2] │ 42. Integrated Camera [v4l2] │ 43. Integrated Camera [v4l2] │ 44. Integrated Camera: Integrated C [libcamera] │ 45. Integrated Camera: Integrated I [libcamera] │ ├─ Sinks: │ ├─ Sink endpoints: │ ├─ Sources: │ * 47. Integrated Camera (V4L2) │ 49. Integrated Camera (V4L2) │ 51. Built-in Front Camera │ 53. Built-in Front Camera │ ├─ Source endpoints: │ └─ Streams: Settings └─ Default Configured Node Names: -- Regards, Sadeep PGP: 103BF9E3E750BF7E

4 6

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