This problem of kde-4.x.x not respecting my screen/monitor resolutions has plagued my kde systems since kde-4.x.x was released, In Gentoo portage or overlay versions, and also on Arch, Pclos, and a few other distros I've tried. I've never found a decent hack or fix that survives for long. It's so annoying to have to reset the screen resolution on every reboot, it almost makes me want quit kde for good. I'm hoping this is the final fix, but unfortunately it seems it won't be introduced until 4.6.0 is released next year.

If anyone can confirm it works, I'll go back to trunk/overlay on one of my kde installs, and just use another DE on my other boxes until 4.6.0 is out.

Is there perhaps a way to hack/backport this fix into 4.5.1? Seems like editing in all the changes made by lunaki in revision 1170315 kdebase/workspace/kcontrol/randr trunk into the portage version 4.5.1 might be worth a shot- or is there more to it than that?
Sure would be nice to have a button in System Settings->Display like it used to be in kde3 "Apply settings at startup"! Seems like I read somewhere that was what these svn commits did.
Any feedback is eagerly anticipated.

[rant] I must say, and even though I've always been a big kde fan and user, for any major and supposedly world-class Desktop Environment to allow this serious problem to exist and continue for so long is a disgrace. I'm sorry, but for any DE user the ability of the system to retain personal screen resolution settings every time you boot the computer is a number one major priority. There was never any problem in kde3, and this should have been completely resolved in kde4 from day one. There's no excuse or reason I can fathom that explains why it hasn't been addressed, unless the kde devs never reboot their machines and so haven't noticed there is a major problem driving their users crazy. [/rant]_________________Main box- Gigabyte GIGABYTE GA-990FXA-UD3 AM3+ rev.-4.0
Amd FX 8320, 3.5 GHz, 16GB GSkill DDR3 1866mhz
Samsung SATA 1000GB, Radeon HD 6570 2GB DDR3
Gentoo ~x86, ~amd64, glibc-2.20-r1, gcc-4.9.2 kernel-3.19.0-gentoo (USE=experimental "native")

Last edited by wrc1944 on Fri Sep 17, 2010 3:36 am; edited 1 time in total

While booted to Gnome, I installed from the kde-live overlay (KDE Development Platform 4.5.68 (4.6 >= 20100912). (I had kde-4.5.1 overlay version installed on this ~amd64 system). I then logged out of gnome and into the newly installed kde-live OK, and applied my desired screen resolution of 1600x1200@70.
There is now a "Save as Default" button in System Settings->Display and Monitor, and apparently it works! On reboot, my 1600x1200@70 was retained, and there was now (finally) a kcmdisplayrc file in /home/wrc/.kde4/share/config, and my krandrrc file now reflects what I set in system settings.

This seems to be at last the long-lost configuration I have been waiting to see.
Kudos to KDE Dev lunaki and his wonderful kdebase/workspace/kcontrol/randr revision 1170315!

Please, please backport to kde-4.5.1 Gentoo portage, as I wish to avoid having to use the overlay live version on my other kde installations. In fact, I probably won't be using kde-4.5.x anymore and have to wait for 4.6.0, due to this one big problem.

Well, I'm not sure if you actually should when there are no issues with qt-4.6.x, but at this (final) stage of 4.7.0, it is supposed to be mostly harmless._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

I have been using it for several months now and while I had some issues with the original one not connecting to wireless networks, those seem to have gone away with the latest revision, although I had to purge my wireless settings before everything started to work nicely.

benneque wrote:

why is there no new ebuild for knetworkmanager ?
version 9999 works well, but I can't get 20100820 compiled against KDE 4.5.1 , QT 4.7.0 ...
Though it's not possible for me to remove the wicd use flag

I use KDE 4.5.1 and I had to edit the ebuild and put it into a local overlay to make it work. Here is a patch file for you:

I suggest that you can take the list of KDE packages from it and put it into your own unmask file. Alternatively, you could find your system's package.mask file and then copy the package list from there, which is what I did to get the list of packages to unmask. Then remove the kde-testing overlay and run emerge -avDuN @world. This will likely switch you from Qt 4.7 to Qt 4.6.3. My laptop is using Qt 4.6.3, so you will want to run revdep-rebuild to make sure that this did not break binary compatibility on your system. There could be some sort of incompatibility between Qt 4.7 and knetworkmanager, but whatever is the case, unless you have a special reason to use the kde-testing overlay, you probably should stick to the ebuilds in the portage tree.

Would you post the contents of emerge --info? I am curious about whether you are running stable or testing and what architecture you are using, among other things. I have this working on a ~x86 laptop.

I'm NOT using any kde overlay on this laptop!
I've unmasked KDE 4.5.1 from portage and unmasked qt 4.7.0 from portage...

But NOW I added kde overlay 'cause knetworkmanager-9999 is NOT in portage, but it's the only available version that compiles fine.
I think it must be an issue concerning QT. But ... doesn't matter now anymore. 9999 is working fine and I can wait for a revision bump in portage

I'm NOT using any kde overlay on this laptop!
I've unmasked KDE 4.5.1 from portage and unmasked qt 4.7.0 from portage...

But NOW I added kde overlay 'cause knetworkmanager-9999 is NOT in portage, but it's the only available version that compiles fine.
I think it must be an issue concerning QT. But ... doesn't matter now anymore. 9999 is working fine and I can wait for a revision bump in portage

Thanks anyway!

Qt 4.7 is likely the problem. KDE 4.5.1 does not depend on Qt 4.7. Remove the unmask for Qt 4.7, run revdep-rebuild and try again. I think that should make knetworkmanager build. Also, make certain that you did not explicitly emerge qt. The qt package is a meta package that is masked because it is not supposed to be used on a production system.

ssteinberg wrote:

4.5.2 is on the overlay but not avaliable from any mirror yet. Just like 4.5.1.

KDE 4.5.2 has not been officially released yet. I was in #gentoo-kde yesterday and one of Gentoo's developers was testing the ebuilds.

I'm NOT using any kde overlay on this laptop!
I've unmasked KDE 4.5.1 from portage and unmasked qt 4.7.0 from portage...

But NOW I added kde overlay 'cause knetworkmanager-9999 is NOT in portage, but it's the only available version that compiles fine.
I think it must be an issue concerning QT. But ... doesn't matter now anymore. 9999 is working fine and I can wait for a revision bump in portage

Thanks anyway!

Qt 4.7 is likely the problem. KDE 4.5.1 does not depend on Qt 4.7. Remove the unmask for Qt 4.7, run revdep-rebuild and try again. I think that should make knetworkmanager build. Also, make certain that you did not explicitly emerge qt. The qt package is a meta package that is masked because it is not supposed to be used on a production system.

ssteinberg wrote:

4.5.2 is on the overlay but not avaliable from any mirror yet. Just like 4.5.1.

KDE 4.5.2 has not been officially released yet. I was in #gentoo-kde yesterday and one of Gentoo's developers was testing the ebuilds.