Armelius Cameron wrote, On 04/23/2011 10:57 AM:
On Saturday, April 23, 2011 02:05:09 am Gene Smith wrote:
> Note: this problem is covered in kde bug
>
https://bugs.kde.org/show_bug.cgi?id=183143 which is classified as
> "resolved as fixed" but *many* disagree.
Thanks for pointing out this bug. I have been having exactly the same problem
as you have and wondering about it too. I have F14 fully updated and it still
having the problem. Fortunately this one is on my desktop where I only rarely
log off, so that somewhat mitigates the annoyance. But I am not sure if I can
live with this bug on the laptop where I move it around a lot and connect it
to different external displays at home, work, etc.
AC
Hi AC,
Right above my bug posting there is a work-around that sounds promising.
I received this additional information from the person who posting the
workaround:
<quote>
I found a workaround for this problem.
You should edit .kde/share/config/krandrrc by hand.
The bottom line is that the StartupCommands= line
is currently brain dead. Try to use a single xrandr call
with multiple --output options there.
More details here:
https://bugzilla.redhat.com/show_bug.cgi?id=699024
Let me know if you have more questions, or send me the broken
StartupCommands= line, so that I can fix it for you.
<end quote>
I also wonder about the startupconfig file in the same dir that contains
the same xrandr string and if it should be changed too. Unfortunately I
can't try anything now since the system with 2 monitors is at another
location.
I have cc's the workaround poster who has generously offered to help
resolve the issue.
-gene