krandr-related display Settings (Size & Refresh Rate) are lost after a
contains an experiemental/contributed patch I'd like to try out.
Here's some builds to test out:
Rats, testing the F-13 build doesn't seem to work for me.
I've tried the rawhide build and it doesn't work for me either.
kdebase-workspace-4.5.2-3.fc14 has been submitted as an update for Fedora 14.
kdebase-workspace-4.5.2-3.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kdebase-workspace'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/kdebase-workspace-4.5.2-3.fc14
kdebase-workspace-4.5.2-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 622891 has been marked as a duplicate of this bug. ***
This bug still occurs with kdebase-workspace-4.5.2-3.fc14.x86_64 on my Dell Latitude E6500 with an Intel video card. This notebook is situated in a docking station with 2 DVI monitors attached. Every time kdm starts both DVI monitors show the same picture (clone mode). When I log into KDE I always have to reconfigure the monitor layout.
The file ~/.kde/share/config/kcmrandrrc has this content:
StartupCommands=xrandr --output "HDMI1" --pos 0x0 --mode 1280x1024 --refresh 60.0197\nxrandr --output "HDMI2" --pos 0x0 --mode 1280x1024 --refresh 60.0197
The xrandr command mentioned in this file looks suspicious to me as it uses "--pos 0x0" two times. I want the second monitor to be at pos 1280x0 (as is mentioned in the Screen_0_Output_HDMI2 section.
I'm going to reopen this one, based on comment #8 and on the fact that the upstream bug is also in reopened state. It looks like this longstanding issue is still open. :-(
Retargeting to F18 because Rawhide has kscreen.
*** Bug 699024 has been marked as a duplicate of this bug. ***
I can confirm, that this still happen on F18.
Can also confirm that this is happening on f18
*** Bug 913712 has been marked as a duplicate of this bug. ***
*** Bug 915522 has been marked as a duplicate of this bug. ***
*** Bug 952820 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
krandr is known to have serious defects, and it's functionality was replaced by kscreen upstream. I'd recommend you try kscreen instead.