Run a LiveUSB of anything else. If it works, install that instead.
Stop listening to AI.
this post was submitted on 05 Jun 2025
53 points (90.8% liked)
Linux
55004 readers
904 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
Tell us more about what's happening, is the whole monitor turning green or just parts of it?
Does it stay green until you do something, or does it go away on its own?
Does it happen only with certain games or applications, or does it happen regardless of what's running?
And please for the love of fuck do not run any commands you don't personally understand, especially if it came from an "ai". Don't poison your brain (and the planet) with "ai" bullshit, please!
Solid green screen across the whole thing. The speaker starts humming the mouse and keyboard do not do anything and it does not resolve on its own (not within five minutes or so anyway). I have to do a hard reboot, then it works fine for the next 7-14 hours and then it happens again. Does not matter what I am doing. I have had it go green when I was reading plain text and not even touching the inputs.
Is the sound coming from the motherboard speaker or through a sound card or display?
From the MB to the external box speaker on the desk.
So I was wrong, sound was wired through the display via HDMI to the MB. I switched the speaker over to the MB directly and plugged the monitor into the GFX card instead of the MB, see if this changes anything.
You're going to get much better performance now too if the monitor was plugged into the motherboard before
Your monitor always needs to be plugged into the graphics card. If you plug it in via the motherboard, then your GPU is doing nothing, as it can't backfeed to that motherboard connector. CPUs often have their own graphics built-in, and that's what yours would have been using instead.
load more comments
(3 replies)
Solid green, have to hard reboot.
Which bazzite build did you install?
Are you able to switch to a secondary or tertiary TTY with Ctrl-Alt-F2 or Ctrl-Alt-F3?
I have not tried what you are asking in the second line because I have no clue what a secondary TTY even is, let alone the shortcuts or commands to do it. You were wondering if I tried this while the green screen is up or while everything is working normally?
While the green screen is up. I listed the shortcuts in the above comment. If there is an issue in the graphics pipeline you may be able to troubleshoot from a terminal only session using Ctrl+Alt+F2.
Login to that text only eesison with the username a password you used when creating the image.
Do you know which bazzite image you used? I think for your configuration it should have been bazzite-desktop. You might be having a green screen graphical issue if you accidentally downloaded a flashed bazzite-deck or bazzite-nvidia with an AMD graphics card.
It was desktop KDE I can not remember if it was the one with gaming mode or not. I think it was not but I could be misremembering. I used one of the first install and the other on the second.
Where you able to log in to a TTY session?
All bazzite images support 'gaming mode'. The deck images boot into it straight away which could cause problems with desktop hardware.
Consider joining the ublue discord group and troubleshooting with the creators of bazzite in the bazzte channel. They are very knowledgeable and if your issue is reproducible they would be able to implement a fix in future images.
I have a 9070xt and a 7600x. I was getting game crashes for a solid week. Although no green screens. Check which version of Mesa you are on, if it’s not the latest, do the upgrade from the terminal. I think you want 25.0.x. This solved my issues it’s been solid since. 9070XT support improved a lot over the last month. I don’t recall the commands to check Mesa version, etc. but that’s something AI should be able to give you. For whatever reason, updating via the GUI did not work for me.
I tried this one already, saw it when I was googling possible solutions. I am also starting to figure it is a hardware issue. I was very uncertain being new to Linux I wanted some software input but it is not looking good for an easy software fix.
Off the top of my head, I think sudo journalctl -xeb -1 should give you some useful error output for the previous boot (after rebooting from a failure).
There's a --list-boots option if you've rebooted a couple times since but aren't entirely sure.
OP, do this - it's the best way to figure out what's happening. It could be any number of issues, e.g. faulty RAM. With the output of the command above people can tell you what to test for.
load more comments
(8 replies)
I will give this a try next time it happens! Good looking out
Alright so it finally happened again, here is the output of that command:
sudo journalctl -xeb -1 [sudo] password for Necroscope: Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:38:47 bazzite kioworker[18070]: qt.gui.imageio.jpeg: Not a JPEG file: starts with 0x52 0x49 Jun 06 09:39:09 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:39:22 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object '/usr/lib/extest/libextest.so' from LD_PRELOAD canno> Jun 06 09:41:58 bazzite steam[3399]: ERROR: ld.so: object '/usr/lib/extest/libextest.so' from LD_PRELOAD canno> Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:45:56 bazzite flatpak[4252]: /usr/lib/x86_64-linux-gnu/GL/default/share/libdrm/amdgpu.ids: No such f> Jun 06 09:46:03 bazzite plasmashell[2860]: file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtra> lines 1091-1114/1114 (END)
I'm a bazzite user for a good year now, and also a first time Linux user. My hardware is amd as well, and for me the experience has been great, the most annoying issues having been compatibility workarounds for windows software. I would definitely recommend you to join their discord for support.
A green screen of death does not sound healthy, even crashes or hard reboots have never produced something similar for me. To rule out hardware issues, can you install a windows copy and/or create a USB with a live Linux OS such as mint to compare? (For reference, some Linux distros are able to run entirely off a USB stick, albeit much slower due to the obvious bottleneck).
If all this checks out I would suggest either reinstalling bazzite off a verified iso (there is a function before installing to make sure there are no errors) or using another distro.
I already tried redownloading and reinstalling Bazzite, yeah. Followed install instructions on Bazzites page pretty sure it had me verify the ISO
Your motherboard wouldn't happen to be an AsRock? There's been reports of ASRock mobos in particular causing problems with 9000 series AMD chips, especially the X3D. Mate of mine running windows has been having it crash especially when idle at desktop.
I'm not familiar with a green Linux equivalent to the BSOD. Is it completely green? In that case it may be a graphics problem...
It’s definitely an AMD graphics card crash.
Hrm, no MB is MSI. Graphics card is AsRock though, were there compatibility issues with them too? And yes, completely solid green screen. Speaker also humming and nothing to be done, a hard reboot is required
Like Hawke said it seems like the graphics card or driver crashing. Very hard to troubleshoot, especially when it's random. Bazzite probably already has very recent drivers, there's this post on the bad website listing some things to try. This stuff can lead to superstitious thinking, with people changing something, rebooting to have it work fine for a while then they post that change as if it fixed it.
God speed.
Thank you for this resource, now I have a couple more things to try before busting open the case and messing with hardware
What do you mean by "green screen of death"? Is there any text or something you can transcribe or screenshot for us?
No text or screen shot possible, screen is just solid green mouse and keyboard do nothing. Have to do a hard reboot.
Ah. If this is a new build that suggests a hardware issue. Can you try running with only one stick of RAM and/or xmp disabled to see if that fixes things?
load more comments
(1 replies)
Can you install slightly older drivers? Also maybe reseat the GPU (plug out and in)
I will try reseating it, this is the second set of drivers I have tried already though
view more: next ›