March 2023 - Arch-general - lists.archlinux.org

Python 3.11 timeline?
by David Rosenstrauch 04 May '23

04 May '23

Anyone know if there's any timeline on when we'll see python 3.11 get released to Arch? I emailed the maintainer about this directly recently, but didn't hear anything back. I know this is a big upgrade, and lots of dependent packages are involved, so this might require some time. I just was wondering if there was any roadmap/timeline for how long that might be. Thanks, DR

6 8

Re: gui network icon not connected
by Rino Mardo 07 Apr '23

07 Apr '23

upon running nmcli, it shows disconnected but the wlan0 have an ip address. i remembered when i finished the installation i only have CLI. also no network connectivity. somehow i managed to have network connectivity by installing the package iwd. after that, i have connection via my wireless and i proceeded to install kde (including plasma-nm). since recalling i'm using iwd package, when i stop that service the GUI network icon still shows all 5 bars but no AP listed. when i restart iwd, i get a list of AP in my area and i also get network connectivity in terminal. so i guess the network icon is the problem then? On Sun, Mar 26, 2023 at 1:55 AM "accounts(a)lrose.de [via Relay]" <noreply(a)relay.firefox.com> wrote: > > Forwarded from wna8xt5uv(a)mozmail.com by Firefox Relay ⁨0⁩ email trackers removed Upgrade for more protection > > On 25. Mar 2023, at 15:18, Doug Newgard <dnewgard(a)outlook.com> wrote: > > What did you enable? What did you configure? YOU did all of this, right? You > should be able to tell us what you did, not the other way around. > > Only because a user installed their system, doesn't mean they completely understand it. It's a continuous learning process, and we should support everyone who's willing to learn. > > In this case, it seems like you're actually using NetworkManager, plasma-nm is a frontend for it. However, it is possible that you have a second network manager or static configuration configured, so network manager backs out. You can check that by typing nmcli in the terminal, it should show you the status of network manager on your system. If it shows connected, then the display applet in your Toolbar is the issue. If it shows disconnected, then you should check what other network manager you have installed, and uninstall it. > > https://wiki.archlinux.org/title/Network_configuration Shows a list of possible options. You should check if any of those besides NetworkManager are installed. > Your dashboard -- "This message was typed on my mobile phone. Please excuse any brevity or hilarious auto correct mistakes." http://about.me/RinoMardo

4 4

Enabling CSM fails, can somebody recommend a bootloader
by Ralf Mardorf 02 Apr '23

02 Apr '23

Hi, I am currently building a new PC. Migrating the drives from an Intel Celeron with integrated GPU, mobo Gigabyte GA-B85M-D3H to an Intel Core i3 13th Gen, mobo Gigabyte B760M DS3H DDR4 does cause some issues. The PC is a Linux multi-boot machine. The old SATA SSDs are all MBR drives, a new NVMe SSD is a GPT drive. The old PC's bootloader is syslinux. The Arch install's root directory holds all kernels, the Arch kernels, but also the kernels from the other Linux installs (an ancient Suse, Ubuntu etc.). Disabling Intel platform trust technology and secure boot works, but enabling CSM (legacy boot) fails. I read that on modern Intel machines CSM cannot be enabled, when using the internal GPU. I wonder if this is correct?! I also read, if I need to stay with EFI boot, that continuing using syslinux for a multi-boot Linux machine without chainloading, by keeping all kernels in one partition, could become a PITA or even impossible. Does anybody know, if it's possible to enable CSM? Maybe I forgot to disable or enable something else, before enabling CSM can work. As a temporarily workaround, to continue building the new PC, I installed Xubuntu, from a pendrive that was at hand. It installed GRUB2, so I can boot Arch Linux from the old MBR drive. If I should need to stay with CSM disabled and if syslinux should not work to boot all Linux installs, is there another alternative bootloader available that is similar to syslinux? If possible I will not stay with GRUB2. FWIW aur/r8125-dkms (chaotic-aur/r8125-dkms) works without issues [1]. Thank you aravance! Regards, Ralf [1] https://aur.archlinux.org/packages/r8125-dkms

4 8

pcspkr loaded, but no bell
by Ralf Mardorf 30 Mar '23

30 Mar '23

Hi, if I turn on the computer, the PC buzzer does beep one time, so it does work for the POST, but the terminal (ROXTerm, with audible bell enabled) is silent, it doesn't beep anymore after using the Arch install from my old PC with my new PC. [rocketmouse@archlinux ~]$ lsmod | grep pcspkr pcspkr 16384 0 [rocketmouse@archlinux ~]$ printf "\abeep! \n" beep! The module is loaded, but nothing, no audible bell. I'm out of ideas. Maybe I'm unable to see the forest for the trees, I still suffer from the after-effects of a COVID infection I had a few days back. Is this a known issue with some new mobos? Am I missing something? Regards, Ralf

3 7

Qwt is currently built with Qt5 - should I mark the package as out-of-date?
by Peyton Murray 30 Mar '23

30 Mar '23

Hi all, Sorry if this is a naive question, but qwt <https://archlinux.org/packages/extra/x86_64/qwt/> is currently being built with Qt5, which is nearing end-of-life <https://endoflife.date/qt>, while Qt6 has been out for a while. I'd like for qwt to be built with Qt6, but I'm not sure if this means the package is out-of-date strictly speaking, so I figured I'd ask here before marking the package as such. What's the right way to deal with this? Best, - Peyton

3 3

Pacman: There are N providers available for X
by Spencer Collyer 29 Mar '23

29 Mar '23

Hi, I'm installing a new system, and using the instructions at https://wiki.archlinux.org/title/Pacman/Tips_and_tricks sections 2.5 and 2.6 to get the list of packages to install from my current system. When I run the `pacman -S --needed - < pkglist.txt` part, I get a few cases where pacman says "There are N providers available for X`. What I did for those cases is look up the providers in the `Package Search` page on the archlinux.org and chose the most recent one. Is that a reasonable strategy to use? Is there a better way to make the decision? Searching the web for that string didn't really provide any useful answers unfortunately. Regards Spencer

8 15

netctl problem
by Fons Adriaensen 29 Mar '23

29 Mar '23

Hello all, Yesterday I assisted (via a text chat) a linux noob to install Archlinux on a laptop. We got so far that the system can boot on its own, and we can login as root. The netctl package is installed. Also the ethernet-dhcp example is copied to /etc/netctl/dhcp and edited for the correct interface (enp0s25). netctl start dhcp runs without reporting any errors, but then ping 8.8.8.8 says 'network unreachable', and ip link shows that enp0s25 is not UP. The network was OK with the ISO of course. I could probably find out what is wrong if I had my hands on the keyboard, but doing it remotely seems more difficult... So what *could* be the problem or missing ? TIA, -- FA

4 5

colored prompt in early userspace
by lacsaP Patatetom 28 Mar '23

28 Mar '23

hi, when you add the `break` parameter to the list of parameters passed when the system boots, you find yourself in an interactive shell that allows you to issue commands, perform tests, and so on... the shell is apparently provided by `ash`. how to have a colored prompt (which visually helps to detach the prompt from the rest) ? the `~/.profile` file mentioned here and there does not seem to be read/used. `/.profile` and `/etc/profile` don't do much better. `ashrc` also tested without success. if the prompt offered at this level can be colored, I think it would not be a luxury to implement it directly in mkinitcpio ;-) regards, lacsaP.

1 1

Re: nginx TLS 1.3 doesn't seem to work
by Polarian 28 Mar '23

28 Mar '23

> So you know how to quote, but choose to never give even the tiniest bit of context when you reply because you think we all keep an entire archive of arch-general locally and never delete anything, just so we can follow your blank replies to threads? When something is a straight forward reply to the previous email, there is no need to quote, because you are replying directly to the email. And yes, I expect you store the email for longer than 2 seconds after reading it, this is not 1980s, you have a few kb of storage spare! > I've been on this list for years, and while I don't participate much, I do read everything. But I don't keep it all, as I expect most people don't. I never said keep it all, I said keep the recent conversations so you know what is going on. > Your attitude sucks. Subjective! Now can we please go back on topic, I would rather my nginx instance supports tlsv1.3, than arguing about when and when not to quote, and also how long we should store emails for! Thank you! -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

2 1

nginx TLS 1.3 doesn't seem to work
by Polarian 28 Mar '23

28 Mar '23

Hello, I was browsing https://onedev.polarian.dev while diagnosing the other SSL issue I was having, and I ave realised that it only supports TLS 1.2, even though I have 1.3 enabled and loaded (confirmed with nginx -t) When I use curl: ~ on ☁ took 2s ❯ curl -vI https://onedev.polarian.dev * Trying 81.187.86.85:443... * Connected to onedev.polarian.dev (81.187.86.85) port 443 (#0) * ALPN: offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: none * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN: server accepted http/1.1 * Server certificate: * subject: CN=onedev.polarian.dev * start date: Mar 14 07:49:09 2023 GMT * expire date: Jun 12 07:49:08 2023 GMT * subjectAltName: host "onedev.polarian.dev" matched cert's "onedev.polarian.dev" * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. * using HTTP/1.1 > HEAD / HTTP/1.1 > Host: onedev.polarian.dev > User-Agent: curl/8.0.1 > Accept: */* > < HTTP/1.1 200 OK HTTP/1.1 200 OK < Server: nginx/1.22.1 Server: nginx/1.22.1 < Date: Fri, 24 Mar 2023 12:03:18 GMT Date: Fri, 24 Mar 2023 12:03:18 GMT < Content-Type: text/html;charset=utf-8 Content-Type: text/html;charset=utf-8 < Connection: keep-alive Connection: keep-alive < X-FRAME-OPTIONS: SAMEORIGIN X-FRAME-OPTIONS: SAMEORIGIN < Set-Cookie: JSESSIONID=node0ksf08v71egm01j4p388blz4e012.node0; Path=/; HttpOnly; SameSite=Lax Set-Cookie: JSESSIONID=node0ksf08v71egm01j4p388blz4e012.node0; Path=/; HttpOnly; SameSite=Lax < Expires: Thu, 01 Jan 1970 00:00:00 GMT Expires: Thu, 01 Jan 1970 00:00:00 GMT < Pragma: no-cache Pragma: no-cache < Cache-Control: no-cache, no-store Cache-Control: no-cache, no-store < * Connection #0 to host onedev.polarian.dev left intact I can see that TLS 1.3 is supported, but for some reason during the handshake it settles on TLS 1.2, why? Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

6 14