Bug 164727

Summary: Incorrect toolbox position on Xinerama
Product: [Unmaintained] plasma4 Reporter: lucas
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Default positions on a Xinerama setup

Description lucas 2008-06-23 10:40:19 UTC 
Version:            (using Devel)
Installed from:    Compiled sources

Attached is an image of what my desktop looks like on first load.

Two noticeable problems:
1) Two toolboxes are placed on top of each other on the left screen
2) The initial panel is added to secondary screen 1 (Left) and not the primary screen 0 (Right)
Comment 1 lucas 2008-06-23 10:40:59 UTC 
Created attachment 25534 [details]
Default positions on a Xinerama setup
Comment 2 Christophe Marin 2008-06-23 21:13:36 UTC 
For the 2nd point, have a look at bug 152917 which is probably still valid.
Comment 3 Aaron J. Seigo 2008-06-23 23:17:12 UTC 
SVN commit 823701 by aseigo:

default config: put the folderview on the same screen as the panel
CCBUG:164727


 M  +11 -7     desktopcorona.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=823701
Comment 4 lucas 2008-06-24 06:00:28 UTC 
Is the second point still a WONTFIX or is there going to be some work on it for 4.2?
Comment 5 Aaron J. Seigo 2008-06-24 23:29:29 UTC 
the second point is a WONTFIX because it's the advanced users who know which screen is 0, most others just assumes the left screen is "the screen" (i polled a number of people to figure this one out; and trust me, i don't like the results since it's less code to ask for screen 0 than find "the left" screen =/)

people who do know which screen is screen 0 can move the panel easily enough?
Comment 6 lucas 2008-07-18 16:23:02 UTC 
First point is a duplicate of bug 166770, second point is WONTFIX. Keeping the other one as it's more precise.

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