Bug 202040

Summary:	wrong desktop is displayed when switching between dual-head and single head
Product:	[Plasma] plasma4	Reporter:	Jan Hnatek <jan.hnatek>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aseigo
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Solaris
Latest Commit:		Version Fixed In:

Description Jan Hnatek 2009-07-30 23:45:02 UTC

Version:            (using KDE 4.2.98)
Compiler:          Sun Studio 12 
OS:                Solaris
Installed from:    Compiled From Sources

While using laptop, I'm often switching between single head and dual deal with KDE4 on OpenSolaris. This brought up an annoying problem, which may be a little complicated to explain.

With first invocation of KDE4 on single-head, I setup my /primary/ desktop, making changes to the panel and adding some desktop widgets.

When later connecting the laptop to docking station with external monitor, the configuration I have set up for the primary monitor now shows up on the external monitor. This is not the way I prefer it, since I use the internal display as primary even in dual-head, so I moved the panel and created an additional panel on the external display.

Using the single display, I now don't see the "primary" panel (with tray!) and I don't see a way to switch to it. This is mostly annoying, because creating additional instances of tray widget doesn't help (tray icons only appear in the first tray instance).

The "desktop activity" switcher widget used to help, but in latest versions this only switches desktop widgets, not panels, and even then the layout gets broken.

Comment 1 Aaron J. Seigo 2009-08-03 08:45:44 UTC

x.org (or kephal, but afaik it just follows x.org's lead in this) is switching the numbering of the screens, and plasma is simply following that. so first and foremost, this is an x.org sillyness.

there's another report asking for intelligent moving of panels from screens they aren't on to screens they are on. i can't find it right now, but it's there, somewhere, and this is a duplicate of it. :/

Comment 2 Aaron J. Seigo 2009-08-03 08:48:08 UTC


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

Comment 3 Jan Hnatek 2009-08-03 17:04:40 UTC

Thanks for the info. Did anyone try to raise this issue with X.org?