Bug 353590 - After changing screen orientation to 90 degrees it can't be changed to normal
Summary: After changing screen orientation to 90 degrees it can't be changed to normal
Status: RESOLVED FIXED
Alias: None
Product: KScreen
Classification: Plasma
Component: kcm (show other bugs)
Version: 5.4.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Vrátil
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-06 06:43 UTC by tguen
Modified: 2016-10-16 22:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tguen 2015-10-06 06:43:29 UTC
In the 'display and monitor' section I changed my screen orientation to 90 degrees clockwise. After clicking apply my screen rotated 90 degrees. I changed orientation back to normal, but when I click apply it just sets orientation back to 90 degrees and doesn't rotate my screen. I can switch between 90 degrees clockwise and counterclockwise, but won't change to either normal or upside down. 

I had to switch from HDMI to Displayport to fix the problem. I tried again with DP and the same thing happened. I had to switch to DVI to fix it and I'm not about to try again because I don't have another port to switch to. I am very upset about this. To say this is a serious problem is an understatement.

Reproducible: Always
Comment 1 tguen 2015-11-02 10:09:48 UTC
Wow, almost a whole month and not a single reply. I guess you're all busy with the massive amount of other bugs plaguing Plasma atm...

Anyway, I figured out I can fix this by changing the screen orientation in Nvidia X Server Setings. I'd guess this is only a problem for Nvidia users, but not a problem with the driver since the setting can be changed in System Settings but not reverted.
Comment 2 Sebastian Kügler 2016-10-16 22:21:48 UTC
Sorry for the long turnaround time.

Could you check if this works with Plasma 5.8? We've had a problem updating the screen size in this scenario, which leads to your bug.
Comment 3 tguen 2016-10-16 22:39:35 UTC
Yes, it seems to be fixed in 5.8.