# Blank screen after logging in on Bazzite **URL:** \ **Category:** Bazzite\ **Created:** [April 6, 2024, 10:58pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020 "2024-04-06T22:58:39Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [April 6, 2024, 10:58pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/1 "2024-04-06T22:58:39Z")
I’ve been using Bazzite on my HP Elitebook 845 G9 for the past couple of weeks just fine. But just recently, I got a blank/black screen after rebooting and entering my password on the login screen. What I’ve tried: - Opening a terminal with CTRL-Alt-F2. This works, and brings up a login prompt. - Updating with `ujust upgrade`. This worked, and brought me up to the 040624 image (from the 032924 image). Maybe I should have downgraded … Because these are my two available images. - Restarting sddm with `sudo systemctl restart sddm`. This brought me back to the login screen, and when I entered my password, it brought me back to a terminal, but which is frozen and hard-locked. No CTRL-Alt-Fx combination does anything. Anything I could try? ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [April 7, 2024, 12:26am UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/2 "2024-04-07T00:26:36Z")
> [@chicagonyc](#): > > HP Elitebook 845 G9 Do you use Steam Gaming Mode? ---
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [April 7, 2024, 4:51am UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/3 "2024-04-07T04:51:01Z")
No, I just use it in normal desktop mode. ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [April 7, 2024, 4:59am UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/4 "2024-04-07T04:59:46Z")
Using the same method as before to enter commands (the TTY), rebase to an earlier build for a while, maybe wait until Fedora 40 builds are out this month before going back. I am not sure what’s going on but if this earlier build actually works for you, I would consider making an issue about it in [Github issue tracker](https://github.com/ublue-os/bazzite/issues). Anyways, try rebasing to the March 22, 2024 build in the TTY. **KDE** : ```command rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:39-20240322 ``` **GNOME** : ```command rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:39-20240322 ``` In order to get back to the `:stable` channel and receive updates past this build, then you can have to enter in a host terminal: ```command rpm-ostree rebase ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable ``` or `bazzite-gnome` if you’re on GNOME. More information can be found in this documentation: [https://universal-blue.discourse.group/docs?topic=36](https://universal-blue.discourse.group/docs?topic=36) ---
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [April 8, 2024, 4:57am UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/5 "2024-04-08T04:57:37Z")
Thank you for the reply. I’m running KDE and ran your first command, then rebooted. Unfortunately, I get the same symptoms: blank screen after successfully entering my password on the login screen. CTRL-ALT-F2 works to bring up a terminal, then I do see the 2024-0322 image is loaded. But still, a blank screen. Wow, this is pretty bad. ---
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [April 8, 2024, 2:14pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/6 "2024-04-08T14:14:33Z")
One update – switching to X11 allows me to go to the desktop on the 0322 image. But … I think I want to be running Wayland, right? ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [April 8, 2024, 5:41pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/7 "2024-04-08T17:41:38Z")
It’s better and newer than X11. However, whatever works. What GPU do you have? ---
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [April 8, 2024, 5:56pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/8 "2024-04-08T17:56:10Z")
This is a Ryzen 6800U based laptop, so there’s a AMD 680M IGPU. The odd thing is that Wayland worked fine up until a few days ago when the black/blank screen appeared! ---
**Author:** ![nicknamenamenick](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/nicknamenamenick/32/4512_2.png) [@nicknamenamenick](https://universal-blue.discourse.group/u/nicknamenamenick)\ **Post date:** [April 8, 2024, 6:09pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/9 "2024-04-08T18:09:08Z")
Yeah this is bizarre especially since AMD and Intel GPUs usually work well with Wayland. My desktop and laptop running Bazzite do not have this issue also both are using AMD GPUs. Incredibly bizarre that even rebasing to an older image did this. Have you messed with `/etc` lately or layered any packages? ---
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [April 8, 2024, 6:25pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/10 "2024-04-08T18:25:25Z")
I added some NFS mounts to /etc/fstab, but that’s it. Through ujust, I had coolercontrol and liquidctl layered. By myself, I only layered google-chrome-stable, the reasoning for which I described [here](https://universal-blue.discourse.group/t/browser-via-rpm-ostree/929). But, Wayland worked fine after I did the latter, up until a few days ago. ---
**Author:** ![baltimoresports](https://yyz2.discourse-cdn.com/free1/user_avatar/universal-blue.discourse.group/baltimoresports/32/1193_2.png) [@baltimoresports](https://universal-blue.discourse.group/u/baltimoresports)\ **Post date:** [April 12, 2024, 11:40pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/11 "2024-04-12T23:40:48Z")
Same issue. Minisforum UM690. If I CTRL+ALT+F2 and shutdown I can sometimes get the SteamdeckUI/Gamescope-session to load. Helps if I unplug all the usb devices. ---
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [April 13, 2024, 5:56am UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/12 "2024-04-13T05:56:07Z")
> [@baltimoresports](#): > > Minisforum UM690 Interesting … also a Ryzen chipset with an iGPU. Did X11 fix the problem? ---
**Author:** ![zeroballoons](https://avatars.discourse-cdn.com/v4/letter/z/ed655f/32.png) [@zeroballoons](https://universal-blue.discourse.group/u/zeroballoons)\ **Post date:** [May 5, 2024, 6:13pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/13 "2024-05-05T18:13:49Z")
Hey all, Check my tutorial for how I fixed this on Aurora and see if it is relevant. [Fixing Blank/Black Screen After Login When Changing Login Shell to Fish](https://universal-blue.discourse.group/t/fixing-blank-black-screen-after-login-when-changing-login-shell-to-fish/1505) ---
**Author:** ![californiaroll](https://avatars.discourse-cdn.com/v4/letter/c/edb3f5/32.png) [@californiaroll](https://universal-blue.discourse.group/u/californiaroll)\ **Post date:** [July 2, 2024, 2:25pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/14 "2024-07-02T14:25:29Z")
I seem to be seeing this issue too (and more!) on one of my kid’s laptops. So far, what I know: - AMD Ryzen / iGPU, an old Acer Inspire 3 - Twas working fine on 062424 (1) for sure until today. Maybe 063024 (0), but, not certain of that first hand. - Secure boot enrolled and on. - Today, he says he was in the OS and shut the lid and it went to sleep mode as far as he knows – when reopened lid, twas in Grub. - I tried selected both 063024 or 062424 there. BOTH gave “bad shim signature” error messages and refused to load. 🤔 - Searching led me to suspect interplay with Secure Boot. So I disabled Secure Boot in BIOS. So secure boot now OFF. - Now both 063024 and 062424 load to SDDM. I get video and can login. BUT. - Blank screen after login. ---
**Author:** ![chicagonyc](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@chicagonyc](https://universal-blue.discourse.group/u/chicagonyc)\ **Post date:** [August 29, 2024, 12:18pm UTC](https://universal-blue.discourse.group/t/blank-screen-after-logging-in-on-bazzite/1020/15 "2024-08-29T12:18:36Z")
After experiencing mega problems with configuring the fish shell as my main shell, I went back to bash, and only set fish as the default in Ptyxis under profile.