- Arch-general - lists.archlinux.org

[arch-general] thunar reporting no gvs on wayland/wayfire
by Javier 01 Mar '23

01 Mar '23

Hi ! For those using thunar or nemo under wayland, but not through gnome neither kde, do you know how to make them work with gvfs. On thunar, at least on advanced preferences I can see a big note on yellow warning about the lack of gvfs. On Xorg, with LXQt, thunar doesn't complain at all, and show the trash, and the FS correctly, of course no warnings about gvfs on the advanced preferences. I have gvfs and a bunch of its plugins already installed. An alternative is using nautilus, but it's not respecting $GDK_DPI_SCALE env var, and the gsettings for gnome do not work, so I can't really read the tiny letters. But it does show the trash, so I guess no problems with it. Any one using a gui file manager, hopefully gtk, with gvfs, under wayland/wayfire, and working fine? Thanks ! -- Javier

3 6

What is/are the IPv4 addresses used by archlinux-keyring-wkd-sync? I need to tell iptables
by David C. Rankin 28 Feb '23

28 Feb '23

Arch devs, What is/are the IPv4 address(es) used by archlinux-keyring-wkd-sync? I need to tell iptables not to block them so my logs quit filling up with errors. I cloned the source (pyhon...) and looked, but my feeble python skills were unable to find where the addresses or domains were listed (other than the @..... e-mail address domains for verification purposes) They may change? That is one challenge the use of varying cloud or service provider may pose. Failing there being any fixed set, I guess I could tcpdump the traffic, but if there is a list of IPs that the keyring sync uses, that would be the easiest way to go. -- David C. Rankin, J.D.,P.E.

4 7

6.2 Module Build - all good except for nvidia-390xx
by David C. Rankin 28 Feb '23

28 Feb '23

All, Follow-up from a recent thread on 6.2 kernel module builds. All Arch package modules built fine, as did 6.1 branch of virtualbox. However the nvidia-390xx driver fails to build with: nv-gpu-numa.c:232:47: warning: cast between incompatible function types from XXX to YYY (long type salad omitted) 232 | nv_dir_context_t ats_ctx = { .ctx.actor = (filldir_t)filldir_get_memblock_id }; nv-acpi.c:77:19: error: initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer type ‘int (*)(struct acpi_device *, int)’ [-Werror=incompatible-pointer-types] 77 | .remove = nv_acpi_remove_two_args, The upside is it is a -Werror trip of a warning into an error so there may be a path to work around from a compiler option standpoint, but I've yet to look into that or an actual patch yet. -- David C. Rankin, J.D.,P.E.

3 3

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