On Thu, 4 Dec 2014 17:02, Stefan Kunze
I guess that should not happen ;)
Environment: OpenSUSE 13.1 with KDE:Current Repo activated and latest patches applied (although today's patches were only updated after the issue happened) Dualscreensetup (no clone)
I played a game of Frozen Bubble today in Fullscreen . After I closed the application my KDE Screensetup was changed.
The output of both displays were the same (unified) and after I broke the unity in the KDE Systemsettings both screens were switched .
The config did not work correctly as I could not change the sequence of the screens ) it took me 15min (patching, logoff and finally restart) . After the restart the screens were still switched but at least systemsettings were back to halfway normal . I still needed to make 1 Display turn by 90° clockwise and back to finally get systemsettings to recognize the displays correctly again)
My guess its a bug, as no application should be allowed to have such consequences, but which info would be needed for a report?
Looking into the sources of Frozen Bubble, all it does is a call to x11. Xrandr if I read the things right. Nothing mystic here. IMHO, the fuck-up happens eiter on the savestate prior switch, or on switchback call. Either the "saved state" (prior to the set res call from Frozen Bubble) can not be restored by xrandr alone due to KDE interna, or the "saved state" info is not complete enough. e.g. only "Main Monitor" state is saved, instead of all state info. I'm lacking the setup to do the proofing needed to make sure what the true cause is. AFAICT, "Full Screen" on a multi screen setup is not really as well defined as for a single screen setup. What should "Full Screen" be? "Full Virtual Screen", or "Full Main Screen"? This ambivalence is the root cause, imho. - Yamaban. -- Never attribute to evil where stupidy is sufficent.