Your message dated Wed, 12 Aug 2009 09:14:28 -0700
with message-id <20090812161428.ga2...@oja.no>
and subject line Oops
has caused the Debian Bug report #540883,
regarding QClipboard can no longer set selection
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
540883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqtgui4
Version: 4:4.5.2-1
When QClipboard::setText(QString, QClipboard::Selection) is called
"late" (meaning at least from an event handler, but I haven't narrowed
it down completely) retrieving the selection in another client doesn't
work. More particularly, ownership of it gets set, but other clients
cannot retrieve the data.
I've attached a small program which demonstrates the problem. After
launching, a window containing a button will show up. Before pressing
that button, retrieving the primary selection via "xsel -v -v -v -v"
displays something like:
xsel: Window id: 0x5e00001 (unmapped)
xsel: Timestamp: 3983411207
xsel: Maximum request size: 4000 bytes
xsel: Got window property: requestor 0x5e00001, property 0x321, target 0xf4
UTF8_STRING, length 12 bytes
Hello world!
That text was set by calling QClipboard::setText in main. After
pressing the button, it changes to:
xsel: Window id: 0x5e00001 (unmapped)
xsel: Timestamp: 3983455616
xsel: Maximum request size: 4000 bytes
xsel: Conversion refused
xsel: Conversion refused
This time, the selection was set by calling QClipboard::setText in a
slot attached to the button's clicked() signal.
I've traced through the execution of the event handler as well as I
can in gdb. At line 1020 of qclipboard_x11.cpp, something very odd
happens in the "bad" case that I cannot explain. It suddenly jumps
down past all the bits which actually put the data in the event to
line 1109, sending an empty reply to the reqesting client.
This behaviour is new. In previous versions of the qt package, other
clients were able to retrieve the selection as expected in all
circumstances.
Random bugreport-y stuff:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libqtgui4 depends on:
ii fontconfig 2.6.0-4 generic font configuration library
ii libaudio2 1.9.2-1 Network Audio System - shared libr
ii libc6 2.9-23 GNU C Library: Shared libraries
ii libfontconfig1 2.6.0-4 generic font configuration library
ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib
ii libgcc1 1:4.4.1-1 GCC support library
ii libglib2.0-0 2.20.1-2 The GLib library of C routines
ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libmng1 1.0.9-1 Multiple-image Network Graphics li
ii libpng12-0 1.2.38-1 PNG library - runtime
ii libqtcore4 4:4.5.2-1 Qt 4 core module
ii libsm6 2:1.1.0-2 X11 Session Management library
ii libstdc++6 4.4.1-1 The GNU Standard C++ Library v3
ii libtiff4 3.8.2-13 Tag Image File Format (TIFF) libra
ii libx11-6 2:1.2.2-1 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxrender1 1:0.9.4-2 X Rendering Extension client libra
ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime
Versions of packages libqtgui4 recommends:
ii qt4-qtconfig 4:4.5.2-1 Qt 4 configuration tool
--
Robert Macomber
xby...@rojoma.com
cliptest.tar.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
I still have no idea why this problem was Qt-only, or why it only
appeared with the latest version of Qt, but rebooting fixed it (merely
restarting X wasn't enough). I'm closing this bug report since it's
not actually a bug.
--
Robert Macomber
xby...@rojoma.com
--- End Message ---
