Bug 232500 - When useing two monitors, monitor positions are not kept / stored and went lost after re-login or reboot
Summary: When useing two monitors, monitor positions are not kept / stored and went lo...
Status: RESOLVED DUPLICATE of bug 183143
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Gustavo Pichorim Boiko
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-28 20:14 UTC by webersinke
Modified: 2010-04-22 16:53 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description webersinke 2010-03-28 20:14:29 UTC 
Version:            (using KDE 4.3.5)
OS:                Linux
Installed from:    openSUSE RPMs

Using an ATI-graphics card, my first (analog-VGA) Monitor is always located right to the 2nd monitor (DVI-Interface). I can set up the monitors in their proper location with system settings, however, these settings are not stored permanently. Each time I login as a different user or reboot the system, I have to reassign the monitor settings.

For me this is a poor situation as I have to user a analog KVM-switch for my main monitor for all of my computers and attached the DVI-Interface to one computer as a second one.

Can one please help?

Thank you very much for support

Regards

Rainer
Comment 1 webersinke 2010-03-28 21:28:31 UTC 
Hi all,

I found a workaround: I booted into runmode 3 and manually edited xorg.conf - in this case I replaced all "LeftOf" with "RightOf" and restarted in runmode 5... Now it works like a charme.

Anyhow, I wonder why system config cannot replace this. Maybe it works like designed. Anyhow: For me you can close this incident.

Regards

Rainer
Comment 2 Hans-Rudi Denzler 2010-03-29 14:54:47 UTC 
/usr/sbin/sax2
Comment 3 Christoph Feck 2010-04-22 16:53:04 UTC 

*** This bug has been marked as a duplicate of bug 183143 ***