Bug 359214 - Wallpaper on second monitor overlaps first monitor and does not rotate
Summary: Wallpaper on second monitor overlaps first monitor and does not rotate
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Image & Slideshow wallpaper plugins (show other bugs)
Version: 5.5.3
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-10 07:36 UTC by Ovidiu-Florin BOGDAN
Modified: 2018-10-31 19:38 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot of the bug in action (2.85 MB, image/png)
2016-02-10 07:36 UTC, Ovidiu-Florin BOGDAN 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ovidiu-Florin BOGDAN 2016-02-10 07:36:01 UTC 
Setup: 2 monitors. The left one is set in vertical position (90 degrees clockwise).
Resolutions:
Monitor 1 (left): H 1050, V 1680
Monitor 2 (right): H 1920 V 1080.

The resolutions and position are set from the system settings Display KCM.

I've attached a screenshot with the behaviour.

However, If I click on the right screen, then the overlapping part disappears. But if I click on the left screen, the overlapping part appears again.

Reproducible: Always
Comment 1 Ovidiu-Florin BOGDAN 2016-02-10 07:36:29 UTC 
Created attachment 97128 [details]
Screenshot of the bug in action
Comment 2 Ovidiu-Florin BOGDAN 2016-02-11 10:33:39 UTC 
Upon a reboot the wallpaper is centred on the left screen. So this happens only when setting the screen rotation.
Comment 3 Aleix Pol 2016-02-13 01:52:40 UTC 
You mean that on reboot it works ok?
Comment 4 Alexander Mentyu 2018-02-06 14:24:50 UTC 
@Ovidiu-Florin BOGDAN Could you reproduce this bug after updates?
Comment 5 David Edmundson 2018-10-31 02:25:16 UTC 
as per comment in feb, marking as needsinfo
Comment 6 Ovidiu-Florin BOGDAN 2018-10-31 19:38:26 UTC 
Sorry for the late reply, I didn't get an email until now about this bug.

I cannot reproduce this anymore.