Bug 366207 - no desktop background, no contextmenu on desktop after login or when screens wakeup
Summary: no desktop background, no contextmenu on desktop after login or when screens ...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-multiscreen (show other bugs)
Version: 5.8.0
Platform: Neon Linux
: NOR grave
Target Milestone: 1.0
Assignee: Aleix Pol
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-28 14:05 UTC by Thomas Weissel
Modified: 2016-12-07 17:48 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.8.4


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Weissel 2016-07-28 14:05:57 UTC
plasma version 5.7.2
frameworks version 5.24.0
qt version 5.7.0
kernel 4.4.0-21
cpu intel core i7-4790T  - intel hd graphics 

i've got two identical "benq" screens connected to my workstation.
almost everytime those screens go to sleep (and sometimes on first login) plasma gets confused.

if i wake up the screens by moving the mouse one of them stays black..  the left screen contains the plasma panel containment which surprisingly stays visible even if the plasma desktop containment seems to be gone..

plasma continues to run and i can continue to work without problems but the desktop containment is somehow broken.. the background on one of the screens is gone and it doesn't show a context menu on rightclick anymore.. 
the other monitor displays a proper plasma desktop containment that works properly.

i've seen a similar behaviour on single screen setups..  and i also tried plasma 5.7.99

Reproducible: Sometimes

Steps to Reproduce:
1.wait for the screen to go to sleep (powermanagment)
2.wake up the screen(s)


Actual Results:  
black desktop (no background)
no contextmenu on desktop containment

Expected Results:  
my desktop !

this is not distro specific .. i've tried several kde distributions including kde neon 
(i also tried the developer unstable version)

Qt 5.6.1 obviously did NOT fix that problem!

if i run..
kquitapp5 plasmashell ; /usr/bin/plasmashell --shut-up
i get a working plasma desktop...
this is critical... i can NOT install plasma on my clients computers anymore which is very bad !
Comment 1 Thomas Weissel 2016-07-31 19:11:14 UTC
i just discovered that this bug also works in reverse ^^   

if i just ignore the black desktop on one of my screens (that means i continue working without restarting plasmashell) the next time the screens go to sleep and i wake them up again desktop backgrounds are and contextmenu are back....

i wasn't sure at first but i've reproduced this 4 times now.....
Comment 2 Oleg Sidorkin 2016-08-10 23:37:35 UTC
+1, Kubuntu 16.04 with kubuntu-backports repository.
Comment 3 sk-os 2016-08-17 17:11:12 UTC
+1,  ArchLinux with plasmashell 5.7.3

workaround1: pkill plasmashell; plasmashell &
workaround2: disable/enable primary/secondary monitor and change primary monitor to each other and back again

I recognized the problem at random logins. my secondary desktop moves to the primary monitor,  secondary desktop stays empty/black - but is usable, you can move programs onto it. Desktop of primary monitor is gone.
Comment 4 Thomas Weissel 2016-10-05 17:35:36 UTC
re-tested with kde neon on kubuntu
plasma: 5.8.0
Qt:  5.7.0

the onlything new is that sometimes only the wallpaper is gone but the contextmenu is still there, adding a widget gets everything back to normal..

also when one of the screens went black the last time plasma seemed to restart automatically after 2 or 3 seconds.. 

what can i do to narrow down the reason for this ? i want this bug gone!
Comment 5 Thomas Weissel 2016-10-06 06:14:55 UTC
yet another interesting observation:   

i added clock widgets to the screens...   one of the screens went dark after sleep  (no background - no rightclick contextmenu) but the widget remained visible (it still displayed the time when the screens went to sleep)
Comment 6 Thomas Weissel 2016-10-09 11:14:51 UTC
i dare to say that this problem is fixed now by changing my own hardware setup.

what i had: 

1x hdmi out (connected to the hdmi port of my first display)
1x dvi out (connected to the hdmi port of my second dislay <dvi to hdmi cable>)

what i have now:

1x hdmi out (conneted to the dvi port of my first display)
1x dvi out   (connected to the dvi port of my second dislay)


my screens went to sleep at least 5 times now without any problems...

attention!! this bug is not fixed !  it just seems to work for my current (new) setup now.
Comment 7 Jaroslav Reznik 2016-10-18 08:48:09 UTC
I can see this on KF5 5.27/Plasma 5.8.1 - it does not happen as often as in the past but the bug is still there. Restarting Plasma usually helps. I can provide config files if needed but it's difficult to explain the behavior aka what I did. It's just not there.
Comment 8 sk-os 2016-11-04 17:41:01 UTC
There's still something strange going on in 5.8.2.
After changing my screen setup - unplugged external monitor or switched over to another hdmi port - I get a default background at the next boot on my secondary monitor. So the wallpaper and the widgets are reset. 
primary monitor stays normal.
Comment 9 Kyle 2016-11-10 04:45:59 UTC
I have a laptop and external screen, My laptop screen has my taskbar and both desktops have the same background. When my computer wakes from sleep, sometimes the laptop screen is black and I am not able to right click and assign a background again. Restart fixes the issue

Plasma 5.8.2 Debian Stretch
Comment 10 Thomas Weissel 2016-11-10 07:55:36 UTC
i can confirm that in 

plasma 2.8.90
frameworks 2.28.0
Qt 5.7.0

this bug is still unresolved. it just changes a little bit...

kquitapp5 plasmashell ; /usr/bin/plasmashell --shut-up

brings back my messed up icons in the panel (different bug) but this time screen number 2 stays black..

so it keeps the problem alive now even if i kill it !

btw. why is this bug still "unconfirmed"? 
is there no developer with a multiscreen setup experiencing the same thing?
Comment 11 Thomas Weissel 2016-11-23 18:50:52 UTC
ok.. it seems this bug is fixed in 5.8.4
Comment 12 sk-os 2016-12-04 15:16:51 UTC
I can confirm that, no more issues in 5.8.4