- Arch-general - lists.archlinux.org

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

IPv6 packet loss issue
by Polarian 28 Mar '23

28 Mar '23

Hello, So I am running Arch Linux on a server and on my laptop, both of which use network manager. Now when I ping, or send a http request to polarian.dev (my website) the first time it works just fine: ~ on ☁ ❯ ping -6 polarian.dev PING polarian.dev(2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2)) 56 data bytes 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=1 ttl=63 time=0.506 ms 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=2 ttl=63 time=0.646 ms 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=3 ttl=63 time=0.512 ms 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=4 ttl=63 time=0.357 ms 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=5 ttl=63 time=0.509 ms ^C --- polarian.dev ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4007ms rtt min/avg/max/mdev = 0.357/0.506/0.646/0.091 ms If I then stop it (as you can see ^C) and then start it again, I get the following: ~ on ☁ took 7s ❯ ping -6 polarian.dev PING polarian.dev(2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2)) 56 data bytes 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=27 ttl=63 time=0.399 ms 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=28 ttl=63 time=0.550 ms 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=29 ttl=63 time=0.357 ms 64 bytes from 2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa (2001:8b0:57a:2385::2): icmp_seq=30 ttl=63 time=0.749 ms ^C --- polarian.dev ping statistics --- 30 packets transmitted, 4 received, 86.6667% packet loss, time 29345ms rtt min/avg/max/mdev = 0.357/0.513/0.749/0.153 ms The first 20-30 packets keep getting lost. When I tcpdump imcp6 during this issue, I get the following: 10:13:21.921967 IP6 _gateway > PolarianServer: ICMP6, redirect, 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa, length 320 10:13:23.958945 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 1, length 64 10:13:23.959028 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 1, length 64 10:13:24.978500 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 2, length 64 10:13:24.978569 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 2, length 64 10:13:25.991827 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 3, length 64 10:13:25.991917 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 3, length 64 10:13:27.005178 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 4, length 64 10:13:27.005270 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 4, length 64 10:13:28.018506 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 5, length 64 10:13:28.018596 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 5, length 64 10:13:29.031841 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 6, length 64 10:13:29.031929 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 6, length 64 10:13:30.045276 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 7, length 64 10:13:30.045408 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 7, length 64 10:13:31.058486 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 8, length 64 10:13:31.058577 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 8, length 64 10:13:32.071837 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 9, length 64 10:13:32.071923 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 9, length 64 10:13:33.085189 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 10, length 64 10:13:33.085258 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 10, length 64 10:13:34.098506 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 11, length 64 10:13:34.098598 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 11, length 64 10:13:35.111589 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 12, length 64 10:13:35.111684 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 12, length 64 10:13:36.124916 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 13, length 64 10:13:36.125009 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 13, length 64 10:13:37.138248 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 14, length 64 10:13:37.138332 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 14, length 64 10:13:38.151827 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 15, length 64 10:13:38.151918 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 15, length 64 10:13:39.165174 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 16, length 64 10:13:39.165270 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 16, length 64 10:13:40.178242 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 17, length 64 10:13:40.178313 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 17, length 64 10:13:41.191585 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 18, length 64 10:13:41.191719 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 18, length 64 10:13:42.205174 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 19, length 64 10:13:42.205266 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 19, length 64 10:13:43.218487 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 20, length 64 10:13:43.218576 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 20, length 64 10:13:44.231826 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 21, length 64 10:13:44.231912 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 21, length 64 10:13:45.245143 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 22, length 64 10:13:45.245253 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 22, length 64 10:13:46.258470 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 23, length 64 10:13:46.258560 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 23, length 64 10:13:47.271944 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 24, length 64 10:13:47.272033 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 24, length 64 10:13:47.272129 IP6 _gateway > PolarianServer: ICMP6, redirect, 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa, length 160 10:13:48.273793 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 25, length 64 10:13:48.273867 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 25, length 64 10:13:48.273969 IP6 _gateway > PolarianServer: ICMP6, redirect, 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa, length 160 10:13:49.275216 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 26, length 64 10:13:49.275288 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 26, length 64 10:13:49.275382 IP6 _gateway > PolarianServer: ICMP6, redirect, 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa, length 160 10:13:50.194693 IP6 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, neighbor solicitation, who has PolarianServer, length 32 10:13:50.194833 IP6 PolarianServer > 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, neighbor advertisement, tgt is PolarianServer, length 24 10:13:50.277192 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 27, length 64 10:13:50.277256 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 27, length 64 10:13:50.277347 IP6 _gateway > PolarianServer: ICMP6, redirect, 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa, length 160 10:13:51.279181 IP6 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa > PolarianServer: ICMP6, echo request, id 4, seq 28, length 64 10:13:51.279255 IP6 PolarianServer > 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa: ICMP6, echo reply, id 4, seq 28, length 64 10:13:51.279352 IP6 _gateway > PolarianServer: ICMP6, redirect, 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa, length 160 10:13:51.419764 IP6 PolarianServer > _gateway: ICMP6, neighbor solicitation, who has _gateway, length 32 10:13:51.419892 IP6 _gateway > PolarianServer: ICMP6, neighbor advertisement, tgt is _gateway, length 24 10:13:53.898667 IP6 _gateway > PolarianServer: ICMP6, redirect, 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa to 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.8.3.2.a.7.5.0.0.b.8.0.1.0.0.2.ip6.arpa, length 136 The ICMP packets are definitely getting to my server, but for whatever reason my server does not respond, until about the 20-30th packet and then it finally responds back to my laptop. Does anybody have any clue why is is occurring? (This is done internally, feel free to ping polarian.dev externally to see if you can reproduce the issue). Thank you, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian(a)polarian.dev

2 3

gui network icon not connected
by alistair cookie 25 Mar '23

25 Mar '23

hello. from CLI, if i do "ip addr show" and "ping google.com" it definitely shows me i'm connected to my network and the Internet. but looking at my network icon on the system tray it says i'm not connected to any AP. a bug?

6 5

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