[systemsettings] [Bug 339084] New: Logoff then Logon causes dual monitor setup to function incorrectly. Fix is to restart.

G garethic at exemail.com.au
Sun Sep 14 23:13:45 BST 2014


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

            Bug ID: 339084
           Summary: Logoff then Logon causes dual monitor setup to
                    function incorrectly. Fix is to restart.
           Product: systemsettings
           Version: unspecified
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: garethic at exemail.com.au

This is a problem with my display settings, that occurs after a logoff/logon,
but not with a restart.
I have a laptop with a 1366x768 display with a 1920x1080 monitor attached via
hdmi, set to be viewed side by side, with the laptop screen as the primary. 
After a logoff/logon the hdmi screen becomes the primary with the display
mirrored onto the laptop screen as if it were a 1920x1080 screen, with the
origin of both being the top left corner. 
Attempting to change the any of the settings in display settings has no result,
eg screen placement or display resolutions.
If I restart, the 2 screens display as I have set them. 
My laptop has a nVidia Optimus system, I'm running Bumblebee to manage it which
otherwise works beautifully. In Other Drivers I installed the latest nVidia
driver. 



Reproducible: Always

Steps to Reproduce:
1. Setup as described above
2. Logoff, logon. 
3. Restart to fix problem

Actual Results:  
It happens every time (twice).


My laptop has a nVidia Optimus system, I'm running Bumblebee to manage it which
otherwise works beautifully. In Other Drivers I installed the latest nVidia
driver. 

BTW, I'm still confused about bug reporting. The 'automated' system I sometimes
(very rarely! That's a good thing!) get when a program crashes asks me to
download debugging symbols but never succeeds in doing so. Ever. So the crash
never gets reported. Are you aware of that?

-- 
You are receiving this mail because:
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list