[Bug 239875] New: Disabling display using System Settings corrupts desktop

thoth at leapdragon.net thoth at leapdragon.net
Fri May 28 15:54:33 BST 2010


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

           Summary: Disabling display using System Settings corrupts
                    desktop
           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
remaining "on" display is corrupted.

Reproducible: Always

Steps to Reproduce:
1. Connect external monitor and boot.
2. Log into KDE.
3. Start System Settings -> Display; disable one display.


Actual Results:  
Remaining "on" display is corrupted, shows partial content from both previous
displays: approximately 80 percent is a "squished" empty desktop of the now
disabled display; approximately 20 percent is the left or right edge of the
previous content of the other display.

Expected Results:  
Disabled display goes dark and is removed from desktop area; remaining display
is unchanged.

Partial workaround: Rather than disabling displays in KDE, I use
$HOME/.xsession to call xrandr to disable display:

xrandr --output VGA --off
startkde

This makes it possible to disable the display before logging in, since
disabling the display from within KDE leads to a corrupted desktop that is
impossible to use.

Additional bug: When xrandr is called this way before startkde, calling System
Settings -> Desktop within KDE causes all screens to go dark until Xorg is
manually killed.

-- 
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