Bug 419942 - In vertical aligned dualscreen mode terminal drops down only on top display, not bottom
Summary: In vertical aligned dualscreen mode terminal drops down only on top display, ...
Status: RESOLVED FIXED
Alias: None
Product: yakuake
Classification: Applications
Component: general (show other bugs)
Version: 3.0.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-11 06:55 UTC by Sam Potekhin
Modified: 2021-01-11 07:01 UTC (History)
1 user (show)

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


Attachments
xorg.conf and kscreen configuration files (102.83 KB, application/gzip)
2020-04-11 06:55 UTC, Sam Potekhin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sam Potekhin 2020-04-11 06:55:11 UTC
Created attachment 127441 [details]
xorg.conf and kscreen configuration files

SUMMARY
Two monitors configured with vertical alignment. Main display on bottom. Secondary display on top.

STEPS TO REPRODUCE
1. Configure X11 to like attached xorg.conf example. And/or kscreen like attached config/screenshots.
2. Move mouse cursor to upper monitor, call yakuake shortcut. You see yakuake appears.
3. Move mouse cursor to downer monitor, call yakuake shortcut. Yakuake doesn't appears.

OBSERVED RESULT
On top display yakuake appears, on bottom doesn't.

EXPECTED RESULT
Yakuake appears on any display, where mouse cursor stays.

SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: Arch x64, KDE Plasma 5.18.4
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.14.2

ADDITIONAL INFORMATION
When using horizontal display alignment - yakuake appears on any of two displays where mouse cursor stays. When I setup vertical alignment - yakuake is not appears on bottom display. Another app that using top border of screen to appear (krunner) - works correctly on both displays with vertical alignment.
Comment 1 Riccardo Robecchi 2021-01-09 19:42:24 UTC
Is the issue still there? I just tried it and it works as expected.
Comment 2 Sam Potekhin 2021-01-11 06:59:50 UTC
This issue was resolved in one of updates. For now described configuration works correctly