Version: 0.5 (using KDE 4.3.1) OS: Linux Installed from: Ubuntu Packages My krandrrc file looks like this: cat ~/.kde/share/config/krandrrc [Screen_0] OutputsUnified=false UnifiedRect=0,0,1024,768 UnifiedRotation=1 [Screen_0_Output_DVI1] Active=true Rect=0,0,1920,1200 RefreshRate=60.0038414001465 Rotation=1 [Screen_0_Output_LVDS1] Active=false Rect=0,0,1280,800 RefreshRate=0 Rotation=1 It's a notebook whose external display is activated and whose internal LVDS display is DEactivated. If I log into kdm it applies the settings of this file just fine. However at the same time during logon it changed one setting in krandrrc: [Screen_0_Output_LVDS1] Active=true The next time I logon from kdm the LVDS display is ACTIVATED this way and usually stays activated until I use krandrtray. Doing that I can DEactivate the LVDS display again and also krandrrc gets set to the previous setting. This will safe me - but only for the next session. After that krandrrc is changed again by MAGIC. -- At first sight this bug looks as a duplicate to this one: https://bugs.kde.org/show_bug.cgi?id=163707 The workaround for the bug above is to launch krandtray. In fact this happens on my KDE 4.3.0 Kubuntu 9.10 beta system already. It is launched by default as proposed in comment #2 in the above bug. I can see it's running since it indeed applies the settings of krandrrc and it's also present in the kicker bar. The bug I'm reporting here is DIFFERENT from the one above. -- I'm on intel GM965 (X3100 graphics) hardware. It's current X driver has a particular and specific feature which can be observed in /var/log/Xorg.0.log: (II) intel(0): Using fuzzy aspect match for initial modes What this actually does is open LVDS1 and DVI1 in 1024 x 768 in CLONE mode. This the highest common resolution supported by BOTH of my displays. There is currently no way around this - that's by design as Keith Packard explains in his blog under section "Initial Mode Selection": http://keithp.com/blogs/X_output_status_july_2008/ I'm not sure whether the initial DUAL CLONE mode configuration is in some weird sense responsible for some other part of KDE (I assume krandrtray) to activate LVDS1 in krandrrc.
Let me get this straight: Version: 0.5 (using KDE 4.3.2) OS: Linux Installed from: Kubuntu 9.10 beta Arch: x86_64 X-Server: 1.6.3 intel-driver: 2.8.1
Since the upgrade to KDE 4.4.3 I'm seeing this too. On every login I get the recommended resolution for my display (1280x1024) instead of the preferred 1600x1200 which I've set through KRandR (or krandrtray these days). Until KDE 4.3 everything worked as expected, now I need to set the resolution manually after each KDM restart (which normally means: after every reboot). If KDM keeps running, the correct resolution is set after login. I'm on Debian Squeeze. Additional note: this might(!!!) be a duplicate of bug 164774
I must correct my first assessment. KRandR didn't change the settings in krandrrc (the change I saw came from a different source). But still fails to restore the correct resolution on login/start. But as my problem is different from the one reported here, I'll retract my previous statement and will look for either the correct bug to support or file a new one.
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)