Bug 411308 - Application Dashboard not opens on primary display
Summary: Application Dashboard not opens on primary display
Status: REPORTED
Alias: None
Product: kdeplasma-addons
Classification: Plasma
Component: Application Dashboard (show other bugs)
Version: 5.15.5
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Eike Hein
URL:
Keywords:
: 419164 469227 473932 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-08-26 08:20 UTC by sedrubal
Modified: 2023-08-30 20:29 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
xprop of the application dashboard (54.56 KB, text/plain)
2019-08-26 10:08 UTC, sedrubal
Details
xrandr -q (19.93 KB, text/plain)
2019-08-26 10:08 UTC, sedrubal
Details
xwininfo if the application dashboard (703 bytes, text/plain)
2019-08-26 10:09 UTC, sedrubal
Details
Screenshot of the current setup (2.26 MB, image/png)
2019-08-26 10:10 UTC, sedrubal
Details
Screenshot of the current setup without the application dashboard (2.03 MB, image/png)
2019-08-26 10:11 UTC, sedrubal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sedrubal 2019-08-26 08:20:10 UTC
SUMMARY

The Application Dashboard always opens on the most left and most upper screen / display and not on the primary display or that display, where the cursor is currently placed.


STEPS TO REPRODUCE
1. Connect an external monitor
2. Align it above or left of the primary display
3. Configure plasmashell to use the application dashboard instead of the application launcher
4. Move the cursor to the primary screen and focus a window there
5. Hit the Super key / Windows key or Alt+F1 or click on the dashboard launch icon

OBSERVED RESULT
It opens on the secondary most left / most upper display.

EXPECTED RESULT
It should open on the primary screen or on that screen, where the cursor is currently placed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 30 - Kernel 5.2.9-200.fc30.x86_64
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4
Comment 1 David Edmundson 2019-08-26 09:15:12 UTC
Please include a screenshot of your setup (with the dash not running)

and output of xrandr -q
Comment 2 sedrubal 2019-08-26 10:08:03 UTC
Created attachment 122362 [details]
xprop of the application dashboard
Comment 3 sedrubal 2019-08-26 10:08:23 UTC
Created attachment 122363 [details]
xrandr -q
Comment 4 sedrubal 2019-08-26 10:09:04 UTC
Created attachment 122364 [details]
xwininfo if the application dashboard
Comment 5 sedrubal 2019-08-26 10:10:16 UTC
Created attachment 122365 [details]
Screenshot of the current setup

The primary monitor is below the secondary. Its resolution is 1920x1080. The second monitor has a higher resolution, but this should not change the behaviour.
Comment 6 sedrubal 2019-08-26 10:11:22 UTC
Created attachment 122366 [details]
Screenshot of the current setup without the application dashboard
Comment 7 Bug Janitor Service 2019-09-10 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Christoph Feck 2019-09-16 21:17:39 UTC
New information was added with comment #6; changing status for inspection.
Comment 9 tomashnyk 2022-09-27 18:14:32 UTC
*** Bug 419164 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2023-08-30 19:57:43 UTC
*** Bug 473932 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2023-08-30 20:29:49 UTC
*** Bug 469227 has been marked as a duplicate of this bug. ***