Bug 180437 - cannot set screen position via "Configure Display"
Summary: cannot set screen position via "Configure Display"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
: 181679 181779 185968 191880 195649 197327 201866 208518 239876 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-12 10:57 UTC by Daniel Thaler
Modified: 2015-01-22 17:05 UTC (History)
27 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of KDE screen settings showing 2 screens being managed (62.53 KB, image/png)
2010-08-16 16:47 UTC, putt1ck
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Thaler 2009-01-12 10:57:02 UTC
Version:           KDE 4.1.96 (4.2 rc1) (using Devel)
OS:                Linux
Installed from:    Compiled sources

I'm running Arch Linux with the current KDE 4.1.96 packages.

In the "Configure Display" window I have 3 entries:
First is "VGA" which is greyed out because nothing is connected to VGA
Second is LVDS, the notebook's built-in display
Third is TMDS-1, an external screen connected via DVI.

Only the VGA entry has buttons to set the position, which are of course disabled.
For the 2 connected displays I can only set the position by running xrandr on the commandline.
Comment 1 Rémi 2009-01-20 19:37:43 UTC
I have a similar problem with an intel card, when my VGA screen is connected to my laptop i can't configure dual screen properly.
I can set orientation of each screen but I am unable to move the boxes to place my screens. I can't drag and drop it like windows or nvidia tools do.
The boxes are superimposed.
Comment 2 Orion Poplawski 2009-01-24 00:47:12 UTC
Me to.  Fedora 10 with kde-testing 4.1.96 and ATI Radeon.  I can set position fine with xrandr.
Comment 3 Orion Poplawski 2009-01-26 23:15:26 UTC
Still present with 4.2.0 from kde-testing repo.
Comment 4 Christoph Feck 2009-05-10 00:13:00 UTC
*** Bug 191880 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2009-05-10 00:14:01 UTC
*** Bug 185968 has been marked as a duplicate of this bug. ***
Comment 6 Joe Mulloy 2009-05-10 02:25:40 UTC
Found this in kdebase-workspace-4.2.2/kcontrol/randr/outputconfig.cpp starting at line 258.

	// FIXME: RandRScreen::applyProposed() has a bit of code for positioning
	// outputs, but it's commented out and might not work as is. Until someone
	// gets this to work, it's probably better not to show these controls.
	positionLabel->setVisible(true);
	positionCombo->setVisible(true);
	positionOutputCombo->setVisible(true);

Looks like this was intentionally turned off because the code behind it isn't fully implemented.

Looks like it still hasn't been fixed in the latest code in SVN. It would be really nice to have this for 4.3.

http://websvn.kde.org/trunk/KDE/kdebase/workspace/kcontrol/randr/outputconfig.cpp?view=markup
Comment 7 Christoph Feck 2009-06-30 09:23:23 UTC
*** Bug 195649 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2009-06-30 09:24:55 UTC
*** Bug 197327 has been marked as a duplicate of this bug. ***
Comment 9 Joe Mulloy 2009-06-30 17:36:47 UTC
Seems we have a lot of people looking for this to be fixed. What's the status of this bug, has any work been done on it yet?
Comment 10 Khashayar 2009-07-01 12:21:46 UTC
*** This bug has been confirmed by popular vote. ***
Comment 11 Christoph Feck 2009-07-30 16:24:24 UTC
*** Bug 201866 has been marked as a duplicate of this bug. ***
Comment 12 putt1ck 2009-07-30 16:39:11 UTC
Awesome. So my reported bug is a duplicate although affects a different version (KDE4.3RC3) and has some specific additional observations and observed symptoms beyond the placement issue. 

Ok. Seems odd to my understanding of bug identification and tracking. Never mind.

So we need to add to this bug that said module also *resets* dual display that has been manually configured (suggesting it is pre-confed as "Unify Outputs") and refuses to set higher monitor resolutions where disparate monitors are used (possibly the same reason, although if you use krandrtray and turn off "Unify Outputs" you still can't do it).

Any progress on this bug? Anything I can do to help?

Those struggling to get dualhead working might want to go over here:

http://forum.kde.org/viewtopic.php?f=66&t=62111&start=0#p84062 (linked from my original bug, has step by step instructions on getting it to work with ATI card on radeon drivers).
Comment 13 Toni Helenius 2009-08-24 14:52:21 UTC
I can confirm this bug. Affects Kubuntu Karmic with KDE 4.3. I'm using Nouveau with my Geforce 9800GTX+. Nouveau is capable of XRANDR 1.2.
Comment 14 Niek Beernink 2009-09-15 11:54:32 UTC
Another confirm, seems I'll be stuck with one monitor at work for the time being. Xrandr can be used as a temporary solution but when I log out and in again I'd have to reset all the panels and taskbars for some reason. So I'll just wait for this bug to be fixed.

2x Prolite E431S
Nvidia 9500GT (tried both open source drivers and proprietary ones.)
KDE 4.3 on Fedora 11
Comment 15 Tobias Hain 2009-10-08 16:26:20 UTC
> Looks like it still hasn't been fixed in the latest code in SVN. It would be
> really nice to have this for 4.3.

Maybe that's because:
> I'm going to hide the positioning controls for the time being - if someone
> wants to take a stab at making this work: it's all yours.
https://bugs.kde.org/show_bug.cgi?id=172315#c4
Comment 16 Tobias Hain 2009-10-11 13:42:14 UTC
I see a fix is developed over at OpenSuse (comment #4 and #14):
https://bugzilla.novell.com/show_bug.cgi?id=468931

Would somebody pull this one in? It annoys Kubuntu Users as well:
https://bugs.launchpad.net/ubuntu/+source/kdebase-workspace/+bug/403610
Comment 17 fred 2009-10-30 07:58:47 UTC
I would like to point out that:

------- Comment #12 From putt1ck 2009-07-30 16:39:11 (-) 

affects me in exactly the same manner; running KDE 4.3.2 on top of Arch Linux.  I've intel GMA 950 graphics, Xorg-server 1.6.3.901.  Despite the fact that I've now written bash scripts to trigger the monitor configurations I commonly use, and now know how to use xrandr like the back of my hand, I think it would be a good idea to fix this.
Comment 18 dschaefer79 2009-11-25 10:19:08 UTC
*** Bug 208518 has been marked as a duplicate of this bug. ***
Comment 19 David Batson 2009-12-02 02:40:57 UTC
Same problem in Fedora 12 KDE and Mandriva 2010 KDE.  I had to add a section to xorg.conf and use the xrandr commands to resolve this.  Details in the following post:
http://forums.fedoraforum.org/showpost.php?p=1299661&postcount=4

KDE should get on the stick and fix this problem.  AND IT IS A PROBLEM.
This is not a problem at all in Fedora 12 GNOME.
Comment 20 Christoph Feck 2009-12-02 12:31:06 UTC
*** Bug 181779 has been marked as a duplicate of this bug. ***
Comment 21 JK 2010-01-04 22:17:09 UTC
Max votes from me --would love to see this fixed.
Comment 22 Geert Janssens 2010-01-20 12:23:39 UTC
I would like to see this fixed as well. It has bitten me on Fedora 12 and Mandriva 2010.
Comment 23 Rémi 2010-01-20 12:34:40 UTC
Hi all, just a little message to tell you it seems to be fixed in 4.4 :)
The tool is not perfect but it works for me. I do not need to use xrandr anymore :)
Comment 24 BRULE Herman 2010-01-20 12:42:54 UTC
Not here in svn.
Comment 25 spikethehobbitmage 2010-02-03 12:58:53 UTC
I had this problem as well.  A work around is to add
Option "RightOf" "<your primary monitor identifier>"
to the Monitor section for your secondary display in xorg.conf

remember to add Option "monitor-<xrandr name>" "monitor identifier" for each monitor to your "Device" section
Comment 26 Octavian Petre 2010-04-24 21:30:30 UTC
The option is in KDE 4.4.2. I will retract my votes
Comment 27 dE 2010-04-26 15:37:45 UTC
Then this bug should be CLOSED.
Comment 28 Christoph Feck 2010-05-29 05:46:26 UTC
*** Bug 239876 has been marked as a duplicate of this bug. ***
Comment 29 Andrey 2010-08-15 03:04:04 UTC
Yes, GUI is there,

but it does not work with my Intel 965GM and KDE 4.5.0.

At first it caused blinking monitor horror, which did not stop 
until I issued good old xrandr command tied to keyboard shotrcut.

After that it just stopped doing anything no matter which options I changed.

Does it work for anybody?
Comment 30 putt1ck 2010-08-15 07:26:24 UTC
Works for me. Kubuntu 10.04 (KDE 4.4.2), Intel Mobile GM965. Regression in 4.5?
Comment 31 BRULE Herman 2010-08-15 08:50:56 UTC
Not work here with open source drivers and ati radeon hd 4570 mobile.
Comment 32 Andrey 2010-08-16 16:38:37 UTC
(In reply to comment #30)
> Works for me. Kubuntu 10.04 (KDE 4.4.2), Intel Mobile GM965. Regression in 4.5?

By "Works" you mean you can set resolution for one monitor?

I tried setting external monitor and turning of internal, 
but it failed and just cloned internal resolution on external screen.

When I make a little bit more complex setup: 
another monitor on top of the internal _not_ in clone mode, 
it fails too. I tried various combinations of absolute/below/above.
But it just blinks many times and then clones one of the screen -> useless.

But xrandr from command line works perfectly: it blinks 1 time
and then sets resolutions and positions correctly.
This is command to place external monitor(VGA) above internal (LVDS):
xrandr --output LVDS --mode 1280x800 --rotate normal --pos 0x1200 --output VGA --mode 1920x1200 --rotate normal --pos 0x0
Comment 33 putt1ck 2010-08-16 16:47:05 UTC
Created attachment 50614 [details]
Screenshot of KDE screen settings showing 2 screens being managed
Comment 34 putt1ck 2010-08-16 16:49:02 UTC
I mean working working :)

Also working (now at my desk) on ATI Radeon X1650 Pro using open source radeon
driver. See attached screen shot.
Comment 35 dE 2010-08-17 09:42:04 UTC
Apparently this's fixed with KDE 4.4.4
Comment 36 Andrey 2010-08-17 12:40:32 UTC
Yes! Thank you for inspiring screenshot. 
Finally I see that it is really working working for me too!

Though, there are some glitches.

When you set your screen layout and then press "Apply",
a message appears to accept new layout. 
If you don't press "Accept" in about 15 seconds 
it reverts to previous configuration.

I think this is what was happening to me, but as my system
is not very fast and I have compositing enabled, 
screen was redrawn quite slowly and I just did not see 
this message properly. Plus sometimes Kwin doesn't redraw
windows correctly after changing resolution if compositing
is enabled (dodgy Intel drivers), so I saw that a message appears,
but didn't see what is written on it.

If composition is disabled changing screen resolution works faster
and dialog windows is displayed properly.

So I think that it would be quite sensible to make the delay
before Accept/Revert window disappears at least 30 seconds.

But there is workaround: you can just press Alt+A, if you sure,
that resolution is correct, but windows just redraw too slowly
or you just don't want to 

Another thing is that you cannot set primary screen,
so on Intel all panels and widgets will migrate to external
screen by default and you have to do it manually:
xrandr LVDS --primary
Here is bug about that: https://bugs.kde.org/show_bug.cgi?id=241719

Yet another glitch is with 90 and 270 orientations 
(useful for monitor with pivoting stand in portrait mode):
relative position is calculated incorrectly.
But if you set absolute positions for both monitors everything is fine.
But I think another bug report should be opened fo that one.

Conclusion:
no regression in KDE 4.5.0 for Intel 965GM. FIXED.
Though, cannot confirm this for ATI/NVidia at the moment - 
I don't have the hardware.
Comment 37 dE 2010-08-18 07:26:45 UTC
I have an ATI, no problems here.
Comment 38 Lubos Lunak 2010-08-31 14:57:08 UTC
*** Bug 181679 has been marked as a duplicate of this bug. ***
Comment 39 ttsoares 2010-10-08 16:13:47 UTC
ArchLinux. KDE 4.5.1. LVDS1 and VGA1. When one activates the VGA1 not to be a clone but an extension of LVDS1 at left, the desktop content from LVDS1 migrates to VGA1 and a new and empty desktop appears at LVDS1 !!

This was not the behavior some weeks ago. At that time the new desktop at VGA1 was the new (empty) one and the LVDS1 remains at the LCD display of the notebook...
Comment 40 ttsoares 2010-10-08 18:54:54 UTC
Complementing my comment:

The command

xrandr --output LVDS1 --mode 1280x800 --output VGA1 --auto --right-of LVDS1

result the exact same not desired behavior i described at the last comment here...

One could conclude that the problem is not with KDE but with xrandr itself...
Comment 41 fred 2010-10-08 19:24:03 UTC
(In reply to comment #40)
> Complementing my comment:
> 
> The command
> 
> xrandr --output LVDS1 --mode 1280x800 --output VGA1 --auto --right-of LVDS1
> 
> result the exact same not desired behavior i described at the last comment
> here...

try running:

xrandr --output LVDS1 --primary --mode 1280x800 --output VGA1 --auto --right-of LVDS1
Comment 42 ttsoares 2010-10-08 19:41:06 UTC
Yes !!!

A quick read at the man page of xrandr was not enough to me to realize this option "primary" !!

Now it would be nice that this solution reach the persons who take care of the module "Display and Monitor".

Many thanks fred.
Comment 43 Ricardo Graça 2010-11-21 14:11:49 UTC
In the latest version (4.5.3) there are still some problems with krandrtray in regards to positioning screens. It's still not possible to drag around the screens in the graphical representation as a way to place them. It's also not possible to define which one is the primary one. Also, sometimes I connect an external monitor to my laptop after kde startup and right-clicking on the krandrtray icon doesn't show the new monitor. Left clicking and going to the configuration dialog does work though.
Comment 44 slavo 2010-11-21 15:14:07 UTC
(In reply to comment #43)
> In the latest version (4.5.3) there are still some problems with krandrtray in
> regards to positioning screens. It's still not possible to drag around the
> screens in the graphical representation as a way to place them. It's also not
> possible to define which one is the primary one. Also, sometimes I connect an
> external monitor to my laptop after kde startup and right-clicking on the
> krandrtray icon doesn't show the new monitor. Left clicking and going to the
> configuration dialog does work though.

i confirm your problems too
Comment 45 RussianNeuroMancer 2013-04-23 00:45:59 UTC
Anyone from this bugreport able to reproduce it on latest KDE or with KScreen?
Comment 46 Geert Janssens 2014-08-22 15:13:08 UTC
Sorry for the late response. The request got lost in an overloaded mailbox...

I have just tried to set up two monitors, connected to an NVidia GForce GT640, using the nouveau driver on Fedora 20 (Gallium 0.4), KDE 4.13.

I had attached the second monitor to my running system and started Display settings module. I could move the screens around but after hitting apply the screens were not redrawn for some time and then reverted back to the original layout.

In a second test I booted the system with the two monitors attached. This time the Display settings module worked fine. I could move monitors around and choose which monitor to make primary.

I did not ever see the pop up dialog asking to confirm the settings for 15 seconds. Has this been removed ?
Comment 47 David Edmundson 2015-01-22 12:06:31 UTC
Thanks for reporting your bug.

Since reporting Krandr has since been replaced by KScreen. It is available in the Plasma 4 series, and is default in Plasma 5 onwards.

I hope this solves your issue. If you still have a problem after upgrading please reopen a new bug under kscreen.

Thanks