Bug 229385 - display resolution not saved by "system settings"
Summary: display resolution not saved by "system settings"
Status: RESOLVED DUPLICATE of bug 183143
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-04 13:03 UTC by George R. Goffe
Modified: 2010-09-10 14:02 UTC (History)
6 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 George R. Goffe 2010-03-04 13:03:44 UTC
Version:           1.0 (using 4.4.00 (KDE 4.4.0), 4.4.0-9.fc12 Fedora)
Compiler:          gcc
OS:                Linux (i686) release 2.6.31.12-174.2.22.fc12.i686

I'm trying to set my screen resolution via "system settings". This is successfully but when I restart kde the old settings are back in effect. I have tried saving the session but that did not work.

I am definitely willing to test changes and/or give more info.

Thank you.

George...
Comment 1 Anne-Marie Mahfouf 2010-03-04 14:36:46 UTC
Confirmed in 4.4 branch (did not check trunk)
Comment 2 Anthony Youngman 2010-03-17 20:52:56 UTC
This is important, to me at least :-)

I have a new linux user, with an HP 2009v screen. This unfortunately reports its resolution (correctly) to linux as 1600x900. However, it then goes into 1440x900 resolution and there is (apparently) NO way to change the resolution using the buttons on the screen :-(

So the poor user has to try and fight their way into System Settings to change the resolution, when Geeko (and hence the system menu) is invisible off the left of the screen :-(

NOT the impression I want to give a new user :-(

It wouldn't normally matter, but interacting with this ?hardware? problem makes it a bit of a problem. (I do gather XP suffers a similar problem :-)

Cheers,
Wol
Comment 3 Ben Cooksley 2010-03-17 21:59:08 UTC
As a workaround, add "krandrtray" to the list of applications to startup. This can be done using System Settings > Advanced > Autostart, or by copying its *.desktop to ~/.kde4/Autostart
Comment 4 Robin Knapp 2010-04-01 12:49:38 UTC
I created an example configuration in vmware.
- X-Server default resolution is 1024x768
- KDE systemsettings set to 800x600

Content of .kde4/share/config/krandrrc:
[Screen_0]
OutputsUnified=false
UnifiedRect=0,0,0,0
UnifiedRotation=1

[Screen_0_Output_default]
Active=true
Rect=0,0,800,600
RefreshRate=60
Rotation=1


Output of .xsession-errors:
kephald starting up
XRANDR error base:  162
RRInput mask is set!!
RandRScreen::loadSettings - adding mode:  265 1024 x 768
RandRScreen::loadSettings - adding mode:  266 1024 x 768
RandRScreen::loadSettings - adding mode:  267 800 x 600
RandRScreen::loadSettings - adding mode:  268 800 x 600
RandRScreen::loadSettings - adding mode:  269 800 x 600
RandRScreen::loadSettings - adding mode:  270 640 x 480
RandRScreen::loadSettings - adding mode:  271 640 x 480
RandRScreen::loadSettings - adding mode:  272 320 x 240
RandRScreen::loadSettings - adding mode:  273 400 x 300
RandRScreen::loadSettings - adding mode:  274 512 x 384
RandRScreen::loadSettings - adding mode:  275 1152 x 864
RandRScreen::loadSettings - adding mode:  276 1280 x 960
RandRScreen::loadSettings - adding mode:  277 1400 x 1050
RandRScreen::loadSettings - adding mode:  278 1600 x 1200
RandRScreen::loadSettings - adding mode:  279 1920 x 1440
RandRScreen::loadSettings - adding mode:  280 2048 x 1536
RandRScreen::loadSettings - adding mode:  281 854 x 480
RandRScreen::loadSettings - adding mode:  282 1280 x 720
RandRScreen::loadSettings - adding mode:  283 1366 x 768
RandRScreen::loadSettings - adding mode:  284 1920 x 1080
RandRScreen::loadSettings - adding mode:  285 1280 x 800
RandRScreen::loadSettings - adding mode:  286 1440 x 900
RandRScreen::loadSettings - adding mode:  287 1680 x 1050
RandRScreen::loadSettings - adding mode:  288 1920 x 1200
RandRScreen::loadSettings - adding mode:  289 720 x 480
RandRScreen::loadSettings - adding mode:  290 720 x 576
RandRScreen::loadSettings - adding mode:  291 320 x 200
RandRScreen::loadSettings - adding mode:  292 640 x 400
RandRScreen::loadSettings - adding mode:  293 800 x 480
RandRScreen::loadSettings - adding mode:  294 1280 x 768
RandRScreen::loadSettings - adding mode:  295 1280 x 1024
RandRScreen::loadSettings - adding mode:  296 2360 x 1770
RandRScreen::loadSettings - adding crtc:  263
RandRScreen::loadSettings - adding output:  264
Setting CRTC 263 on output "default" (previous 0 )
CRTC outputs: (264)
Output name: "default"
Output refresh rate: 60
Output rect: QRect(0,0 1024x768)
Output rotation: 1
XRandROutputs::init
  added output  264
adding an output 0 with geom:  QRect(0,0 1024x768)
output: "SCREEN-0" QRect(0,0 1024x768) -1162167622 true true
load xml
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
screen: 0 QRect(0,0 1024x768)
looking for a matching configuration...
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
found outputs, known: false
activate external configuration!!
registered the service: true
screens registered on the bus: true
outputs registered on the bus: true
configurations registered on the bus: true
kded(7300)/kded4 Kded::loadModule: Successfully loaded module "kephal"



So kephald does not read krandrrc?
Comment 5 Christoph Feck 2010-04-22 16:54:31 UTC

*** This bug has been marked as a duplicate of bug 183143 ***
Comment 6 dramascus 2010-09-09 00:11:13 UTC
Not resolved at all. This has been a problem for me across three distro's and since kde 4.1. Will some one for the love of god fix this properly.
Comment 7 Anthony Youngman 2010-09-10 14:02:49 UTC
Almost certainly related ...

Take a look at bug 246298, which has been marked as "resolved". That's probably actually a duplicate of this bug, but the report goes into far more detail, and guy who's flagged it as fixed (lunak1) seems to have cleaned up a load of stuff.

I haven't got the latest KDE (I'm waiting for gentoo to update it :-) so I can't confirm it really is fixed.

Cheers,
Wol