Bug 359100

Summary: desktop freeze when plug-in an external monitor
Product: [Plasma] kwin Reporter: Bruno Coudoin <bruno.coudoin>
Component: compositingAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: major CC: kde, plasma-bugs-null
Priority: NOR Keywords: triaged
Version First Reported In: 5.4.3   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: support information
glxinfo
xrandr

Description Bruno Coudoin 2016-02-07 12:36:27 UTC
Dual screen does not work with a Dell XPS 13 2015.

Reproducible: Always

Steps to Reproduce:
1. Plug an external monitor on the mini DV connector (Using a mini DV to DVI/HDMI/VGA converter ends up in the same result)

Actual Results:  
The external monitor shows the desktop background and the mouse can be moved in it 
Clicks are not taken in account whatever the screen
Keyboards event are not played either
When the dual screen is disconnected the lost keyboard events are played and the laptop screen works fine.

Expected Results:  
Keyboard and mouve events should be accepted in dual screen.

Hardware is a Dell XPS13 2015
Kubuntu 15.10 with plasma 5.4.3 and framework 5.15.0
Dual screen works fine with Unity.
Comment 1 David Edmundson 2016-02-07 22:28:52 UTC
Can you move windows or is it just interacting with the panels that's frozen?
Comment 2 Bruno Coudoin 2016-02-07 23:15:23 UTC
Can't move windows. Tested title bar click, alt+click, none works.
Comment 3 David Edmundson 2016-02-07 23:17:43 UTC
ok. Moving to kwin then.
Comment 4 Thomas Lübking 2016-02-07 23:22:42 UTC
please attach the output of "qdbus org.kde.KWin /KWin supportInformation"

Do things revive if you suspend the compositor (SHIFT+Alt+F12)?
Comment 5 Bruno Coudoin 2016-02-08 10:02:20 UTC
Created attachment 97082 [details]
support information

Attached is the support information. And yes disabling the compositor makes dual screen working.
Comment 6 Thomas Lübking 2016-02-08 10:33:49 UTC
ok, outputs of "xrandr -q" with dualscreen setup and "glxinfo -l" as well, please.
Comment 7 Bruno Coudoin 2016-02-08 22:48:20 UTC
Created attachment 97095 [details]
glxinfo

Here is the glxinfo -l
Comment 8 Bruno Coudoin 2016-02-08 22:49:37 UTC
Created attachment 97096 [details]
xrandr

And the xrandr both with external screens.
Comment 9 Thomas Lübking 2016-02-08 23:02:17 UTC
Thanks. Does it also happen if you arrange the screens vertically?
    xrandr --output DP1 --below eDP1

(In case not, try to disable bur and contrast effect in "kcmshell5 kwineffects" and check whether it still happens w/ the original layout)
Comment 10 Bruno Coudoin 2016-02-08 23:19:18 UTC
Excellent, the xrandr does the trick I can use KDE again.
No success changing the wineffects.
Comment 11 Thomas Lübking 2016-02-08 23:32:12 UTC
You're running into some weird GL limitation.
The driver announces:
   GL_MAX_RECTANGLE_TEXTURE_SIZE_NV = 4096
and your original width exceeds that, what apparently is the problem.

It's "weird" because you should not be operating on  GL_ARB_texture_rectangle but on GL_ARB_texture_non_power_of_two where GL_MAX_TEXTURE_SIZE (8192) should apply (and we warn you when trying to exceed that, because things could turn slow)

Assuming that GL_ARB_texture_rectangle is considered relevant by the driver the question is
a) where we hit the limit (it's apparently not the usual suspects - any window of that size?)
b) why that texture isn't simply black, but the screen simply "freezes"

Does the wide layout work in unity or is it more quadratic or intersecting there?
Comment 12 Bruno Coudoin 2016-02-08 23:38:53 UTC
I just tried Unity and by default this is a wide layout and it works fine.
Comment 13 Martin Flöser 2016-02-09 07:55:30 UTC
As it's an Ubuntu 15.10 it means it uses glamor which might be a key in the question. My guess would be that the overlay window exceeds the texture size in this setup with glamor.
Comment 14 Martin Flöser 2016-08-29 08:15:08 UTC
To verify my idea from comment #13: could you try switching to xrender and see whether that works?
Comment 15 Martin Flöser 2016-11-02 13:50:12 UTC
waiting for xrender test case.
Comment 16 Andrew Crouthamel 2018-09-26 22:25:41 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 set the bug status 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 17 Andrew Crouthamel 2018-10-27 02:53:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!