Launchpad has imported 45 comments from the remote bug at https://bugs.kde.org/show_bug.cgi?id=180437.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2009-01-12T10:57:02+00:00 Daniel Thaler wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/0 ------------------------------------------------------------------------ On 2009-01-20T19:37:43+00:00 Remi-assailly wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/1 ------------------------------------------------------------------------ On 2009-01-24T00:47:12+00:00 Orion-cora wrote: Me to. Fedora 10 with kde-testing 4.1.96 and ATI Radeon. I can set position fine with xrandr. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/2 ------------------------------------------------------------------------ On 2009-01-26T23:15:26+00:00 Orion-cora wrote: Still present with 4.2.0 from kde-testing repo. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/3 ------------------------------------------------------------------------ On 2009-05-10T00:13:00+00:00 Christoph-maxiom wrote: *** Bug 191880 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/4 ------------------------------------------------------------------------ On 2009-05-10T00:14:01+00:00 Christoph-maxiom wrote: *** Bug 185968 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/5 ------------------------------------------------------------------------ On 2009-05-10T02:25:40+00:00 Joe Mulloy wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/6 ------------------------------------------------------------------------ On 2009-06-30T09:23:23+00:00 Christoph-maxiom wrote: *** Bug 195649 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/7 ------------------------------------------------------------------------ On 2009-06-30T09:24:55+00:00 Christoph-maxiom wrote: *** Bug 197327 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/8 ------------------------------------------------------------------------ On 2009-06-30T17:36:47+00:00 Joe Mulloy wrote: 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? Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/9 ------------------------------------------------------------------------ On 2009-07-01T12:21:46+00:00 Khashayar Naderehvandi wrote: *** This bug has been confirmed by popular vote. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/10 ------------------------------------------------------------------------ On 2009-07-30T16:24:24+00:00 Christoph-maxiom wrote: *** Bug 201866 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/12 ------------------------------------------------------------------------ On 2009-07-30T16:39:11+00:00 Chris Puttick wrote: 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). Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/13 ------------------------------------------------------------------------ On 2009-08-24T14:52:21+00:00 Toni Helenius wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/24 ------------------------------------------------------------------------ On 2009-09-15T11:54:32+00:00 N-beernink wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/27 ------------------------------------------------------------------------ On 2009-10-08T16:26:20+00:00 7oby wrote: > 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/31 ------------------------------------------------------------------------ On 2009-10-11T13:42:14+00:00 7oby wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/35 ------------------------------------------------------------------------ On 2009-10-30T07:58:47+00:00 pseudonomous wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/40 ------------------------------------------------------------------------ On 2009-11-25T10:19:08+00:00 Dschaefer79-6 wrote: *** Bug 208518 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/57 ------------------------------------------------------------------------ On 2009-12-02T02:40:57+00:00 Dkbatson wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/58 ------------------------------------------------------------------------ On 2009-12-02T12:31:06+00:00 Christoph-maxiom wrote: *** Bug 181779 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/59 ------------------------------------------------------------------------ On 2010-01-04T22:17:09+00:00 Deus-ex-machin wrote: Max votes from me --would love to see this fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/61 ------------------------------------------------------------------------ On 2010-01-20T12:23:39+00:00 Geert Janssens wrote: I would like to see this fixed as well. It has bitten me on Fedora 12 and Mandriva 2010. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/62 ------------------------------------------------------------------------ On 2010-01-20T12:34:40+00:00 Remi-assailly wrote: 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 :) Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/63 ------------------------------------------------------------------------ On 2010-01-20T12:42:54+00:00 BRULE Herman wrote: Not here in svn. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/64 ------------------------------------------------------------------------ On 2010-02-03T12:58:53+00:00 Spikethehobbitmage wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/65 ------------------------------------------------------------------------ On 2010-04-24T21:30:30+00:00 Octavian Petre wrote: The option is in KDE 4.4.2. I will retract my votes Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/69 ------------------------------------------------------------------------ On 2010-04-26T15:37:45+00:00 dE wrote: Then this bug should be CLOSED. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/70 ------------------------------------------------------------------------ On 2010-05-29T05:46:26+00:00 Christoph-maxiom wrote: *** Bug 239876 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/71 ------------------------------------------------------------------------ On 2010-08-15T03:04:04+00:00 Andrey S wrote: 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? Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/72 ------------------------------------------------------------------------ On 2010-08-15T07:26:24+00:00 Chris Puttick wrote: Works for me. Kubuntu 10.04 (KDE 4.4.2), Intel Mobile GM965. Regression in 4.5? Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/73 ------------------------------------------------------------------------ On 2010-08-15T08:50:56+00:00 BRULE Herman wrote: Not work here with open source drivers and ati radeon hd 4570 mobile. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/74 ------------------------------------------------------------------------ On 2010-08-16T16:38:37+00:00 Andrey S wrote: (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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/75 ------------------------------------------------------------------------ On 2010-08-16T16:47:05+00:00 Chris Puttick wrote: Created attachment 50614 Screenshot of KDE screen settings showing 2 screens being managed Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/76 ------------------------------------------------------------------------ On 2010-08-16T16:49:02+00:00 Chris Puttick wrote: I mean working working :) Also working (now at my desk) on ATI Radeon X1650 Pro using open source radeon driver. See attached screen shot. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/77 ------------------------------------------------------------------------ On 2010-08-17T09:42:04+00:00 dE wrote: Apparently this's fixed with KDE 4.4.4 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/78 ------------------------------------------------------------------------ On 2010-08-17T12:40:32+00:00 Andrey S wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/79 ------------------------------------------------------------------------ On 2010-08-18T07:26:45+00:00 dE wrote: I have an ATI, no problems here. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/80 ------------------------------------------------------------------------ On 2010-08-31T14:57:08+00:00 L-lunak-5 wrote: *** Bug 181679 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/81 ------------------------------------------------------------------------ On 2010-10-08T16:13:47+00:00 Ttsoares wrote: 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... Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/82 ------------------------------------------------------------------------ On 2010-10-08T18:54:54+00:00 Ttsoares wrote: 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... Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/83 ------------------------------------------------------------------------ On 2010-10-08T19:24:03+00:00 pseudonomous wrote: (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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/84 ------------------------------------------------------------------------ On 2010-10-08T19:41:06+00:00 Ttsoares wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/85 ------------------------------------------------------------------------ On 2010-11-21T14:11:49+00:00 Ricardo Graça wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/86 ------------------------------------------------------------------------ On 2010-11-21T15:14:07+00:00 slavo wrote: (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 Reply at: https://bugs.launchpad.net/ubuntu/+source/kdebase- workspace/+bug/403610/comments/87 ** Changed in: kde-baseapps Status: Confirmed => Unknown ** Bug watch added: KDE Bug Tracking System #172315 https://bugs.kde.org/show_bug.cgi?id=172315 ** Bug watch added: KDE Bug Tracking System #241719 https://bugs.kde.org/show_bug.cgi?id=241719 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in Ubuntu. https://bugs.launchpad.net/bugs/403610 Title: kde 4.3 Multiple Monitors tells lies To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/403610/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
