UB
Universal Blue•4w ago
Mizuki

Black screen with cursor after typing password

Upgraded from 20250301 to 20250317 and that happened suddenly...I rolled back now but I want to know whether it's an upstream issue or if my installation is just screwy - how would I debug this?
4 Replies
Pandabrain
Pandabrain•4w ago
if you want to know if your installation is screwy, you can run sudo ostree fsck, which checks your system commits for integrity. (afaik it also checks those other than the current deployment) that aside: there was an update today, 20250325, maybe give that a try if that doesn't work, you could post your rpm-ostree status maybe there is something layered that is causing the problem?
Mizuki
MizukiOP•4w ago
fsck returned nothing wrong which is good but upgrading to 20250325 gave me this 
$ sudo bootc upgrade
layers already present: 47; layers needed: 25 (1.9 GB)
Fetched layers: 1.74 GiB in 72 minutes (419.83 KiB/s)                                                          ⠈ Deploying                                                                    
(bootc:25315): GLib-CRITICAL **: 21:18:22.500: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
⠤ Deploying                                                                                                    
(bootc:25315): GLib-CRITICAL **: 21:18:22.556: g_atomic_ref_count_dec: assertion 'old_value > 0' failed

  Deploying: done (77 seconds)                                                                                 Queued for next boot: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
  Version: 41.20250325
  Digest: sha256:a4a2c0458a6e01af8fbcfae5f6192d09c0429cacee50604489b1a7072101efa1
Total new layers: 72    Size: 5.1 GB
Removed layers:   71    Size: 4.7 GB
Added layers:     71    Size: 5.1 GB
$ sudo bootc upgrade
layers already present: 47; layers needed: 25 (1.9 GB)
Fetched layers: 1.74 GiB in 72 minutes (419.83 KiB/s)                                                          ⠈ Deploying                                                                    
(bootc:25315): GLib-CRITICAL **: 21:18:22.500: g_atomic_ref_count_dec: assertion 'old_value > 0' failed
⠤ Deploying                                                                                                    
(bootc:25315): GLib-CRITICAL **: 21:18:22.556: g_atomic_ref_count_dec: assertion 'old_value > 0' failed

  Deploying: done (77 seconds)                                                                                 Queued for next boot: ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
  Version: 41.20250325
  Digest: sha256:a4a2c0458a6e01af8fbcfae5f6192d09c0429cacee50604489b1a7072101efa1
Total new layers: 72    Size: 5.1 GB
Removed layers:   71    Size: 4.7 GB
Added layers:     71    Size: 5.1 GB
are those errors normal?
Kyle Gospo
Kyle Gospo•4w ago
No Try rpm-ostree instead of bootc
Mizuki
MizukiOP•4w ago
reboot and still same issue...oddly I got into another tty and ran ostree fsck there, no problem I should probably rollback, but how would I force-redownload the upgrade with rpm-ostree? before that if there's anything I can do in tty to try to debug it I'll be happy to try also, the KDE splashscreen did show up before the black screen cursor only I wonder if it's anything to do with plasma ah it's a segfault 
[   57.947568] wlp2s0: associated
[   57.977471] wlp2s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:57:03:f8:6a:25
[   58.687692] show_signal_msg: 1 callbacks suppressed
[   58.687699] QQmlThread[2527]: segfault at 1a ip 00007f920d77944e sp 00007f91c77fbb60 error 4 in libQt6Qml.so.6.8.2[37944e,7f920d401000+490000] likely on CPU 3 (core 1, socket 0)
[   58.687728] Code: a2 cd ff e9 f1 fc ff ff 48 8b 05 dd 95 2d 00 eb 88 be ff ff ff ff e9 16 fb ff ff be ff ff ff ff e9 21 fb ff ff e8 12 5f c9 ff <0f> b6 04 25 1a 00 00 00 0f 0b 0f 1f 84 00 00 00 00 00 f3 0f 1e fa
[   62.440169] QQmlThread[2798]: segfault at 1a ip 00007f58af37944e sp 00007f5879bf7b60 error 4 in libQt6Qml.so.6.8.2[37944e,7f58af001000+490000] likely on CPU 3 (core 1, socket 0)
[   62.440189] Code: a2 cd ff e9 f1 fc ff ff 48 8b 05 dd 95 2d 00 eb 88 be ff ff ff ff e9 16 fb ff ff be ff ff ff ff e9 21 fb ff ff e8 12 5f c9 ff <0f> b6 04 25 1a 00 00 00 0f 0b 0f 1f 84 00 00 00 00 00 f3 0f 1e fa
[   65.146523] QQmlThread[2850]: segfault at 1a ip 00007fd48bf7944e sp 00007fd455ff8b60 error 4 in libQt6Qml.so.6.8.2[37944e,7fd48bc01000+490000] likely on CPU 2 (core 0, socket 0)
[   65.146543] Code: a2 cd ff e9 f1 fc ff ff 48 8b 05 dd 95 2d 00 eb 88 be ff ff ff ff e9 16 fb ff ff be ff ff ff ff e9 21 fb ff ff e8 12 5f c9 ff <0f> b6 04 25 1a 00 00 00 0f 0b 0f 1f 84 00 00 00 00 00 f3 0f 1e fa
[  123.687636] pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:00:1c.4
[  123.687695] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  123.687718] pcieport 0000:00:1c.4:   device [8086:9d14] error status/mask=00000001/00002000
[  123.687744] pcieport 0000:00:1c.4:    [ 0] RxErr                  (First)
[   57.947568] wlp2s0: associated
[   57.977471] wlp2s0: Limiting TX power to 30 (30 - 0) dBm as advertised by fc:57:03:f8:6a:25
[   58.687692] show_signal_msg: 1 callbacks suppressed
[   58.687699] QQmlThread[2527]: segfault at 1a ip 00007f920d77944e sp 00007f91c77fbb60 error 4 in libQt6Qml.so.6.8.2[37944e,7f920d401000+490000] likely on CPU 3 (core 1, socket 0)
[   58.687728] Code: a2 cd ff e9 f1 fc ff ff 48 8b 05 dd 95 2d 00 eb 88 be ff ff ff ff e9 16 fb ff ff be ff ff ff ff e9 21 fb ff ff e8 12 5f c9 ff <0f> b6 04 25 1a 00 00 00 0f 0b 0f 1f 84 00 00 00 00 00 f3 0f 1e fa
[   62.440169] QQmlThread[2798]: segfault at 1a ip 00007f58af37944e sp 00007f5879bf7b60 error 4 in libQt6Qml.so.6.8.2[37944e,7f58af001000+490000] likely on CPU 3 (core 1, socket 0)
[   62.440189] Code: a2 cd ff e9 f1 fc ff ff 48 8b 05 dd 95 2d 00 eb 88 be ff ff ff ff e9 16 fb ff ff be ff ff ff ff e9 21 fb ff ff e8 12 5f c9 ff <0f> b6 04 25 1a 00 00 00 0f 0b 0f 1f 84 00 00 00 00 00 f3 0f 1e fa
[   65.146523] QQmlThread[2850]: segfault at 1a ip 00007fd48bf7944e sp 00007fd455ff8b60 error 4 in libQt6Qml.so.6.8.2[37944e,7fd48bc01000+490000] likely on CPU 2 (core 0, socket 0)
[   65.146543] Code: a2 cd ff e9 f1 fc ff ff 48 8b 05 dd 95 2d 00 eb 88 be ff ff ff ff e9 16 fb ff ff be ff ff ff ff e9 21 fb ff ff e8 12 5f c9 ff <0f> b6 04 25 1a 00 00 00 0f 0b 0f 1f 84 00 00 00 00 00 f3 0f 1e fa
[  123.687636] pcieport 0000:00:1c.4: AER: Correctable error message received from 0000:00:1c.4
[  123.687695] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
[  123.687718] pcieport 0000:00:1c.4:   device [8086:9d14] error status/mask=00000001/00002000
[  123.687744] pcieport 0000:00:1c.4:    [ 0] RxErr                  (First)
ostree fsck shows nothing so file corruption ruled out is it alright to bring this topic up again if there was no answer? alright I just upgraded on another system and as expected it works fine either my installation is definitely screwy or my hardware is hating bazzite all of a sudden but...

Did you find this page helpful?