[ wxwindows-Bugs-1531348 ] DnD locks up X11 mouse completely

[SourceForge.net]

Bugs item #1531348, was opened at 2006-07-30 21:12
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1531348&group_id=9863

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: wxGTK specific
Group: Platform specific
Status: Open
Resolution: None
Priority: 5
Submitted By: Milan Babuskov (mbabuskov)
Assigned to: Nobody/Anonymous (nobody)
Summary: DnD locks up X11 mouse completely

Initial Comment:
It happens from time to time. When I drag and drop item
(from a tree ctrl for example) for a quite short period
(it isn't a real DnD, I just happen to press mouse down
a little longer while clicking), the entire X windows
system locks up, i.e. no window is able to receive
mouse events.

Keyboard keeps working fine, I can for example alt+tab
to terminal and ctrl+c kill the wx application that
caused the lock, after which everything goes back to
normal.

This doesn't happen often and it is not easy to
reproduce it. I tried and sometimes I need 100 DnD
tries to make it lock. But it does happen, and at that
point user loses all unsaved data in the application.

Here's the backtrace (it's for wxGTK 2.6.2, but I don't
see that the DnD code changed much since).

#0  0xe8b7afe1 in ?? ()
#1  0x0827c4fb in gtk_dnd_window_configure_callback
(source=0xbf9a6a90)
    at ./src/gtk/dnd.cpp:732
#2  0xb7dc10ce in gtk_marshal_VOID__UINT_STRING ()
   from /usr/lib/libgtk-x11-2.0.so.0
#3  0xb7b63cb6 in g_closure_invoke () from
/usr/lib/libgobject-2.0.so.0
#4  0xb7b7548f in g_signal_emit_by_name () from
/usr/lib/libgobject-2.0.so.0
#5  0xb7b7433a in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#6  0xb7b747e6 in g_signal_emit () from
/usr/lib/libgobject-2.0.so.0
#7  0xb7eb08a7 in gtk_widget_send_expose () from
/usr/lib/libgtk-x11-2.0.so.0
#8  0xb7dbeaca in gtk_main_do_event () from
/usr/lib/libgtk-x11-2.0.so.0
#9  0xb7c69085 in gdk_x11_register_standard_event_type ()
   from /usr/lib/libgdk-x11-2.0.so.0
#10 0xb7af7c02 in g_main_depth () from
/usr/lib/libglib-2.0.so.0
#11 0xb7af8c78 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#12 0xb7af8fb0 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#13 0xb7af9553 in g_main_loop_run () from
/usr/lib/libglib-2.0.so.0
#14 0xb7dbe2e3 in gtk_main () from
/usr/lib/libgtk-x11-2.0.so.0
#15 0x08350a47 in wxEventLoop::Run (this=0x85b9e70) at
./src/gtk/evtloop.cpp:80
#16 0x082da5c2 in wxAppBase::MainLoop (this=0x85ac0e8)
    at ./src/common/appcmn.cpp:272
#17 0x082da70b in wxAppBase::OnRun (this=0x85ac0e8)
    at ./src/common/appcmn.cpp:340
#18 0x0811a651 in Application::OnRun (this=0x85ac0e8)
at ../src/main.cpp:117


This may seem similar to another bug report, but it
isn't the same since for that other one you can't get
the backtrace (it shows gtk main loop running, and
that's too late).




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1531348&group_id=9863