https://bugs.kde.org/show_bug.cgi?id=359100
Andrew Crouthamel changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=359100
Andrew Crouthamel changed:
What|Removed |Added
Keywords||triaged
--- Comment #16 from Andrew Croutha
https://bugs.kde.org/show_bug.cgi?id=359100
Martin Gräßlin changed:
What|Removed |Added
Status|UNCONFIRMED |NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=359100
Martin Gräßlin changed:
What|Removed |Added
Component|general |compositing
--- Comment #14 from Martin Gräßli
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #13 from Martin Gräßlin ---
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.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #12 from Bruno Coudoin ---
I just tried Unity and by default this is a wide layout and it works fine.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #11 from Thomas Lübking ---
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
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #10 from Bruno Coudoin ---
Excellent, the xrandr does the trick I can use KDE again.
No success changing the wineffects.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #9 from Thomas Lübking ---
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 ha
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #8 from Bruno Coudoin ---
Created attachment 97096
--> https://bugs.kde.org/attachment.cgi?id=97096&action=edit
xrandr
And the xrandr both with external screens.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #7 from Bruno Coudoin ---
Created attachment 97095
--> https://bugs.kde.org/attachment.cgi?id=97095&action=edit
glxinfo
Here is the glxinfo -l
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #6 from Thomas Lübking ---
ok, outputs of "xrandr -q" with dualscreen setup and "glxinfo -l" as well,
please.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #5 from Bruno Coudoin ---
Created attachment 97082
--> https://bugs.kde.org/attachment.cgi?id=97082&action=edit
support information
Attached is the support information. And yes disabling the compositor makes
dual screen working.
--
You
https://bugs.kde.org/show_bug.cgi?id=359100
--- Comment #4 from Thomas Lübking ---
please attach the output of "qdbus org.kde.KWin /KWin supportInformation"
Do things revive if you suspend the compositor (SHIFT+Alt+F12)?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=359100
David Edmundson changed:
What|Removed |Added
Product|plasmashell |kwin
Target Milestone|1.0
15 matches
Mail list logo
