Your message dated Fri, 10 Oct 2014 19:15:58 +0100 with message-id <[email protected]> and subject line Re: Bug#671785: python-gtk2: crashes reportbug on Linux with GLib >= 2.41, or kFreeBSD has caused the Debian Bug report #671785, regarding python-gtk2: segfaults when running reportbug on kfreebsd 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 [email protected] immediately.) -- 671785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671785 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: python2.7 Version: 2.7.3~rc2-2.1 Severity: grave User: [email protected] Usertags: kfreebsd $ LD_LIBRARY_PATH=/usr/lib/debug:/usr/lib/debug/lib/x86_64-kfreebsd-gnu gdb --args python /usr/bin/reportbug [...] (gdb) r Starting program: /usr/bin/python /usr/bin/reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. > Program received signal SIGSEGV, Segmentation fault. __pthread_unlock (lock=0x13cd698) at spinlock.c:228 228 spinlock.c: El fitxer o directori no existeix. (gdb) bt #0 __pthread_unlock (lock=0x13cd698) at spinlock.c:228 #1 0x0000000800a85de9 in *__GI___pthread_mutex_unlock (mutex=<optimized out>) at mutex.c:190 #2 0x00000008036d7c81 in g_mutex_unlock (mutex=<optimized out>) at /build/buildd-glib2.0_2.32.2-1-kfreebsd-amd64-QJQ4PI/glib2.0-2.32.2/./glib/gthread-posix.c:227 #3 0x00000008047a4a1f in IA__gtk_main () at /build/buildd-gtk+2.0_2.24.10-1-kfreebsd-amd64-ErjCNI/gtk+2.0-2.24.10/gtk/gtkmain.c:1255 #4 0x0000000804359c24 in ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so #5 0x00000008027625d1 in readline_until_enter_or_signal (signal=<synthetic pointer>, prompt=<optimized out>) at /home/rmh/hacking/kfreebsd/python/python2.7-2.7.3~rc2/Modules/readline.c:963 #6 call_readline (sys_stdin=<optimized out>, sys_stdout=<optimized out>, prompt=<optimized out>) at /home/rmh/hacking/kfreebsd/python/python2.7-2.7.3~rc2/Modules/readline.c:1055 #7 0x000000000041faa2 in PyOS_Readline (sys_stdin=0x801ebea00, sys_stdout=0x801ebeae0, prompt=0xf9b144 "> ") at ../Parser/myreadline.c:211 #8 0x00000000004c9595 in builtin_raw_input (self=<optimized out>, args=<optimized out>) at ../Python/bltinmodule.c:2046 #9 0x00000000004d3d2d in call_function (oparg=<optimized out>, pp_stack=0x7fffffffd2c0) at ../Python/ceval.c:4021 #10 PyEval_EvalFrameEx (f=<optimized out>, throwflag=<optimized out>) at ../Python/ceval.c:2666 #11 0x00000000004d58d6 in PyEval_EvalCodeEx (co=<optimized out>, globals=<optimized out>, locals=<optimized out>, args=<optimized out>, argcount=3, kws= 0x142dd88, kwcount=0, defs=0xf96888, defcount=3, closure=0x0) at ../Python/ceval.c:3253 [...] Also reproducible with 2.7.2-11. As it appeared recently in sid it's probably related to an upgrade of some other package. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 8.1-1-amd64 Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---Package: gtk+2.0 Version: 2.24.25-1 On Thu, 21 Aug 2014 at 10:49:53 +0100, Simon McVittie wrote: > Having just done basically the same analysis for #758619 > (which is the same locking error manifesting on Linux due to GLib 2.41 > having better checks similar to those in kFreeBSD, and is currently RC), > I think pygtk's PyOS_InputHook is fundamentally flawed. gtk+2.0 (>= 2.24.25) has a workaround around this design flaw, and incorrect locking in various other users of Gtk2. That makes this bug largely theoretical (on both Linux and kFreeBSD), and it seems vanishingly unlikely that it will ever be fixed in pygtk (which is dead upstream anyway), so I'm closing it. S
--- End Message ---
