Bug 377019 - [copyq-git, qt5 build] why menu is soo high?
Summary: [copyq-git, qt5 build] why menu is soo high?
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray widget (other bugs)
Version First Reported In: master
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL: https://github.com/hluk/CopyQ/issues/639
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-28 14:13 UTC by fademind
Modified: 2017-03-03 00:33 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fademind 2017-02-28 14:13:56 UTC
Developer of copyq clipboard manager asked me about submit new bug directly to KDE Developers.

ISSUE

Context Menu from CopyQ Tray Icon in Plasma 5 DE is showed higher than should be:
https://cloud.githubusercontent.com/assets/9846948/22987121/0ae9feaa-f3ae-11e6-89e3-3f5edc98b3ae.png

Please read full ISSUE report from here: https://github.com/hluk/CopyQ/issues/639

DE: Plasma 5.9.2
KF5: 5.31.0
Distro: Manjaro Linux KDE x86_64
App: copyq-git 1:2.9.0.r112.g06865d5f-1
Comment 1 fademind 2017-02-28 14:17:57 UTC
AFAIK the menu works fine in other desktop environments.
Comment 2 David Edmundson 2017-02-28 15:50:58 UTC
can you test something:

close copyq

unset 
XDG_CURRENT_DESKTOP
KDE_FULL_SESSION

and see if it still happens?

Also ideally can you get a log from running dbus-monitor and then opening the menu.
Comment 3 Kai Uwe Broulik 2017-03-01 11:03:57 UTC
Most likely a scaling issue, e.g. Plasma using 1x scaling and the app being 2x scaled which results in a mismatch and as such in a misplaced menu.
Comment 4 David Edmundson 2017-03-03 00:33:54 UTC
Just read upstream, they're changing the number of items in repsonse to aboutToShow; they're sending the new data after we've resized the popups.

They claim it's us with the bug, I'm not very convinced. If they want to send us a bustle log, we can see either way.

Anyway, they've worked round it upstream so that the we get the DBus reply from aboutToShow before they signal layoutChanged. Seems to work.