Diamond hangs on a number of dialogs

[Jon Hill]

To replicate:

Open diamond.

Menu->file open

Click cancel

Diamond will hang.

I *think* this is a bug in pyGTK.

Running in a gdb session, I get:

jhill1@cube:~/software/libspud/spud/diamond$ gdb -args python bin/diamond
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/python...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/python bin/diamond
[Thread debugging using libthread_db enabled]
['/home/jhill1/.diamond/plugins/flml', '/usr/local/share/diamond/plugins/flml', '/etc/diamond/plugins/flml']
[New Thread 0xb701db70 (LWP 14937)]
[New Thread 0xb66ffb70 (LWP 14938)]
[New Thread 0xb5efeb70 (LWP 14939)]
[New Thread 0xb54ffb70 (LWP 14940)]
[New Thread 0xb4cfeb70 (LWP 14941)]
[Thread 0xb4cfeb70 (LWP 14941) exited]
[Thread 0xb54ffb70 (LWP 14940) exited]
[Thread 0xb5efeb70 (LWP 14939) exited]
[Thread 0xb66ffb70 (LWP 14938) exited]
^C
Program received signal SIGINT, Interrupt.
0x0012e416 in __kernel_vsyscall ()
(gdb) back
#0 0x0012e416 in __kernel_vsyscall ()
#1 0x0013c169 in __lll_lock_wait ()
    at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/lowlevellock.S:142
#2 0x001375cb in _L_lock_748 () from /lib/libpthread.so.0
#3 0x001373f1 in __pthread_mutex_lock (mutex=0x830b9c0)
    at pthread_mutex_lock.c:61
#4 0x00bf16d6 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#5 0x00bf195b in ?? () from /usr/lib/libgdk-x11-2.0.so.0
#6 0x00521841 in ?? () from /lib/libglib-2.0.so.0
#7 0x00523855 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#8 0x00527668 in ?? () from /lib/libglib-2.0.so.0
#9 0x00527ba7 in g_main_loop_run () from /lib/libglib-2.0.so.0
#10 0x0093c1d9 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x0076d060 in ?? () from /usr/lib/pymodules/python2.6/gtk-2.0/gtk/_gtk.so
#12 0x080ddd39 in PyEval_EvalFrameEx ()
#13 0x080df04c in PyEval_EvalFrameEx ()
#14 0x080dfbb2 in PyEval_EvalCodeEx ()
#15 0x080dfca7 in PyEval_EvalCode ()
#16 0x080fd956 in PyRun_FileExFlags ()
#17 0x080fdbb2 in PyRun_SimpleFileExFlags ()
#18 0x0805b6d3 in Py_Main ()
#19 0x0805a8ab in main ()
(gdb)

Search the internet seems to support this.

This occurs on Maverick (my laptop). It's about to be updated to Natty.

[Patrick Farrell (pefarrell)]

I can't reproduce this on natty with the latest diamond trunk.

[Jon Hill (jon-hill)]

Agreed - no longer appears in my upgraded Natty laptop.

Marking as "Won't fix", but making a metal note if a user ever mentions it.