[Bug 239873] New: Dual head setting ignored on login

thoth at leapdragon.net thoth at leapdragon.net
Fri May 28 15:48:57 BST 2010


https://bugs.kde.org/show_bug.cgi?id=239873

           Summary: Dual head setting ignored on login
           Product: kde
           Version: unspecified
          Platform: Fedora RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: dualhead
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: thoth at leapdragon.net


Version:           unspecified (using KDE 4.4.3) 
OS:                Linux

When an external monitor is connected to a Thinkpad T60 and the user uses
System Settings -> Display to disable either internal or external monitor, the
setting is not saved across logout/relogin.

Reproducible: Always

Steps to Reproduce:
1. Connect external monitor and boot laptop.
2. Log into KDE.
3. Open System Settings -> Display (both displays detected and active).
4. Disable either display; save changes.
5. Log out and log back in.

Actual Results:  
Sometimes: both displays on again after login, despite changes.
Other times: one display "off", but mouse still movable to "dark" display and
listed desktop width the size of both displays, not single display.

Expected Results:  
Disabled display remains dark; mouse not able to move "onto" that display;
desktop width the size of single remaining display.

Current workaround: start KDE from $HOME/.xsession, which contains calls to
xrandr. For example:

xrandr --output VGA --off
startkde

When this is done, KDE correctly ignores the disable display and does not
include the display in desktop width.

ADDITIONAL BUG: When this workaround is used, starting System Settings ->
Display in the KDE session will cause ALL SCREENS to go permanently dark until
Xorg is manually killed/restarted from a virtual console.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list