Screen resolution - not using set value at boot.

[Rednex]

For me this bug (https://bugs.launchpad.net/ubuntu/+bug/296797, discussed here: http://kubuntuforums.net/forums/inde...opic=3098968.0) is back with 9.10 (it was there on 8.10, gone in 9.04)!

I'd love to work @ 1600x1200, but every reboot reverts me back to something lower, which screws up all my widgets placement, etc. - annoying !!!

Opening System Settings and just clicking on Display puts screen res back to what I have set, but I still have to place widgets back manually.

Any ideas?

[Guest]

Re: Screen resolution - not using set value at boot.

I'm having the same issue and it's bugging me to know end. I've tried changing the screen refresh settings with no luck at all. I've had this issue every since I upgraded to Kubuntu 9.10.

The screen refresh rates are not right at all either. I have 2 choices, 52, 55 or auto. Shouldn't it be running at 60? Forget about trying to use dual display that is a real mess. No matter was resolution I set the monitor at, it will always boot up in 1680/1050 the monitors max supported res. I will click on the display properties and it go to the res I set. Anyone help with this issue.

Video Card: Nvidia 9400/ 1gig ram
2 Dell FP 24" monitors. I have only 1 connected at the moment.
Driver Nvidia 185. I've reverted to 173 with the same results.

Any help would be greatly appreciated.

[finny388]

Re: Screen resolution - not using set value at boot.

me too
As soon as I open the Display Setting Dialog, the resolution is corrected
but I lose my widget and wallpaper settings every time

very frustrating

is this a known bug or is there a known fix?

please and thank you

[bernd2]

Re: Screen resolution - not using set value at boot.

I've got a similar problem;

I set my preferred resolution in the settings manager and it works. After a reboot, KDE sets another resolution(way to high). I have to go to settings manager, clik on display settings and immediatly after the clik KDE sets my preferred resolution.

Very anoying to do this everytime on startup!

I tried to make an xorg.conf file in /etc/X11, but no difference (the only difference is that I can add or delete resolutionoptions in settings manager)

[dibl]

Re: Screen resolution - not using set value at boot.

For your Nvidia cards, this has the procedure to set the default resolution:

http://kubuntuforums.net/forums/inde...opic=3107406.0

[sithlord48]

Re: Screen resolution - not using set value at boot.

if you have an ati card , use this instead

[code= run in krunner (alt+f2)]
kdesudo amdcccle
[/code]

then under display set desired res, and be sure to apply (if needed i can post more accurate discreption , but i am away from the machine w/ my ati card.. right now)

[bernd2]

Re: Screen resolution - not using set value at boot.

lol,

This time I'm trying to fix a friends computer, it has an on-board card of intel:

Intel Corporation 82865G Integrated Graphics Controller (rev 02)

Meanwhile, I found some more info about what's going wrong in ~.xsession-errors:

Setting IM through im-switch for locale=nl_BE.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/defau$
Bus error
xset: bad font path element (#23), possible causes are:
Directory does not exist or has wrong permissions
Directory missing fonts.dir
Incorrect font server address or syntax
startkde: Starting up...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_klauncher.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kded4.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kbuildsycoca4.so
kbuildsycoca4 running...
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kconf_update.so
Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Ses$
Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Sess$
Invalid D-BUS member name 'x11-display-device' found in interface 'org.freedesktop.Conso$
Invalid D-BUS member name 'x11-display' found in interface 'org.freedesktop.ConsoleKit.S$
Invalid D-BUS member name 'display-device' found in interface 'org.freedesktop.ConsoleKi$
Invalid D-BUS member name 'remote-host-name' found in interface 'org.freedesktop.Console$
Invalid D-BUS member name 'session-type' found in interface 'org.freedesktop.ConsoleKit.$
Invalid D-BUS member name 'unix-user' found in interface 'org.freedesktop.ConsoleKit.Ses$
X Error: XSyncBadAlarm 152
Extension: 143 (Uknown extension)
Minor opcode: 11 (Unknown request)
Resource id: 0x0
X Error: XSyncBadAlarm 152
Extension: 143 (Uknown extension)
Minor opcode: 11 (Unknown request)
Resource id: 0x0
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kglobalaccel.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kcminit_startup.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_ksmserver.so
<unknown program name>(1487)/ KStartupInfo::createNewStartupId: creating: "tois;1262189$
kephald starting up
XRANDR error base: 162
RRInput mask is set!!
RandRScreen::loadSettings - adding mode: 59 1280 x 1024
RandRScreen::loadSettings - adding mode: 60 1152 x 864
RandRScreen::loadSettings - adding mode: 61 1024 x 768
RandRScreen::loadSettings - adding mode: 62 1024 x 768
RandRScreen::loadSettings - adding mode: 63 1024 x 768
RandRScreen::loadSettings - adding mode: 64 832 x 624
RandRScreen::loadSettings - adding mode: 65 800 x 600
RandRScreen::loadSettings - adding mode: 66 800 x 600
RandRScreen::loadSettings - adding mode: 67 800 x 600
RandRScreen::loadSettings - adding mode: 68 800 x 600
RandRScreen::loadSettings - adding mode: 69 640 x 480
RandRScreen::loadSettings - adding mode: 70 640 x 480
RandRScreen::loadSettings - adding mode: 71 640 x 480
RandRScreen::loadSettings - adding mode: 72 640 x 480
RandRScreen::loadSettings - adding mode: 73 720 x 400
RandRScreen::loadSettings - adding mode: 74 720 x 400
RandRScreen::loadSettings - adding mode: 75 720 x 400
RandRScreen::loadSettings - adding mode: 76 640 x 400
RandRScreen::loadSettings - adding mode: 77 640 x 350
RandRScreen::loadSettings - adding crtc: 57
RandRScreen::loadSettings - adding output: 58
Setting CRTC 57 on output "VGA1" (previous 0 )
CRTC outputs: (58)
Output name: "VGA1"
Output refresh rate: 60.0197
Output rect: QRect(0,0 1280x1024)
Output rotation: 1
XRandROutputs::init
got a valid edid block...
vendor code: "DPC"
product id: 6000
serial number: 0
added output 58
adding an output 0 with geom: QRect(0,0 1280x1024)
output: "SCREEN-0" QRect(0,0 1280x1024) 0 true false
load xml
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
screen: 0 QRect(0,0 1280x1024)
looking for a matching configuration...
connected: 1
looking for current "SCREEN-0"
known "*" has score: 0.125
screen: 0 QRect(0,0 1280x1024)
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

etc...

The preferred resolution is 1024x768@75.1Hz, the reso 1280x1024 to wich KDE automaticaly sets is really not pleasent for the eyes

[KeithZG]

Re: Screen resolution - not using set value at boot.

I'm having the OP's problem in a nutshell, with a slightly added complication that System Settings is forgetting every time that I have the laptop's display disabled (it's broken, so just displays mostly garbage). So every time I restart the computer the displays are set back to a rather annoyingly small and stretched resolution, and upon clicking on the Display option in System Settings things revert to what they should be set at to start with, but then I also have to go and disable the laptop LCD again.

For your Nvidia cards, this has the procedure to set the default resolution:

http://kubuntuforums.net/forums/inde...opic=3107406.0

if you have an ati card , use this instead

[code= run in krunner (alt+f2)]
kdesudo amdcccle
[/code]

then under display set desired res, and be sure to apply (if needed i can post more accurate discreption , but i am away from the machine w/ my ati card.. right now)

I've actually been an OSS puritan, and the computer in question is using an Intel chip with those entirely open source drivers . . . which means neither of those control centers are called for, and KDE is supposed to be able to do all this through its built-in tools and settings . . .

[KeithZG]

Re: Screen resolution - not using set value at boot.

... no answers? Has anyone tried Lucid on an offending setup to see if there's an upstream fix?

[Guest]

Re: Screen resolution - not using set value at boot.

I have the same problem which only appeared after the upgrade from 9.04 to 9.10. I generally deal with it by not having too many widgets and not turning off the pc more than once a day.

[KeithZG]

Re: Screen resolution - not using set value at boot.

Sad that there's no sign of any fix, it's a rather irritating bug, the kind of thing that I can see a non-techie being quite frustrated by.

Oh well, Lucid is nearly upon us; we'll see then, I suppose, if time heals all wounds.

(P.S. Typing this from Lucid right now, but though it's with Konqueror it's in OpenBox; a release still in development + Nouveau + KWin = crash! heh.)

[sithlord48]

Re: Screen resolution - not using set value at boot.

the computer in question is using an Intel chip

i wonder caligo do you also have an intel gfx chip?
on this netbook i have an intel gfx card, and i have only have an issue when i plug in a ext monitor to the netbook the computer fails to set a mode for the monitor at all and does not let me select one in system settings. it completely acts as if there is no monitor connected.

[KeithZG]

Re: Screen resolution - not using set value at boot.

the computer in question is using an Intel chip

i wonder caligo do you also have an intel gfx chip?
on this netbook i have an intel gfx card, and i have only have an issue when i plug in a ext monitor to the netbook the computer fails to set a mode for the monitor at all and does not let me select one in system settings. it completely acts as if there is no monitor connected.

Hmmmmm. Mine acts a bit nicer, but it's definitely only when there's an external monitor that's connected that it does it (admittedly I only ever run this netbook with an external monitor connected since the screen is mostly broken, but it's still "working" enough that I can boot it up without having the monitor plugged in and I can see that in theory it's setting the display parameters correctly then). So perhaps the common denominator for the problem persisting with the current iteration of *buntu is Intel chip + external monitor.

[sithlord48]

Re: Screen resolution - not using set value at boot.

i just dug out my ext monitor. to test again and now it works. but i had to set a res for it, i should leave it pluged in a do a few reboots see if it remains working..