I decided to upgrade, and so far everything is working fine. I had some hiccups after the installation, but a reboot fixed all of them. Thanks for your input :)
I upgraded from 39 to 40 and I think the only issues I had were:
Background I was using got removed, got a better one anyway
A few gnome extensions stopped working and I had to update them or find an alternative
Had to re-create virtual disk mapped to real disk for booting windows installation in virtual box (there is a sonicwall VPN I have to use for work which only works on Windows)
I think that was it!
I have had some strange behaviour from Firefox saying it’s become unresponsive a few times and at the same time Thunderbird but that seems to have fixed itself now
Background I was using got removed, got a better one anyway
I had that happen a few times. This time I downloaded those backgrounds again (from gnome-backgrounds repository). Still, it’s pretty annoying to have this happen.
I upgraded just before the beta. Discovered a mutter crash, reported it, it was fixed in a day or so.
Had a sound issue: output device options only listed “Dummy Output” and nothing was listed for input devices. I eventually got my headset to be recognized again, but sadly couldn’t tell you what did it, since I tried so many things and I lack proper understanding of the Linux sound scene.
Just in case it’s useful to someone, here’s a collection of ideas I found while working through the issue:
Make sure wireplumber service is enabled and running OK
Plug in an HDMI device and reboot (some people said this permanently fixed a similar issue)
Backup, then delete $XDG_STATE_HOME/wireplumber and reboot
Check if you have installed the packages:
kernel-modules
alsa-sof-firmware
Note, however, that I really don’t understand what some of these do. You should be very wary of taking suggestions from people who don’t know what they’re talking about… unless you’re desperate enough and want your sound back, perhaps.
…Also, here’s a gentle reminder to test your sound device with other equipment and try different ports/adapters, if available. Wasn’t my case, but sometimes stuff simply breaks at inopportune times.
I'm fairly confident that it's a change in Flatpak itself rather than any one specific Flatpak, since all of my apps now use the same new screen sharing interface. Difference is that it actually works in those apps.
Were you using X11 before, by chance? IIRC Fedora 40 dropped X11, and only ships with Wayland by default. The fact that all of your apps are using the same screen sharing interface sounds like they’re using the screen share portal due to running under a Wayland session, which Discord doesn’t currently support currently.
For a while there was a workaround using a tool called XWaylandVideoBridge but even that stopped working for me.
I’ve heard that Vesktop supports screensharing under Wayland (and supposedly with sound support too), and it is available on Flathub - might be worth a try.
It was going perfectly smooth (Plasma 6 wayland, amdgpu drivers); though the past week or so I started getting random shell crashes. (It’s very impressive that Qt apps all come back unscathed – but I don’t use too many Qt apps.)
I tried Ubuntu recently out of curiously. It was buggy, slow and contained a lot of promotional material. For context, I hadn’t used it since a wipe my machine after they forced snap.
I think that the last time I used Ubuntu was like 10+ years ago. Too many awesome distros out there to remain on it, and even then, it was already broken.
I would 100% use that. Snap on Fedora is likely not sandboxed at all, as it relies on Apparmor, and also not really that well maintained as nobody cares.
Add comment