Bug 230872 - KDE doesn't remember multi-monitor configuration
Summary: KDE doesn't remember multi-monitor configuration
Status: RESOLVED UNMAINTAINED
Alias: None
Product: krandr
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.6
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-15 20:41 UTC by Alexey Chernov
Modified: 2015-01-23 00:08 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexey Chernov 2010-03-15 20:41:33 UTC
Version:            (using KDE 4.4.1)
Compiler:          GCC 4.4.3 Target: x86_64-unknown-linux-gnu Configured with: ../gcc-4.4.3/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,fortran --disable-multilib --disable-bootstrap Thread model: posix
OS:                Linux
Installed from:    Compiled From Sources

Settings of multi-monitor configuration (layout, mode etc.) made in System Settings/Display somehow aren't stored and on next login fall back to 'Clone' mode which is in fact not multi-monitor configuration. If I go to Settings and setup everything again it switches to the correct mode at once, no problem. But I have to go there after every login.

xorg.conf settings are somehow ignored.
Comment 1 Cade Robinson 2010-04-21 20:23:47 UTC
I see this with kde 4.4.2 debian packages as well.
I tried running systemsettings as root to see if it would save and it doesn't.
Running systemsettings as root did show multiple monitors in the "Multiple Monitors" section where as I get a message that I don't have multiple monitors.

I am using an ATI Radeon HD 2400 XT using the "radeon" X driver.
Comment 2 Cade Robinson 2010-04-21 20:42:00 UTC
I added a script to ~/.kde/Autostart to do the xrandr for me:
xrandr --output DVI-1 --right-of DVI-0

This "works" but it shouldn't have to set that way as system settings should remember it.
Comment 3 Alexey Chernov 2010-08-19 22:32:19 UTC
Is there for 4.5.0.

Sorry, will there be any activity on this bug? I can't use multimonitor configuration with KDE properly at all because of it.
Could someone at least give any references where these settings are applied on startup because I've checked they are saved properly to ~/.kde/share/config/krandrrc
Comment 4 Jonathan 2010-09-28 12:48:41 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 benni 2010-10-13 08:41:44 UTC
Does this bug still exist ? (using nvidia-drivers atm and can't test)
Comment 6 Alexey Chernov 2010-10-13 08:55:05 UTC
Yes it is. But I think the bug is reproducible when you use something other than kdm (e.g. gdm or console login - my personal case). I think the problem is that only KDM restores the multihead settings and when you start KDE with startkde or startx nothing is being restored as KDM is skipped.

I think the resolution is in copying restoring code from KDM to KWin or something which can check if the proper multihead mode is already set and if not set it correctly.
Comment 7 Alexey Chernov 2010-11-04 00:21:52 UTC
I seem to find the problem. Well, it's complex:
1. Randr (multi-monitor) configuration is read in startkde script and it is read from ~/.kde/share/config/kcmrandrrc instead of ~/.kde/share/config/krandrrc
2. It reads only screens with defined names e.g. [Screen0] while modern kcmrandr applet of systemsettings creates custom-named screens e.g. [Screen_0_Output_DisplayPort-0]
3. It reads wrong or obsolete parameters. For instance, it tries to read width and height of the screen while config has only Rect property which equals for example 0,0,1920,1200
4. It reads and uses not all the necessary and stored information. For instance, it doesn't care of offset of the screen e.g. all the screens are started from 0, 0.

So the problem is inside startkde script which is generated from startkde.cmake when compiling. I'll try to fix it and see the result.
Comment 8 Jonathan 2011-01-30 23:20:15 UTC
The system settings offer a new functionality in 4.6.0 which is saving the current display configuration as default. Thus after relogin the multi-monitor configuration is restored. So for me this bug is fixed.
Comment 9 Alexey Chernov 2011-01-30 23:22:14 UTC
Yes, exactly. I'm just forgot to write here after upgrade.
Comment 10 Jonathan 2011-01-30 23:25:54 UTC
Thanks a lot for your work!

I guess this bug can be closed then.
Comment 11 Alexey Chernov 2011-01-31 00:16:05 UTC
Hm, thanks, but I'm not the author of the fix :) In fact I've almost done my variant of the fix, but in 4.6.0 another way was introduced (that's to store full xrandr startup commands in config while I tried to analyze the config in startkde and create command in script). I meant I also noticed that it started working on 4.6.0 after upgrade from 4.5.x.

I agree, thanks for this fix, works just fine.
Comment 12 Georg Greve 2011-09-30 12:44:24 UTC
FWIW, I'd also love to see this fixed.

Right now KDE assumes a new monitor is located on the right, but mine is on the left. So memorizing where a particular monitor is typically located would be a good thing.
Comment 13 Leszek Lesner 2012-09-07 18:28:14 UTC
It would be even better to save the last configuration of an detected monitor and restore it whenever the monitor is plugged in.
Comment 14 Don 2013-04-27 16:31:01 UTC
I'm on 4.10.2, setup a multiple monitor (left-right) config and it gets lots upon logout.

Still broke for me.
Comment 15 Georg Greve 2013-04-29 10:38:16 UTC
Still broken here as well.

KDE 4.10.2 on Fedora w/Red Hat RPMs.
Comment 16 co2 2014-05-17 10:15:29 UTC
I'm also affected by this. 

KDE 4.13 on ArchLinux.
Comment 17 Christoph Feck 2015-01-23 00:08:15 UTC
Thank you for your bug report or feature request.

Unfortunately, we did not have a maintainer for the "krandr" components, which are used to manage displays and monitors in the KDE Workspaces.

The "krandr" components has been superseded by "KScreen" in newer releases of the KDE Workspaces. It is compatible with all versions since 4.11, and is also used with Plasma 5. Please check with your distribution how to update to KScreen.

If this issue or feature request is still applicable to KScreen version 1.0.5 or newer, please add a comment. We will then reassign this ticket to KScreen developers.

If you are already using KScreen to manage displays or monitors, and found a different bug or need a specific feature, please create a new ticket for "KScreen" product in this bugzilla using this link: https://bugs.kde.org/enter_bug.cgi?product=KScreen

(This is an automatic message from the KDE Bug Triaging Team)