Bug 364463

Summary:	Window & menu of app & "leave" menu , show in wrong position when I set external monitor as primary
Product:	[Unmaintained] ksmserver	Reporter:	Joey Chan <joeychan.ubuntu>
Component:	ui	Assignee:	Lubos Lunak <l.lunak>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	joeychan.ubuntu, mgraesslin, nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.6.4
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	screenshot app leave menu

Description Joey Chan 2016-06-18 15:24:27 UTC

OS:  Kubuntu 16.04 with backport PPA,  KDE version 5.6.4

Device: thinkpad x230,  as secondary screen; philips 224E monitor, 1080P,  as primary screen.

 I use my external monitor as primary(programming, GIMP work, etc.),  I put my laptop on the left side and rotate it 90 degrees for docs viewing usage.  But some apps, mostly ship with KDE, their menu or slide menu show in different screen; the worse,  the "leave" menu, always show in the wrong position.

Reproducible: Always

Steps to Reproduce:
1. connect with external monitor;
2. set external monitor as primary;
3. rotate the first monitor 90 degrees;
4. screenshot app & leave menu show in wrong position;

Actual Results:  
screenshot app & its menu show in different screen;
leave menu, part of it in secondary monitor, part of it in primary monitor.

Expected Results:  
screenshot app and its menu should show in the same screen;
leave menu should show only in the primary screen;

OS: Kubuntu 16.04
KDE Plasma: 5.6.4
KDE framework: 5.22.0
Qt version: 5.5.1
Linux kernel: 4.4.0-24
OS bit: 64 bit

CPU: Intel Core i5 3210M @2.5GHz

Comment 1 Joey Chan 2016-06-18 15:26:42 UTC

Created attachment 99572 [details]
screenshot app

A photo about the bug happened from the screenshot app.

Comment 2 Joey Chan 2016-06-18 15:28:27 UTC

Created attachment 99573 [details]
leave menu

A photo about the bug happened from the leave menu.

Comment 3 Joey Chan 2016-06-18 15:30:21 UTC

I upgraded my os from Kubuntu 14.04.   Those bugs never happened before, only since I use this new one.

Comment 4 Joey Chan 2016-06-22 16:22:53 UTC

xrandr -q     output
//////////////////////
Screen 0: minimum 8 x 8, current 2688 x 1366, maximum 32767 x 32767
LVDS1 connected 768x1366+0+0 left (normal left inverted right x axis y axis) 277mm x 156mm
   1366x768      60.10*+
   1360x768      59.80    59.96  
   1280x720      60.00  
   1024x768      60.00  
   1024x576      60.00  
   960x540       60.00  
   800x600       60.32    56.25  
   864x486       60.00  
   640x480       59.94  
   720x405       60.00  
   680x384       60.00  
   640x360       60.00  
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
HDMI1 connected primary 1920x1080+768+286 (normal left inverted right x axis y axis) 476mm x 268mm
   1920x1080     60.00*+
   1680x1050     59.88  
   1280x1024     75.02    60.02  
   1440x900      74.98    59.90  
   1280x720      60.00  
   1024x768      75.08    60.00  
   800x600       75.00    60.32  
   640x480       75.00    72.81    66.67    60.00  
   720x400       70.08  
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Comment 5 Martin Flöser 2016-07-11 12:19:53 UTC

These are two different issues:
* screenshot app is a problem within Qt. Please report this one on bugreports.qt.io and paste the link here.
* the other bug is what we handle here. I'll reasign the bug to proper component.

Comment 6 Martin Flöser 2016-07-11 12:25:29 UTC

I just learned that there is already a bug report for the issue exposed in the screenshot application: https://bugreports.qt.io/browse/QTBUG-53813

Comment 7 Nate Graham 2020-01-31 18:34:57 UTC

This was fixed a while ago.

Comment 8 Nate Graham 2020-01-31 18:36:18 UTC


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