Summary: | Klipper causes a BadWindow error when selecting a large text in a GTK text editor | ||
---|---|---|---|
Product: | [Unmaintained] klipper | Reporter: | Patrick <mail> |
Component: | plasma-widget | Assignee: | Martin Flöser <mgraesslin> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | cavendish.qi |
Priority: | NOR | ||
Version First Reported In: | 5.7.5 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick
2016-09-28 19:04:56 UTC
Klipper doesn't interact with the clipboard directly. It only uses Qt. Can you try whether the problem can also be reproduced by copying the content into any other Qt application? I can reproduce the problem without klipper by pasting a large text into a Qt5 application (Qt4 seems to work fine). But with klipper enabled the problem occurs immediately after selecting the text. ok, thanks for testing. That means the problem is within Qt's clipboard implementation. Klipper just exposes it more directly. I suggest to report this issue to both the GTK developers as GTK should not crash on a BadWindow error on bugs.gnome.org and the Qt problem to Qt developers on bugreports.qt.io. On our side there is unfortunately nothing we can do about it as klipper only uses Qt's clipboard abstraction. I have seen https://bugreports.qt.io/browse/QTBUG-56595 , QXcbConnection::getTimestamp() returns old timestamp . Is there any way to get some debug output from klipper? Searched a bit in https://github.com/KDE/plasma-workspace/tree/master/klipper , found sth about klipper_debug.h and klipper_debug.cpp in source, how should I do to enable it? Thanks. No need to reply my previous comment. Got some progress, more in qt jira. |