I have a strange issue since the 7.2 kernel upgrade - my laptop screen is blank after I log in. The screen is still on, but nothing is shown - its just blank/black. The mouse can move on the screen, but its not shown either.
Going to the KDE Display Settings and changing anything brings the display back to life. Doesn’t seem to matter much what I change - resolution and refresh rate both fix it for sure.
The external monitor works fine
- Operating System: openSUSE Tumbleweed 20260830
- KDE Plasma Version: 6.7.4
- KDE Frameworks Version: 6.29.0
- Qt Version: 6.11.2
- Kernel Version: 7.2.2-1-default (64-bit)
- Graphics Platform: Wayland
- Processors: 8 × Intel® Core™ Ultra 7 258V
- Memory: 32 GB of RAM (30.8 GB usable)
- Graphics Processor: Intel® Graphics
- Manufacturer: LENOVO
- Product Name: 21NSCTO1WW
- System Version: ThinkPad X1 Carbon Gen 13
1 Like
same here. hope it gets fixed.
though I want to know wdym with your external monitor work fine?
I mean… I have a external monitor (Dell U2414H) connected via HDMI. It works as expected. I wonder if this is due to the large difference in screen resolution? The laptop is 2880 x 1800, the external screen 1920x1080.
I’ve noticed some more details:
- Both screens are enabled and functional on the login screen. That still uses X IIRC?
- When I log in, the laptop screen shows corrupted data briefly before going blank
I did a bit of digging and found this in the system journal:
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSink/sbc
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSource/sbc
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSource/faststream
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSource/faststream_duplex
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSink/opus_05
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSource/opus_05
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Sep 05 10:19:15 martin-work bluetoothd[1424]: Endpoint registered: sender=:1.41 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Sep 05 10:19:15 martin-work systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: Socket to launch DrKonqi for a systemd-coredump crash skipped, unmet condition check ConditionUser=!@system
Sep 05 10:19:15 martin-work systemd[2126]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Wil>
Sep 05 10:19:15 martin-work systemd[2610]: Starting Accessibility services bus...
Sep 05 10:19:15 martin-work systemd[2610]: Started Accessibility services bus.
Sep 05 10:19:15 martin-work dbus-broker-launch[3042]: Ready
It seems that Dr.Konqi was trying to report something that crashed, but couldn’t. Is there a way I can get to see that log?