- Arch-general - lists.archlinux.org

One to remember linux 6.1.12.arch1-1 and linux-lts 6.1.13-1
by David C. Rankin 25 Feb '23

25 Feb '23

All, This is the first time I can remember since 2009 that LTS is ahead of the regular kernel: linux 6.1.12.arch1-1 linux-lts 6.1.13-1 Here is to hoping 6.2 doesn't bring a lot of surprises and kernel module issues... -- David C. Rankin, J.D.,P.E.

4 3

pacman -Syu fails - python-augeas (existing files) needed by certbot-apache?
by David C. Rankin 25 Feb '23

25 Feb '23

All, Update of a server failed today with: (35/35) checking for file conflicts [######################################] 100% error: failed to commit transaction (conflicting files) python-scapy: /usr/lib/python3.10/site-packages/test/__init__.py exists in filesystem (owned by python-augeas) python-scapy: /usr/lib/python3.10/site-packages/test/__pycache__/__init__.cpython-310.opt-1.pyc exists in filesystem (owned by python-augeas) python-scapy: /usr/lib/python3.10/site-packages/test/__pycache__/__init__.cpython-310.pyc exists in filesystem (owned by python-augeas) Errors occurred, no packages were upgraded. The python-augeas package is needed by certbot-apache. How to resolve the conflict? -- David C. Rankin, J.D.,P.E.

4 5

Alacritty crashes on start
by Paul Schaefer 23 Feb '23

23 Feb '23

Hey, a few days ago, I updated my old system. Since this update Alacritty refuses to start on Sway. When started, it crashes with the following message: [wayland-client error] Attempted to dispatch unknown opcode 0 for wl_shm, aborting. [1] 723599 IOT instruction (core dumped) alacritty If I start Alacritty on X(-Wayland) by setting WAYLAND_DISPLAY= , everything works fine. On my second machine (using the same software combination) Alacritty just works. Can you help me debugging this issue? Thank you!

1 0

Status of paraview package
by Åsmund Ervik 23 Feb '23

23 Feb '23

Hi, The paraview package is at version 5.10 and has been flagged as out-of-date since October. Are there any blockers for updating the package to 5.11? Regards, Åsmund

5 8

vim 9.0 bash syntax highlight broken for large if [ cond ]; then ... else ... fi block
by David C. Rankin 22 Feb '23

22 Feb '23

All, After the vim 9.0 update the syntax highlight in my .bashrc is off for: if [ "$EUID" -eq 0 ]; then ## suff else ## sudo stuff fi (generic blocks used in both user/root .bashrc) Where about a dozen alias set for various combinations of systemctl and pacman commands are set. Before this past time looking at the .bashrc, highlight had been fine (don't know if that was 1, 2, 3 months ago), but now it is hosed. Image of the wonky highlight: https://paste.opensuse.org/pastes/89a2016e0483 (good 24 hours) -- David C. Rankin, J.D.,P.E.

4 5

libmysofa-1.3.1-2 hidden and breaks pipewire - with fix
by Genes Lists 21 Feb '23

21 Feb '23

Problem: This package is available in community, but pacman cannot find it - which breaks pipewire-audio due to missing soname depends. pacman only finds 1.3.1-1 which is missing the needed provides. Cause: The reason appears to be that while the package is available, it was not added to the repo database - effectively hiding the package. I've heard of quite a few folks who've been bitten by this. Fix: add this to the repo Anyway fix should be quick and easy :) thanks. gene

3 3

I think I found a quite severe bug, what is the next step?
by Storm Dragon 19 Feb '23

19 Feb '23

Howdy, I started this new topic, because I think we have gone from weird quirk to serious bug. Fenrir, in the console, uses /dev/vcsa and /dev/vcsu. Here is the output of ls -l for each of them: [storm@mjollnir dev] $ ls -1l vcsa* crw-rw---- 1 root tty 7, 128 Feb 15 18:30 vcsa crw-rw---- 1 root tty 7, 129 Feb 15 18:30 vcsa1 crw-rw---- 1 root tty 7, 130 Feb 15 18:30 vcsa2 crw-rw---- 1 root tty 7, 131 Feb 15 18:30 vcsa3 crw-rw---- 1 root tty 7, 132 Feb 15 18:30 vcsa4 crw-rw---- 1 root tty 7, 133 Feb 15 18:30 vcsa5 crw-rw---- 1 root tty 7, 134 Feb 15 18:30 vcsa6 crw-rw---- 1 root tty 7, 135 Feb 15 18:30 vcsa7 [storm@mjollnir dev] $ ls -1l vcsu* crw-rw---- 1 root tty 7, 64 Feb 15 18:30 vcsu crw-rw---- 1 root tty 7, 65 Feb 15 18:30 vcsu1 crw-rw---- 1 root tty 7, 66 Feb 15 18:30 vcsu2 crw-rw---- 1 root tty 7, 67 Feb 15 18:30 vcsu3 crw-rw---- 1 root tty 7, 68 Feb 15 18:30 vcsu4 crw-rw---- 1 root tty 7, 69 Feb 15 18:30 vcsu5 crw-rw---- 1 root tty 7, 70 Feb 15 18:30 vcsu6 crw-rw---- 1 root tty 7, 71 Feb 15 18:30 mcsu7 And now, things get interesting: [storm@mjollnir dev] $ sudo \cat /dev/vcsa cat: /dev/vcsa1: No such device or address Same for /dev/vcsu also including 1-7 for each of them. Other tests I tried. Importing them with python results the same for vcsa and vcsu: [root@mjollnir ~]# python Python 3.10.9 (main, Dec 19 2022, 17:35:49) [GCC 12.2.0] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import os >>> useVCSA = os.access('/dev/vcsa', os.R_OK) >>> print(useVCSA) True >>> vcsa= open("/dev/vcsa",'rb') >>> d = vcsa.read() Traceback (most recent call last): File "<stdin>", line 1, in <module> OSError: [Errno 6] No such device or address >>> I hope I have provided enough information. I'm kind of stuck at this point. What should I do next? This happened yesterday after updates. I can add the pacman logs from yesterday if those are needed. Thanks, Storm

4 9

Re: Miracast help?
by Giovanni Santini 19 Feb '23

19 Feb '23

Hi Petr, Re-adding the mailing list to the conversation :) Didn't quote your previous email as I may have a more fundamental issue. So, I have checked my WiFi card via the command here: https://github.com/albfan/miraclecast/blob/master/res/miracle-utils.sh#L112 it seems to not support P2P mode nor commands. Are those required for connecting to a Miracast device? I believed that as long as the card understand the packages it should work and the card seems to have support for RX / TX of P2P-client, P2P-go and P2P-device frames. It mentions also the command "start_p2p_device" as supported. Bests, / Giovanni

3 2

TTY behaving strangely after yesterday update
by Storm Dragon 17 Feb '23

17 Feb '23

Howdy, I use the fenrir screen reader, and after updating yesterday, it will no longer work in the console. I have tested it in a PTY, and it works fine there, so it's not a change in the screen reader itself. Also, it is the same version that was being used before the update. Also, interestingly, screen gives an error when I launch it now. It did not used to do this, but it flashes up an error that I can't review because it's gone as quickly as it appears. I probably wouldn't have noticed it at all if it wasn't for speakup reading the error. So I'm probably not spelling this exactly, but it sounds like it is saying: /home/storm/.screenrc expected character, x, or ioctl 38 The interesting part from the Fenrir log is, there are quite a few of these errors: ERROR 2023-02-16 06:55:48.420559: VCSA:updateWatchdog:[Errno 6] No such device or address I have checked and all the /dev/vcs stuff is there. It even seems to have the correct permissions and ownership. Here is a sample: crw-rw---- 1 root tty 7, 1 Feb 15 18:30 /dev/vcs1 Does anyone have any idea what may be going on with this? Oh, and I'm using Linux-lts: linux-lts 5.15.94-1 Thanks, Storm

3 3

cannot resolve "libxml"
by Ralf Mardorf 17 Feb '23

17 Feb '23

Hi, isn't the issue shown below worth a comment on "Latest News" and on arch-announce? [rocketmouse@archlinux ~]$ sudo pacman -Syu [snip] resolving dependencies... warning: cannot resolve "libxml", a dependency of "yoshimi" :: The following package cannot be upgraded due to unresolvable dependencies: yoshimi :: Do you want to skip the above package for this upgrade? [y/N] [snip] "libxml (virtual)" - https://archlinux.org/packages/community/x86_64/yoshimi/ Regards, Ralf

3 4