Bug 292419 - KDE reset display setting for two display configuration every boot (or maybe just doesn't read saved configuration)
Summary: KDE reset display setting for two display configuration every boot (or maybe ...
Status: RESOLVED WORKSFORME
Alias: None
Product: krandr
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-25 23:37 UTC by RussianNeuroMancer
Modified: 2012-06-20 07:49 UTC (History)
3 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 RussianNeuroMancer 2012-01-25 23:37:21 UTC
Version:           4.8.0 (using KDE 4.7.4) 
OS:                Linux

I doesn't sure related this bug to kwin or not. If I mistake please reassign to right KDE component.

This bug appear only today after upgrade to KDE 4.8.0. Before with KDE 4.7.x two display configuration work fine on this laptop.

Reproducible: Didn't try

Steps to Reproduce:
Boot laptop with attached external HDMI display (probably should be reproduceable for desktop with two or three displays too). Configure second display via System Settings - set proper resolution, refresh rate, select main output, etc. Save configuration as default. Now reboot.

Actual Results:  
Laptop display is disabled. Resolution of HDMI display is 800x600 (or something like that). Looks like KDE doesn't read display configuration while login.
In my case displays was configured via system settings on KDE 4.7.x and proper default configuration already in place and work fine before upgrade to 4.8.0.

Expected Results:  
KDE 4.8 read saved display configuration and apply it while login like 4.7.

KDE version: 4.8.0 (from ppa:kubuntu-ppa/backports).
Kubuntu 11.10 x86_64.
Video driver R600g, GPU is AMD Radeon HD 6620G (AMD APU A8-3500M integrated GPU).

Two displays (laptop 1600x900 and separate HDMI display 1920x1080) was configured via System Settings (xorg.conf is not used at all).

There is no such problem for one display configuration.
Comment 1 RussianNeuroMancer 2012-01-25 23:38:54 UTC
Reproducible: Always. I check this few times.
Comment 2 RussianNeuroMancer 2012-01-26 08:08:42 UTC
Tested with nouveau - same issue. Only one difference: laptop display is not disabled while login.
Comment 3 Dominic Lyons 2012-01-27 19:30:17 UTC
Same problem here: On rebooting screens are unified and at low resolution. 

Then I reconfigured the displays and the correct settings are wrote to ~/.kde/share/config/krandrrc. After deleting this file and reconfiguring the file is written correctly again (I wanted to assure that the file is not outdated and the settings are written to somewhere else by now).

file krandrrc:
-------------------------------
[Display]
ApplyOnStartup=true
StartupCommands=xrandr --output VGA-0 --pos 1920x0 --mode 1280x1024 --refresh 60.0197\nxrandr --output DVI-0 --pos 0x0 --mode 1920x1200 --refresh 59.9502\nxrandr --output DVI-0 --primary

[Screen_0]
OutputsUnified=false
UnifiedRect=0,0,0,0
UnifiedRotation=1

[Screen_0_Output_DVI-0]
Active=true
Rect=0,0,1920,1200
RefreshRate=59.9501724243164
Rotation=1

[Screen_0_Output_VGA-0]
Active=true
Rect=1920,0,1280,1024
RefreshRate=60.0038414001465
Rotation=1
-------------------------------------------


I have tested the command at StartupCommand. It is correct so I guess the command doesn't get executed at KDE startup.

This is reproducible.
Comment 4 Dominic Lyons 2012-01-27 19:40:48 UTC
I forgot something:

KDE version: 4.8.0 (from ppa:kubuntu-ppa/backports).
Kubuntu 11.10 x86_64.
Radeon video driver
Comment 5 Dominic Lyons 2012-01-27 19:47:17 UTC
Possible Duplicates:
* https://bugs.kde.org/show_bug.cgi?id=290240
* https://bugs.kde.org/show_bug.cgi?id=283625 (not sure, this is KDE 4.7.2)
Comment 6 Thomas Lübking 2012-01-27 19:50:57 UTC
this sounds like bug #183143 (but i've little insight in this)
Comment 7 RussianNeuroMancer 2012-04-12 23:18:32 UTC
Resolved for me with upgrade to 4.8.1.