Wayland to X11 ????
Is there a way to switch Bazzite from Wayland to X11 because of Nvidia without triggering a login loop?
48 Replies
No. It's deprecated in bazzite from my understanding. Though we may be able to help with the login loop with logs, etc. Since I haven't heard of nvidia causing login loops for most users.
I installed X11 and Plasma X11 appears on the login screen, but I can't log in from there because I keep getting back to the login screen
I'm not even sure how you installed it. You didn't layer it did you?
i be use that command sudo rpm-ostree install plasma-workspace-x11
I went through the whole process with Chat GPT because I couldn't find the error that caused the control bar to always disappear on Nvidia.
Please do not use GPT or LLMs whenever possible and ask here first. It will often get you into trouble and welcome issues.
As for the entire x11 session being layered you're unlikely to get support as it's not a supported configuration. In addition to being a layer of a major system package. Updates will likely not function among other issues.
The only possible recommendation I can give is unless you absolutely need x11 for some reason that you try a distro like Nobara which would offer you system level package management. Otherwise you can probably get help with whatever wayland issues you run into with nvidia if you were to unlayer and go back to a base state.
A third option, if you really want to use bazzite as a basis, is to spin your own custom iso up which includes the x11 things rather than layering, but note you're not likely to get bazzite support for that configuration but it would likely work.
There's guides mentioned in other chats about how to do such, but again no official support.
But I do recommend trying wayland first and asking for help with issues that come up as there aren't too many left for nvidia that I'm aware of, and there are other users here who can help with whatever might happen.
I always have the problem that the control bar disappears on YouTube videos and the desktop background turns black.
The whole background and the bar? When was the last update you had and when did the issue happen last? There was actually a chromium browser issue that was fixed last week.
That's why I already asked the question here, but apparently no one else has had this problem so far.
It COULD be linked to the issue solved last week so you may want to unlayer and make sure
ujust update runs without layered x11 and see if it works now. I don't know about the controller bar disappearing but for 2-3 weeks there was a regression where the media player taskbar applet would try to process bad album art and segfault loop plasma into crashing. (which would leave no bar or background only apps). That got fixed upstream and we got the fix last week. Chromium browsers were the main cause, but the primary issue was the media applet trying to process null images.
Chromium (vivaldi, edge, chrome, brave, etc) with youtube was just the most likely to give it a bad image.yea wayland is not what caused that original issue
So my steps would be
1) Unlayer the package
2) Be sure you're updated fully
3) If it happens again feel free to ask in the main #🎮bazzite channel and post the result of
ujust get-logs.
If you're not updated and the issue arises we can find both out real fast.
I can spot the media player bug from 4 miles away. Dvel can surely attest.
And if it so happens it's not the media player issue we can certainly comb the logs and figure out what it is since wayland is pretty stable with nvidia now.
Right now their biggest issue is that DX12 "fps tax"
And that's just nvidia in general not wayland.I'd recommend,
rpm-ostree reset to get rid of layered packages including the x11 stuff that's certain to cause issues. update to get the media player fix, restart, and start from there.To be fair too the media player issue looks COMPLETELY UNRELATED to what is causing it until you look at the logs so no wonder no one recognized it IF it was that. Most people assumed plasma was freaking out and just not working well but no it was one teeny tiny applet.
They REALLY need to sandbox those.
I'll run rp-ostree reset and then do an update to bring everything back up to date.
And lets have fingers crossed it was indeed that issue.
If not we'll work on it from there.
it sounds like it is that
Yeah the only outlier is the playback bar disappearing, but that could be a hiccup plasma going down caused since it did just loose the session.
Is there an error log that can be forwarded if something like this occurs so that the debuggers at Bazzite can perhaps patch something?
Yep!
ujust get-logs
in terminal will grab all the logs from current and previous boot
That'll also get the rpm-ostree status so we can check the version of bazzite you have
System Information:
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable-42.20250916.1
Digest: sha256:33b539973873e3ea41aa417c71121b12a7669c7249e02a77e5cb23fbf4229f66
Version: 42.20250916.1 (2025-09-16T17:32:52Z)
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable-42.20250916.1
Digest: sha256:33b539973873e3ea41aa417c71121b12a7669c7249e02a77e5cb23fbf4229f66
Version: 42.20250916.1 (2025-09-16T17:32:52Z)
LayeredPackages: cdemu-client cdemu-daemon ckb-next docker-compose
kde-cdemu-manager-kf6 plasma-workspace-x11 xorg-x11-server-Xorg
Logs This Boot: https://paste.centos.org/view/ef50b7ff
Logs Last Boot: https://paste.centos.org/view/20bbb376
yea its the mediacontroller issue
CAAAAALLLED IIIIT
God that issue is so annoying. You'd NEVER THINK it was the applet that offers a play/pause and album art that takes your WHOLE DESK DOWN
At least it was fixed real fast
The problem is bigger than expected.
It's happened again, and you can't even see it in the screenshot. .
You're still on the old update so you'll need to run
ujust update or System Upgrade in the main menu and be sure it grabs the update.
So go do that, reboot, and toss us "rpm-ostree status" so we can be sure you're on the new version.
Once we confirm you SHOULD be in the clear.
It's silly but your crash is actually because of a little thing in the system tray that shows next, previous, play/pause and album art. Videos from chromium browsers are giving it a bad screenshot, it tries to process it anyways, and crashes the whole desktop.I just updated, I've done more driving. This is the latest version available for me.
Hmn...
chincia@bazzite:~$ ujust update
── 17:51:48 - System update ────────────────────────────────────────────────────
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable-42.20250916.1
No upgrade available.
── 17:51:50 - Firmware upgrades ────────────────────────────────────────────────
Metadaten sind aktuell; benutze --force um sie erneut zu aktualisieren.
Geräte mit keinen verfügbaren Firmware-Aktualisierungen:
• ASUSTeK KEK Certificate
• ASUSTeK SW Key Certificate
• CT1000BX500SSD1
• CT480BX500SSD1
• CT480BX500SSD1
• KEK CA
• Master Certificate Authority
• Master Certificate Authority
• SDSSDH3512G
• System Firmware
• Windows Production PCA
System manufacturer System Product Name
....strange...0916 is like two updates out of date.
Why isn't it seeing it...
Well until we can solve your update issue the workaround is simple
Right click the arrow next to your clock to get to the system tray settings, and turn "Media player" to disabled.
That prevents it from trying to process bad album art.
Which means you won't crash while we try to figure out why your system won't update.
@dvelshnef Looks like their system isn't recognizing a newer upgrade. I think our solution may be to rebase to the same branch if it allows that.
I've given them the workaround for now
Operating System: Bazzite 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.16.4-108.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060
Why doesn't it recognize the update to 6.16.4-114.bazzite?
That's what we're wondering. Since the issue is fixed in Plasma version 6.4.5
My GUESS is it might have to do with the layering and how it checks for updates so its not checking because of how unlayering works.
That's just a blind guess though
An option is to use
bruh to rebase to the same version of bazzite and if it lets you do that it SHOULD grab latest.
a sorta "Shut up and do it"thats odd, if you just did the rpm-ostree reset, maybe try rebooting if you haven't already, then updating?
I did a hard reset after the rest and then ran the update, but I still don't have the new version.
My best guess is it's not checking because it believes it is latest. That's why if a reboot doesn't help we may need to just rebase to the current image and see if that'll do it.
But I'm not sure if Bruh will be happy with a rebase to the same version or if we can force it to do it anyways.
If it's the former it may start seeing updates when yet another update comes out but that might be a week or two as we're close to fedora's new release.
So...I mean lets try to rebase to the same image. Worse that happens is we learn how it behaves in this case.
With bash, he can see the current version.
Still at least we found your issue. And hopefully you applied that fix I gave you. Which leaves us just the update issue and forcing it to check.
-# I'm going to throttle that media applet, though
I'll try to load the update via bash - rebase.
bruh is another tool for it. But yeah try to rebase to the version you already have. Lets see if we can force the update.
Pulling manifest: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable-42.20251002
Importing: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable-42.20251002 (digest: sha256:a87d7408b5f1b57676288ac8c3402daab13f25861562477e1f8570893f2e66d6)
ostree chunk layers already present: 30
ostree chunk layers needed: 42 (2,7 GB)
[0/42] Fetching ostree chunk 52aa306bcfee2afc701 (23,5 MB)... done
[1/42] Fetching ostree chunk 2da504ca32fac29f421 (221,7 MB)... done
[2/42] Fetching ostree chunk 246e15301a09f149cba (14,9 MB)... done
[3/42] Fetching ostree chunk cd3f0eb6895c6654831 (245,2 MB)... done
[4/42] Fetching ostree chunk 1947caddffeb6314ac4 (46,3 MB)... done
[5/42] Fetching ostree chunk 1e1454e14fd9b9d3b25 (230,8 MB)... done
[6/42] Fetching ostree chunk f182751785fa954afa3 (26,7 MB)... done
[7/42] Fetching ostree chunk 4de6c4e987ec9393e70 (59,3 MB)... done
[8/42] Fetching ostree chunk 6b987a5f60dd6708d47 (98,3 MB)... done
[9/42] Fetching ostree chunk 96b700bfc4e883403d0 (111,2 MB)... done
[10/42] Fetching ostree chunk 47cf5cc727a94a5ffd4 (30,4 MB)... done
[11/42] Fetching ostree chunk e7416b713fa47f3b795 (14,3 MB)... done
[12/42] Fetching ostree chunk 2bd3fd55ff318343fc8 (20,3 MB)... done
[13/42] Fetching ostree chunk 6024d36c627bfc02323 (49,4 MB)... done
[14/42] Fetching ostree chunk c745ceb5f131ce4ad25 (86,3 MB)... done
[15/42] Fetching ostree chunk 95e42edeba9329497f0 (94,1 MB)... done
[16/42] Fetching ostree chunk 40e950e9464905ef26d (14,7 MB)... done
[17/42] Fetching ostree chunk 8228772baa37224be5f (34,3 MB)... done
[18/42] Fetching ostree chunk 282a44d7187b15b95af (37,7 MB)... done
HUZZAH
looks good
We're getting those beautiful chunks
And once you confirm you have plasma 6.4.5 the media player is safe to turn back on. By the way.
What browser do you use?
I need to confirm something to myself
chrome
I KNEW IT
Operating System: Bazzite 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.4-114.bazzite.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 32 GiB of RAM (31.2 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060
Okay that solves that. Chromium browsers are almost ALWAYS the cause
YOU GOT THE FIX \o/
Go into it for one issue and of COURSE it's my old friend media applet segfault
Soon as I touch an issue like this it's got a 50% chance it's that bloody thing
For users, that's not exactly nice either, because it just annoys you.
No