Bug 475831 - Desktop randomly black and empty after boot
Summary: Desktop randomly black and empty after boot
Status: RESOLVED DUPLICATE of bug 469192
Alias: None
Product: plasmashell
Classification: Plasma
Component: Containment (show other bugs)
Version: 5.27.6
Platform: Manjaro Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-19 16:12 UTC by php4fan
Modified: 2023-10-20 20:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description php4fan 2023-10-19 16:12:45 UTC
Half of the times I boot, my desktop is completely black, with no wallpaper and no icons.

I fix it with:
> sudo killall plasmashell
> kstart5 plasmashell

I've always had this issue ever since I've been using KDE, first with OpenSuse:
https://bugzilla.opensuse.org/show_bug.cgi?id=1184866
and then with Manjaro where I still have it

A comment from over a year ago in the OpenSUSE bug report says:
> Should be fixed in 5.25. Have you tried that?
> https://invent.kde.org/plasma/plasma-workspace/-/commit/41fb821545aac4df273fb45d0e4de9ab49143d9c

(although the link doesn't seem to have much to do with this issue from the very little I understand of it)

STEPS TO REPRODUCE
1. reboot
2. log in

OBSERVED RESULT
The desktop is completely black and empty

EXPECTED RESULT
The desktop should have the wallpaper image and  icons

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.10
Kernel Version: 6.1.53-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.3 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: LENOVO
Product Name: 81WE
System Version: IdeaPad 3 15IIL05
Comment 1 Nate Graham 2023-10-20 16:56:23 UTC
Do you have more than one screen? If you do, does the issue still reproduce with only one screen?
Comment 2 php4fan 2023-10-20 18:07:37 UTC
> Do you have more than one screen?

Yes, the laptop's built-in screen and one external screen. The external one is configured as the main and only screen, and the built-in one turned off.

When I boot, I do the following things in completely random order (I should not be expected to do them in any particular order):
- open the lid if I am turning on the computer, so that I can push the on/off button to turn it on (because sadly the on/off button is under the lid, a stupid design flaw that most laptops share). Or, if I am rebooting but software rebooting is not working, I open the lid so that I can access the on/off button in order to force a power off and then power on.
- close the lid while the system is booting
- connect the external screen if it wasn't already connected (usually it is, but if I need to open the laptop I also need to take it off of where it usually sits, and for that, sometimes I disconnect everything to take it off more easily, and then I reconnect everything.
- log in

Sometimes I don't need any of that (except the login), if I am just rebooting and rebooting from software works: in that case I just reboot, the lid remains closed all the time and the external screen remains connected all  the time. That is if I don't incur in bug 472581, in which case I need to open the lid so that the login screen shows up on the built-in screen.


> does the issue still reproduce with only one screen?

I don't know. Maybe not. I very rarely use the laptop without the external screen, and it requires too much time to test it on purpose.

I can say with certainty that sometimes It happened that I booted with the built-in screen only and didn't observe the issue, but (a) I am not completely sure that I never did observe the issue with the built-in screen only, (b) with the external screen I don't think it happens 100% of the times, (c) I pretty rarely reboot or turn off and on the computer at all (basically I only do when some bug forces me to, or when I travel).
Comment 3 Nate Graham 2023-10-20 20:15:59 UTC
Ok, thanks. That means this is Bug 469192, unfortunately. It hasn't been fixed yet.

*** This bug has been marked as a duplicate of bug 469192 ***