Bug 363440 - Detached Drop-down list in dual-monitor
Summary: Detached Drop-down list in dual-monitor
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.6.4
Platform: Kubuntu Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-23 16:28 UTC by Valdas
Modified: 2016-09-06 17:53 UTC (History)
5 users (show)

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


Attachments
Screenshot of detached drop-down list (167.75 KB, image/png)
2016-05-23 16:30 UTC, Valdas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Valdas 2016-05-23 16:28:51 UTC
I have two monitor setup:
 - big primary;
 - smaller secondary on the left.

 When application's window resides in primary monitor and I click on Drop-down in application then Drop-down List is shown in secondary monitor (see screenshot; big black band on left-lower part is inaccessible part of smaller monitor).
 In my system I have installed NVidia v361.42.
 I experience this bug also in v5.5.5.

Reproducible: Always
Comment 1 Valdas 2016-05-23 16:30:07 UTC
Created attachment 99145 [details]
Screenshot of detached drop-down list
Comment 2 Kai Uwe Broulik 2016-05-25 12:27:38 UTC
Looks like a Qt bug to me, I have a similar issue with context menus; if I open a context menu on the right monitor so it touches the edge of the screen, all submenus will open on the left monitor instead.
Comment 3 Bernhard Scheirle 2016-07-06 05:51:45 UTC
Just for reference:
The bug with the misplaced context menus can be found at: https://bugreports.qt.io/browse/QTBUG-53813
Comment 4 Valdas 2016-08-16 09:29:38 UTC
Seems there is NVIDIA involved: when I switch GPU to Intel (using NVIDIA X server settings then issue is gone. Also is gone that nasty diagonal tearing and laggy UI update.
Comment 5 Dan Dascalescu 2016-09-03 07:44:39 UTC
This should be confirmed - I have the same issue, see #367477.
Comment 6 Dan Dascalescu 2016-09-06 17:53:59 UTC
I got an email that the status of this bug changed to "RESOLVED UPSTREAM".

However, I can't see here in Bugzilla who changed the status, or any other information about the solution.