Black screen with blinking white bar in top left after fresh install
I'm trying to install bazzite-nvidia-stable on an old dell optiplex with an i7-980 and a 750ti and 8gb of ram (on a fresh samsung 1tb ssd). The install seemed fine (I used fedora media writer to make my bootable usb and confirmed the sha256 checksum of the iso I downloaded from bazzite's site). On first boot it gave the kargs message and then rebooted. On the next boot (and all following) it shows the bazzite logo with the white loading circle and then just goes to a black screen with a white blinking cursor in the top left.
I did some searching for past threads and some suggested going back to the 2024-9-30 build which I'm going to try. But before I do that I was wondering how to try and diagnose the issue better before just running an older version of the installer. It seems similar issues but not exactly the same has been posted here (at least from my quick searches).
EDIT: Forgot to add that I let it sit on that black screen for 30mins just to make sure it wasn't doing anything and I was using the kde version
Solution:Jump to solution
Since we have no internet i just did the workaround
sudo rpm-ostree override remove kf6-kimageformats and rebooted with no issues. Got the regular login and can see the desktop as expected. Marking this message as solution, please refer to the github issues renner linked above (once those fixes make it into stable I'll just reset that override and upgrade)10 Replies
Are you trying to run the Bazzite-deck-nvidia image? If so, the 750ti isn't a supported GPU for game mode. Have you tried the bazzite-nvidia image?
Oh nevermind you mentioned bazzite-nvidia-stable
Yeah try a rebase to an older version and see if that helps or try a bazzite-gnome
2024-09-30 is a bit far back though
The blinking cursor usually means that there is a GPU problem of sorts
Actually, I've seen it before that you get the blinking cursor because it's failing to load sddm. When you get the blinking cursor does pressing CTRL+ALT+F2 give you a terminal?
If so, login to the terminal, note that nothing will show up while you type your password (no feedback at all) then once you are logged into the terminal try start plasma with
startplasma-wayland and see if you can get into the desktopokay I will try that, the pc is at a friends house, gonna drive over in an hour or so and give an update then
good luck
Okay update, that kind of worked. I saw the task bar for a second and then 3 different plasmashell crash handler pop ups occur
This pc has no internet currently so i cant send auto reports, i can save them to a file and get them on a flash drive currently
I can ctrl+alt+t to open a new konsole/terminal window whenever I want which is nice
These crash logs don't mean much to me if I'm being honest @wolfyreload I assume not having an internet connection is okay. My friend was planning on getting a usb wifi adaptor soon but can run and get one if some stuff just needs to download an update
launching dolphin from terminal causes some kioworker crashes and the terminal mentions "Could not load default global viewproperties"
I can use dolphin to navigate to the crash reports and open them in Kate no problem, it just seems like some weird issue with plasma
sounds like:
https://github.com/ublue-os/aurora/issues/8
GitHub
No graphical session after update to 41.20241117.3 on Aurora. · Iss...
Describe the bug The system updated from 41.20241112.1 to 41.20241117.3 and on the next boot it showed the arrow cursor for a little while and then a blank screen. It didn't even show the login...
possible cause:
https://github.com/ublue-os/main/issues/695
GitHub
libheif and heif-pixbuf-loader from negativo causes sddm/plasma/qt ...
Context: ublue-os/aurora#8 ublue-os/aurora#8 (comment) Responsible commit? negativo17/libheif@4a4cbd9 affected hardware: possibly everything that uses i915? Pentium B940 SandyBridge = Gen6 Graphics...
That was the issue, ty so much renner
Solution
Since we have no internet i just did the workaround
sudo rpm-ostree override remove kf6-kimageformats and rebooted with no issues. Got the regular login and can see the desktop as expected. Marking this message as solution, please refer to the github issues renner linked above (once those fixes make it into stable I'll just reset that override and upgrade)