https://bugs.kde.org/show_bug.cgi?id=375507
--- Comment #2 from Thomas Weissel <xapi...@gmx.net> --- oke.. i think i can describe it a little bit better now: the moment you add a second display your plasma-org.kde.plasma.desktop-appletsrc gets a new entry > a new containment for the same activity id that looks 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 this containment has no "applets" and therefore is empty that is ok for the default setup where the new display extends the first one to the left or to the right (big desktop) BUT the moment you move the first display over the second (in systemsettings or with xrandr) in order to "clone" the displays (display the same content on both screens) it becomes a problem.. plasma seems to randomly chose which containment is shown on the screens!! new widgets are placed on the primary screen1 containment (and you can see that if you are lucky and this is the one containment that is currently displayed) but the moment you move them they switch to the secondary (empty) contaiment for screen2 (somehow behind the current containment) by pressing meta+tab you can switch between those two contaiments and change the "stack" order.. it seems that sometimes (in my case after every boot) the containment of screen2 acts as overlay over screen1 containment. IMHO they should always have the same content in "clone" mode and the user should never be able to see (or even switch) between those to.. OR.. the containment of any other screens that are not marked as primary should be rigorously ignored -- You are receiving this mail because: You are watching all bug changes.
