Bug 369178 - Yakuake does not properly scale to the width of a monitor if it's rotated 90 degrees
Summary: Yakuake does not properly scale to the width of a monitor if it's rotated 90 ...
Status: RESOLVED DUPLICATE of bug 389448
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 3.0.2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL: http://imgur.com/a/vYJ5I
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-22 00:24 UTC by stedlev
Modified: 2020-02-29 23:05 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stedlev 2016-09-22 00:24:19 UTC
In KDE System Settings under Display and Monitor, you can set a monitor to be rotated 90 degrees. When you rotate a monitor, the width of yakuake does not take the proper width of the screen on the rotated monitor. I have width set to 90% for Yakuake, when on my horizontal monitor, it works perfectly fine. When on the vertical monitor, it only takes up a small portion of the screen. If it matters, I have it rotated 90 degrees counterclockwise.

Reproducible: Always

Steps to Reproduce:
1. Rotate a monitor 90 degrees counter clockwise, change settings in Display Configuration to reflect the physical monitor changes
2. Open Yakuake on the rotated display

Actual Results:  
The Yakuake window does not take up 90% of the screen, more like a quarter of it. 

Expected Results:  
The Yakuake window should take up 90% of the width of the screen.
Comment 1 stedlev 2016-10-03 23:16:58 UTC
It seems to be fixed, but I changed Display Configuration -> Scale Display to 1.0 and it was set higher before when the problem was happening. I recently upgraded to 4k and I have been adjusting things to make things work better. Still on Yakuake 3.0.2, though I did upgrade some other KDE libraries in the last update to the system.
Comment 2 Andrew Hou 2020-02-29 23:05:50 UTC

*** This bug has been marked as a duplicate of bug 389448 ***