Below you will find pages that utilize the taxonomy term “Fedora-36”
Warning: Bug in latest Pipewire packages for Fedora 36
This morning I updated my Fedora 36 computer and suddenly it could no longer find any sound devices. Thanks to a Fedora user who commented on this reddit thread, I found that the solution was to downgrade my Pipewire packages. Specifically, at this point in time:
sudo dnf install pipewire-pulseaudio-0.3.49-1.fc36
A reboot didn’t make it work on its own. So I had to do the following afterwards:
systemctl --user restart pipewire-pulse.service
And I got my sound back. Huzzah!
Fedora 36, KDE Plasma 5, and Wayland Part 2
After using Plasma with KWayland for about a week, I had to go back to X11 because it’s not yet ready for me. There are 3 main issues I’m having:
- Occasionally, when I come back to my computer after locking the screen it would say that the screen locker had crashed. I would need to go to antoher TTY and type in a command to unlock it. After I did that, coming back to the TTY that has the GUI just remains black with a mouse cursor. So I would need to reboot the machine.
- Context menus would appear in the wrong place and I actually filed a bug about this one.
- I cannot drag and drop video files to upload to YouTube with Firefox. I have to click the button on YT and then navigate to the folder that has the video file. (Not sure if there are other things that can’t be dragged in - photo upload to Flickr, for example)
I’ll keep looking to see if they improve things. But for now I’m staying on X11.
Wayland on KDE on Fedora 36
I upgraded to Fedora 36 so I wanted to see all the latest updates to Wayland. I’d been reading about the updates in the KDE and wanted to see if it was more stable. I had to redo my latte dock profile. Other than that, SO FAR the only issues are that the scroll wheel on the mouse scrolls WAY too far on the page, making it almost useless. And Yakuake (the KDE drop down terminal) appears at the middle of the screen instead of at the top. I went to file a bug, but I saw a comment that this is fixed in the next version of Yakuake, so it seems I just need to wait for an update. Otherwise, so far it seems to be working OK.