Oh, that’s good to know. So I can just install x11 on my Fedora no problem whatsoever?

Only shame is that they don’t recommend dual hooting with windows, which is a requirement for me

Thanks! I’m downloading nobara now, any tips to get it to work as expected?

I’ve done some more digging and indeed, the AMD integrated GPU is being used. Optimus seems like a good option, but then apparently I’d have to use x11 as the desktop renderer because Wayland doesn’t play nice with nvidia.

As far as I can see, x11 will be deprecated not too long from now?

Thanks for your answer! I had 535 installed on Debian 12 and 570 on Fedora 42. This is the result of fastfetch (neofetch is EOL). Let me know if you need any more info or if you think you have something that might help. Thanks!

System Details:

• OS: Fedora Linux 42 (Workstation Edition)

• Host: Lenovo Legion 5 Pro 16ACH (82JQ)

• Kernel: Linux 6.14.5-300.fc42.x86_64

• Uptime: 30 mins

• Locale: en_GB.UTF-8

Hardware:

• CPU: AMD Ryzen 7 5800H (16) @ 4.46 GHz

• GPU 1: NVIDIA GeForce RTX 3060 Mobile

• GPU 2: AMD Radeon Vega Series

• Memory: 4.30 GiB / 27.25 GiB (16%)

• Swap: 0 B / 8.00 GiB (0%)

• Disk (/): 23.09 GiB / 243.14 GiB (9%)

• Display: 2560x1600 @ 60 Hz

• Battery: 60% [AC Connected]

Software Environment:

• DE: GNOME 48.1

• WM: Mutter (Wayland)

• Theme: Adwaita

• Packages: 2490 (rpm), 12 (flatpak)

• Shell: bash 5.2.37

• Terminal: Ptyxis 48.1

• Network: 192.168.2.14/24 (wlp4s0)

Interesting, thanks! Do you happen to have a link to it?

It seems indeed the nvidia drivers disable wayland. I played around in Firefox settings a bit more and a setting around input delay seems to have fixed it for now. I hope it stays that way. If not, I’ll migrate to chromium

Smooth as butter on a chromium browser, which is nice but also annoying haha

It’s x11, when I check my desktop environments I only have gnome and gnome classic

I checked in about:support and Firefox is using x11, so maybe wayland isn’t installed

I don’t have experience with wayland yet, so I’ll need to check if it’s available on my installation. Do you now how I can run Firefox in wayland?

The drivers are the latest officially supported Debian ones, they should not be the main issue here. But I can give it a look, thanks!

Thanks! Unfortunately my VPN is OpenVPN and doesn’t support Wireguard yet :(

Cool! And you can easily control the mini router from your devices so that it connects to the hotel WiFi or whatever network you want?

Interesting! I’m new to this, this is really valuable! What made you choose this approach?

Understood, yes it’s a kill switch. I’ll test your set of rules in a bit and let you know!

Except that that set of rules doesn’t work, or do you mean defining a default gateway?

Interesting, but by the time I apply the rules the VPN connection has already been established. Wouldn’t that remove the necessity for the last line?

I guess what I’m really trying to do is make sure that whatever happens, if the vpn fails (tun0), there is no more communication with the Internet.

Hmm, but wouldn’t that allow applications to communicate on wlan0 without using the vpn?

Thanks for your help and excuse my ignorance.