users December 2025

users@lists.fedoraproject.org

21 participants
14 discussions

grub won't show menu in f43 VM
by Robert McBroom 08 Dec '25

08 Dec '25

Installed Fedora-Cloud-Base-Generic-43-1.6.x86_64.qcow2 in a qemu/kvm virtual machine. It doesn't give me the grub menu on boot. There are three kernels available and I would also like to put options on the grub start. What is inhibiting the grub menu on the VM?

2 2

Can't reboot system
by Paolo Galtieri 08 Dec '25

08 Dec '25

Folks, I have a F42 system which since yesterday has been in a state in which I cannot shut it down or reboot it. Any attempt just l Iogs me out. I use MATE as my desktop and trying to shut it down via the system menu ends up logging me out. If I try using the shutdown button in the upper right just presents the restart/shutdown menu but clicking on one or the other does nothing. Even if I try running sudo shutdown -r now from a terminal window just hangs. I would try just hitting the system's power button, but based on what happened to my 2 other Linux boxes I am very hesitant to do this. When I tried this on my 2 other Linux boxes they now only boot into emergency mode. Does anyone have any suggestions? Curiously one of the systems which now fails to boot Linux also runs Windows which boots just fine. Any help would be appreciated. Paolo

6 12

Re: How to get to a kernel selection screen at boot
by Stephen Morris 08 Dec '25

08 Dec '25

>>>>>> I also have the GRUB_ENABLE_BLSCFG=false option as well as I >>>>>> found that caused me issues with the grub menu as well. >>>>> >>>>> That's not good. You've kind of broken things... >>>>> >>>> Thanks Samuel, what has it broken? It's been a long time since I >>>> did this change and now I don't remember exactly what the issue >>>> was, but I think it was something to do with the way the grub menu >>>> was being presented. >>> >>> Fedora uses BLS by default. I don't know if the various kernel >>> install bits can handle not doing that. I guess they must somewhat >>> since your system is still working. The grub boot entries should be >>> in /boot/loader/entries/. >> Yes, in my case all 4 boot entries are there. They have an entry in >> them I've never seen before. When they blacklist nouveau they also >> blacklist nova_core, what is nova_core? >> I think why I disabled BLS, was for the same reason I overwrite what >> grubby does, using BLS was causing the GRUB_DISABLE_SUBMENU=false to >> be ignored for the grub menu generation. >> >> Just as a slightly off topic question, one of the entries in /boot/ >> loader/entries is >> 916eba9527bd4f4cbcca61769a8beae4-6.17.1-300.fc43.x86_64.conf, why >> does sudo cat /boot/loader/entries/*6.17.1* not work to list its >> contents? > > Did you mean to send this directly? Sorry Samuel, I didn't mean to send this directly. I think the issue might have been that this thread was one where I wasn't given the option of "Reply List", I was only given "Reply" or "Reply All" as happens from time to time. > > What happens when you run that command? > When I run the command I get the following: sudo cat /boot/loader/entries/*6.17.1* [sudo] password for steve: cat: '/boot/loader/entries/*6.17.1*': No such file or directory regards,

4 6

How to get to a kernel selection screen at boot
by Terry Hurlbut 08 Dec '25

08 Dec '25

Everyone: I've mentioned this before, but still don't have an answer that gives a consistent result. Since I installed F43 on my system - and I mean a fresh, clean install, overriding old swap and home partitions (I had my data saved on another drive, so that's unaffected) - booting up goes to a message that reads: "GRUB boot loader: Welcome to GRUB." Five seconds later, it goes through its startup routines. (I removed "rhgb quiet" from the list of boot-up command-level switches). Someone suggested I was getting that five-second Welcome screen because I had only one kernel installed at the time. Well, that was two weeks ago, and the system has had several updates. And rarely I /do/ get to a screen listing three kernels to choose from - so I already have more than one. So: where do I find the file that governs whether to just "go with the latest kernel," and what command do I change, remove, or add? FYI, I installed the new KDE Plasma Desktop Edition. Several updates later, it's been running better than ever - all except for that one thing. -- Temlakos <temlakos(a)gmail.com>

12 19

OpenVPN client connects but no traffic (“write to TUN/TAP : Invalid argument (fd=-1,code=22)”)
by Paul Smith 07 Dec '25

07 Dec '25

Dear All, I’m having trouble getting an OpenVPN connection to work properly on Fedora and would appreciate some advice. Distribution: Fedora (fully up to date from the official repos) OpenVPN: 2.6.17 (from Fedora repos) Mode: TCP, using the .ovpn configuration supplied by the provider ________________________________ What works If I run OpenVPN from the command line, the TLS handshake completes and the tunnel appears to come up: sudo openvpn --config /path/to/provider-tcp.ovpn --dev tun0 --verb 4 2>&1 | tee /tmp/ovpn-test-tcp.log From the log (edited and anonymised): PUSH: Received control message: 'PUSH_REPLY,sndbuf 393216,rcvbuf 393216, redirect-gateway def1,dhcp-option DNS 8.8.8.8,register-dns, route-gateway 10.15.0.1,topology subnet,ping 10,ping-restart 60, socket-flags TCP_NODELAY,ifconfig 10.15.0.4 255.255.0.0,peer-id 0, cipher AES-256-GCM' TUN/TAP device tun0 opened do_ifconfig, ipv4=1, ipv6=0 net_addr_v4_add: 10.15.0.4/16 dev tun0 net_route_v4_add: /32 via dev [NULL] net_route_v4_add: 0.0.0.0/1 via 10.15.0.1 dev [NULL] net_route_v4_add: 128.0.0.0/1 via 10.15.0.1 dev [NULL] Initialization Sequence Completed The interface looks fine: ip addr show tun0 gives something like: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP inet 10.15.0.4/16 brd 10.15.255.255 scope global tun0 The routing table also seems consistent with “redirect-gateway def1”. For example: ip route get 8.8.8.8 returns: 8.8.8.8 via 10.15.0.1 dev tun0 src 10.15.0.4 uid 1000 ________________________________ What does NOT work Despite the above, there is no traffic over the tunnel. Examples: ping -c3 10.15.0.1 ping -c3 8.8.8.8 curl -4 --connect-timeout 10 https://api.ipify.org All of these time out (100% packet loss for ping, no response for curl). When I disconnect the VPN, normal Internet over the Ethernet interface works fine. To exclude firewall issues, I temporarily disabled everything: sudo systemctl stop firewalld 2>/dev/null || true sudo nft flush ruleset 2>/dev/null || true sudo iptables -F 2>/dev/null || true sudo ip6tables -F 2>/dev/null || true The behaviour is the same: OpenVPN connects, but I can’t even ping the VPN gateway (10.15.0.1), and the log keeps printing: write to TUN/TAP : Invalid argument (fd=-1,code=22) repeatedly. ________________________________ Extra oddity: many stale tunX interfaces/routes Because I’ve been testing several times (and previously experimented with some scripts), ip route now shows dozens of tunXX routes with state DOWN and linkdown, even when no OpenVPN process is running. Example (excerpt, anonymised): 10.15.0.0/16 dev tun28 proto kernel scope link src 10.15.0.3 metric 500 linkdown 10.15.0.0/16 dev tun53 proto kernel scope link src 10.15.0.5 metric 500 linkdown ... Even after: sudo pkill openvpn sudo ip route flush table main sudo systemctl restart NetworkManager many of these routes still remain. I’m not sure whether this is just cosmetic or a symptom of a deeper problem. ________________________________ NetworkManager plugin also fails I also tried importing the same .ovpn file into NetworkManager and bringing it up via: nmcli connection up "ovpn" --show-secrets This consistently fails with: Error: Connection activation failed: Unknown reason In the journal I see messages like: vpn["ovpn"]: starting openvpn vpn["ovpn"]: dbus: failure: connect-failed (1) The OpenVPN NM service binary is present and executable: /usr/libexec/nm-openvpn-service also exists. The connection profile (anonymised) looks roughly like: vpn.service-type: org.freedesktop.NetworkManager.openvpn vpn.data: auth = SHA256, ca = /path/to/ca.pem, cipher = AES-256-CBC, connection-type = password, dev = tun, mssfix = yes, proto-tcp = yes, remote = vpn.example.com:4443, ta = /path/to/ta.key, ta-dir = 1, username = vpn.secrets: ________________________________ Question Has anyone seen this combination of symptoms on Fedora? OpenVPN 2.6.17 connects, tun0 is UP with an IP, routes are installed, but: ping 10.15.0.1 and any other IP via the tunnel fail, and the log shows repeated write to TUN/TAP : Invalid argument (fd=-1,code=22). There are many stale tunX interfaces and routes left behind even when there is no OpenVPN process, and even after flushing routes and restarting NetworkManager. NetworkManager’s OpenVPN plugin refuses to bring up the connection with dbus: failure: connect-failed (1) even though nm-openvpn-service is present. Is there anything obvious I might be doing wrong on Fedora (kernel/module, permissions on /dev/net/tun, SELinux, interaction with NetworkManager, etc.) that could explain the write to TUN/TAP : Invalid argument and the lack of traffic, even though the control channel is clearly established? Any hints on how to systematically debug this on Fedora (and/or what extra logs to collect) would be very welcome. Best regards, Paul

1 0

Slightly OT (but not really) Linus talks PCs
by Patrick O'Callaghan 05 Dec '25

05 Dec '25

Linus Tech Tips talks to Linus Torvlads about PCs, among other things. I found this quite entertaining: https://www.youtube.com/watch?v=mfv0V1SxbNA Guess what distro they install ... poc

4 4

OT: rpmbuild SPEC error
by Ranjan Maitra 03 Dec '25

03 Dec '25

Hi, I posted this twice earlier, but it did not show up because the error message it moving it a tad more than 60KB which makes it require moderator approval (which may well be delayed because of the holiday weekend in the US). So, here is a repost. Hopefully, someone can get to it before the 24-hour clock on the fpaste runs out (I do not see how to increase that time.) I am the package maintainer of SLiM, the Simple Login Manager. While trying to take care of an automated BZ request, I decided to look into also updating the package. Because upstream is not very responsive, as the author is sadly indisposed for the long-term, I moved the code to github at https://github.com/maitra/slim-fork after having made some of the corrections (suggested earlier here) which make the package compile without error. And also bumped up the cmakeminimum which is what triggered the BZ request. However, when I go to build the RPM with the spec file, I get an error. THe spec file is here: https://paste.centos.org/view/96e6b7db However, I get an error which does not show up when I do the compilation outside the spec file, which is really perplexing to me so my guess is that the problem is with the spec file, and I wonder if anyone more knowledgable on SPEC files can give me some suggestions. Here are the errors I get when I run rpmbuild -bb slim.spec. https://paste.centos.org/view/8f71e2c5 I do not understand why these errors do not show up when I compile the package (outside of the SPEC file). Many thanks again for any help, and best wishes, Ranjan

3 7

List Mails not Being Echoed Back to me
by Stephen Morris 03 Dec '25

03 Dec '25

Hi, Could someone give me the mail name and address of the list moderator please. Since upgrading my hardware and doing a fresh install of F43, along with a fresh install of the upstream Thunderbird Daily, any mails I send to the list or any replies I send to the list are not being echoed back to me unless I put my email address as a CC. I had the same issue under F42 but the issue of replies not being echoed back to me was rectified by the moderator (I hadn't raised the issue of new mails not being echoed back), so I need to contact that person again. -- regards,

4 13

Network USB Dongle Connection Issue
by Stephen Morris 03 Dec '25

03 Dec '25

Hi, I've just purchased a Netgear Nighthawk Wifi 7 Tri-band router (RS300) along with a Netgear Nighthawk Tri-band USB 3.0 dongle (A9000). The issue I have is the A9000 won't stay connected to F42 and keeps disappearing from the Networks list in Network Manager. Lsusb sees the dongle without any issues but I can't identify what chipset the dongle is using. Under windows it has a driver that is supplied with the dongle. From what I can see from net searches Linux Kernels 5.18 and above have an A9000 driver built in to the kernel. It seems from the network definition in Network Manager that Linux has selected WPA3-SAE for the wifi security, but changing the security to WPA/WPA2 doesn't change the dongles usability. Netgear is saying that the A9000 is usable under Windows10, Windows 11, Linux and Mac, but it does say to search netgear.com for the latest info on Linux and Mac support, but I can't find anything. Can someone suggest what I can look at to determine why F42 isn't retaining the device and why when it auto-connects it keeps deactivating it? I've had a look at dmesg and I can see lots of messages for the device around authentication time out, plus this message " [ 2573.919926] iwlwifi 0000:05:00.0: Unhandled alg: 0x707" regards,

5 22

Pi-Hole on Fedora
by Patrick O'Callaghan 02 Dec '25

02 Dec '25

Is anyone using Pi-Hole on Fedora? The project page at: https://docs.pi-hole.net/main/prerequisites/#supported-operating-systems says Fedora is supported, but installation involves either a Docker container (I don't know if it works with podman) or running a Bash script, and there doesn't appear to be an RPM version. I guess I'm concerned about how easy it is to remove if something goes wrong. poc

1 0