Comment 49 for bug 268434
Revision history for this message
|
|
#49 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I can confirm this behaviour and have a "bandaid" resolution.
**THE SYSTEM**
I'm running a unstable (~x86) Gentoo Linux system.
I've built KDE from R908976 of the 4.2 SVN branch.
I'm using QT version 4.4.2
I'm using version 6.9.0 of xf86-video-ati on an AGP R420 (Radeon X800)
I'm using version 7.4 of xorg-x11.
**THE BUG**
This behaviour is seen when setting KDE's resolution to anything lower than the display adaptor/monitor's maximum resolution, then logging out, and logging back in.
Repro recipe for a system with a maximum resolution of 1600x1200:
* Start KDE.
* Open the "Display" System Settings applet.
* Set the "Size" of your monitors to something smaller than 1600x1200.
* Click "Apply".
* Close the System Settings window and log out.
* Start KDE.
* Watch the display size be set to 1600x1200.
** Opening the "Display" System Settings applet correctly reset the screen resolution.
** Starting krandrtray also correctly resets the screen resolution.
I've repro'd this with a monitor whose max resolution was 1024x768 and one whose max resolution was 1856x1392. I would imagine that this bug is triggered regardless of max resolution.
**THE PROPOSED BANDAID**
Add krandrtray to the list of applications that get started at default.
**THE RATIONALE**
The prototypical visually-impaired grandma with the 24" CRT that her geeky son set to 1024x768 will have to reconfigure her system each and every time she logs in. This would get really annoying, really fast. (It's annoying when it happens to me, at least.)
Also, -unless the "automatically start Strigi, Nepomuk, and Akonadi" setting is stored somewhere other than ~/.kde4- we're starting Strigi, Nepomuk, and Akonadi on startup as well. I imagine that an average user would care about his desktop resolution decision being constantly ignored long before he worried about file indexing.
And, Half-Left in #kde spoke to Aaron Seigo about it. Siego agreed that it should be started by default.
Let me know if I can provide more info. I'm not afraid of applying patches or experimental code, either!