https://bugs.kde.org/show_bug.cgi?id=375507

            Bug ID: 375507
           Summary: blank plasmadesktop containment is created when
                    cloning display
           Product: plasmashell
           Version: 5.8.95
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Desktop Containment
          Assignee: se...@kde.org
          Reporter: xapi...@gmx.net
  Target Milestone: 1.0

steps to reproduce:

# configure desktop and fill it with widgets
# attach projector
# clone display to projector
# restart xserver

the file: plasma-org.kde.plasma.desktop-appletsrc gets a new entry like this:

[Containments][73]
activityId=95dec76c-3e71-47af-a064-cbd5a50957de
formfactor=0
immutability=1
lastScreen=2
location=0
plugin=org.kde.desktopcontainment
wallpaperplugin=org.kde.image

>> all desktop widgets are gone

the old entry :

[Containments][1]
activityId=95dec76c-3e71-47af-a064-cbd5a50957de
formfactor=0
immutability=1
lastScreen=0
location=0
plugin=org.kde.desktopcontainment
wallpaperplugin=org.kde.image

and all it's associated [Applets] are still there but not shown.


pressing "meta+tab" or accessing the activity switcher (or pressing "alt+tab"
without running applications) immediately switches back to containment #1
instead of containment #73 and all widgets are visible again.


i switched the lastScreen values so that containment #73 has lastScreen=0 >
restarted the desktop > everything worked.. all my widgets are here (i'm still
able to switch to the empty containment from the parallel universe with
meta+tab)

the problem is that the moment i disconnect the projector and restart the
desktop the containment with lastScreen=0 is shown (ergo the empty one) 

it seems i can't have both..



there is no other desktop configured and no other activity - plasmashell is
doing this automatically but this new "hidden" containment does not show up
anywhere except in the config file..


reproduceable: ALWAYS!

here is a short video of this strange behaviour:
https://www.youtube.com/watch?v=95z7yuZQLCo


IMHO creating another desktop containment entry in the config file is fine for
big-desktop but clone-desktop should not do this - it should just clone the
current one!

is there a quick fix for that?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to