https://bugs.kde.org/show_bug.cgi?id=408775
--- Comment #22 from tcanabr...@kde.org --- On Mon, Jun 17, 2019 at 2:59 PM Bernd Steinhauser <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=408775 > > --- Comment #21 from Bernd Steinhauser <li...@bernd-steinhauser.de> --- > Sorry, can't do that, I'm not running team viewer. > > I did another test though. I ran konsole inside of urxvt and tried a few > things. > On normal splitting, there are no error messages, but as soon as I mix > vertical > and horizontal splitting, I get about 100 of these messages: > qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 5129, > resource > id: 35651610, major code: 130 (Unknown), minor code: 3 > > That gave me an idea that it might actually be related to kwin or how > konsole > interacts with kwin (since iirc kwin handles the xcb connections). > So as a wild guess, I tried it with the compositor disabled and then it > worked! > So to sum up: > compositor activated -> bugged > compositor deactivated -> works > > That's both really weird and really anoying: I run compositor and I have no issue. I'll forward this to the kwin guys as I really have no idea. Thank you very much for the tests, I know it's frustrating to have a bug and not be able to deal with it. without the compositor, do you like how konsole behaves? Weird, isn't it? > Doesn't matter which backend for the compositor is used, I tried all of > them > (normally, I'm using the OpenGL 3.1 backend). > Also played around with the desktop effects and other compositor-related > stuff, > but couldn't find any further influence. > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
