Bug#758619: Reportbug closes with mutex locking issue
Package: Reportbug Version: 6.5.1 Reportbug crashes with the Attempt to unlock mutex that was not locked Aborted error. The backtrace for the same is gdb --args python /usr/bin/reportbug -b --no-check-available libpulse0 GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1 Copyright (C) 2014 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 i586-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from python...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/python /usr/bin/reportbug -b --no-check-available libpulse0 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. Gtk-Message: Failed to load module canberra-gtk-module [New Thread 0xadb09b40 (LWP 25300)] Attempt to unlock mutex that was not locked Program received signal SIGABRT, Aborted. 0xb7fde424 in __kernel_vsyscall () (gdb) thread apply all bt Thread 2 (Thread 0xadb09b40 (LWP 25300)): #0 0xb7fde424 in __kernel_vsyscall () #1 0xb7e6350b in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0xb6fc70b0 in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0 #3 0xb6fb8054 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6fb8479 in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0 #5 0xb63d5955 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 #6 0xb6fdf3da in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #7 0xb7fa2efb in start_thread (arg=0xadb09b40) at pthread_create.c:309 #8 0xb7e6dd4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 1 (Thread 0xb7d82700 (LWP 25294)): #0 0xb7fde424 in __kernel_vsyscall () #1 0xb7db2267 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #2 0xb7db3923 in __GI_abort () at abort.c:89 #3 0xb6ffdb20 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #4 0xb6665f74 in ?? () from /usr/lib/i386-linux-gnu/libgdk-x11-2.0.so.0 #5 0xb67b2bc5 in gtk_dialog_run () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0 #6 0xb6cb9283 in ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so #7 0x08107c0c in PyEval_EvalFrameEx () #8 0x081078db in PyEval_EvalFrameEx () #9 0x081078db in PyEval_EvalFrameEx () #10 0x08105f4d in PyEval_EvalCodeEx () #11 0x0813a88c in ?? () #12 0x08131578 in PyRun_FileExFlags () #13 0x08130725 in PyRun_SimpleFileExFlags () #14 0x080daaa7 in Py_Main () #15 0x080da50b in main () (gdb) quit Is there any patch available for this issue. -- Regards., Prema S
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I have had the same problem, reportbug has not launched, and when I tried from command line, I got the messages Attempt to unlock mutex that was not locked Aborted I found that bug 763690 claims to have a patch to this. Z - --- System information. --- Architecture: amd64 Kernel: Linux 3.16-2-amd64 Debian Release: jessie/sid 500 testing-updates ftp.uk.debian.org 500 testing security.debian.org 500 testing ftp.uk.debian.org 500 testing deb.bitmask.net 500 stable deb.bitmask.net 1 experimentalftp.uk.debian.org - --- Package information. --- Depends (Version) | Installed ===-+-=== python (= 2.6) | 2.7.8-1 apt | 1.0.9.3 python-reportbug (= 6.5.0+nmu1) | 6.5.1 python (= 2.6) | 2.7.8-1 python-support (= 0.90.0) | 1.0.15 apt | 1.0.9.3 python-debian | 0.1.24 python-debianbts| 1.12 Package's Recommends field is empty. Suggests (Version) | Installed -+- postfix | OR exim4| 4.84-2 OR mail-transport-agent | gnupg| 1.4.18-4 OR pgp | debconf-utils ( 1.1.0) | debsums (= 2.0.47) | file ( 1.30) | 1:5.19-2 dlocate | python-urwid | python-gtk2 | 2.24.0-4 python-vte | 1:0.28.2-5 python-gtkspell | 2.25.3-13 xdg-utils| 1.1.0~rc1+git20111210-7.1 emacs22-bin-common | OR emacs23-bin-common | claws-mail(= 3.8.0) | reportbug| 6.5.1 - --- Output from package bug script --- reportbug_version 6.4.4 mode standard ui gtk2 realname Z email b...@theloosespoke.org.uk no-cc header X-Debbugs-CC: b...@theloosespoke.org.uk smtphost reportbug.debian.org -BEGIN PGP SIGNATURE- iQEcBAEBCgAGBQJUQ3J5AAoJEC8Z0Emvryki5QEIAJd3ht2DOm8Dgf32xE8fNoQl +G1wvriZXyXYdH5FbctHTFoHrmQHFn43sQXTjy8JSMfpextQXir2fIHij0aRtdmw ZCVxIHng+sW1A/0X2azDIsv+LVOgo2rPagoemDmZrf/p6phhoi3Ic1JbbfHf2ENT Slzg/eClr4g1CBN63MRcpBIv1tuZ88IGwW3D4mTIGQMJSXIH0gB+yjM2ZkBkaeQn 67/CC2xmOdDIMks6qIf3vB7VDVHDmzOiJl/8IlfbeTHZ+dCJmFbi0ZLyRtiJIFeJ ePJ961mX3fBl/XNSTKaUikkPCz+guyqCaqI1Qxm7GTLW6yCx1PbIlZaABf2GIj4= =2Ie9 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug and pyrenamer problems are not fixed on Jessie
I (on Jessie up-to-date) still have this problems # reportbug Attempt to unlock mutex that was not locked Aborted and # pyrenamer /usr/lib/pymodules/python2.7/pyrenamer/pyrenamer.py:120: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated self.glade_tree = gtk.glade.XML(pyrenamerglob.gladefile, main_window) Attempt to unlock mutex that was not locked Aborted Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug and pyrenamer problems are not fixed on Jessie
On 2014-10-13 22:43, sp113438 wrote: I (on Jessie up-to-date) still have this problems # reportbug Attempt to unlock mutex that was not locked Aborted and # pyrenamer /usr/lib/pymodules/python2.7/pyrenamer/pyrenamer.py:120: GtkWarning: GtkSpinButton: setting an adjustment with non-zero page size is deprecated self.glade_tree = gtk.glade.XML(pyrenamerglob.gladefile, main_window) Attempt to unlock mutex that was not locked Aborted Thanks! That's entirely expected, since the fixed version of gtk+3.0 has not yet migrated to Jessie. See https://www.debian.org/devel/testing for an explanation of this process. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: pyrenamer: Attempt to unlock mutex that was not locked
pyrenamer also gives: Attempt to unlock mutex that was not locked Aborted Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: Attempt to unlock mutex that was not locked
It happens on Sid as well as Jessie (amd64). Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
It seems, that there a several applications with that error. pyrenamer and gftp also have that issue. Thomas -- gpg-id: ccdbc2cf https://www.setho.org/people signature.asc Description: OpenPGP digital signature
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
Package: reportbug Version: 6.5.1 Followup-For: Bug #758619 What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/tester/.reportbugrc: reportbug_version 6.4.4 mode novice ui gtk2 no-cc header X-Debbugs-CC: tester@localhost.localdomain smtphost reportbug.debian.org -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-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/dash Versions of packages reportbug depends on: ii apt 1.0.9.2 ii python2.7.8-1 ii python-reportbug 6.5.1 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: ii claws-mail 3.10.1-4 pn debconf-utils none ii debsums2.0.52+nmu2 pn dlocatenone ii emacs23-bin-common 23.4+1-4.1+b1 ii exim4 4.84-2 ii exim4-daemon-light [mail-transport-agent] 4.84-2 ii file 1:5.19-2 ii gnupg 1.4.18-4 ii python-gtk22.24.0-4 ii python-gtkspell2.25.3-13 pn python-urwid none ii python-vte 1:0.28.2-5 ii xdg-utils 1.1.0~rc1+git20111210-7.1 Versions of packages python-reportbug depends on: ii apt 1.0.9.2 ii python-debian 0.1.23 ii python-debianbts 1.12 pn python:anynone python-reportbug suggests no packages. -- Configuration Files: /etc/reportbug.conf changed: submit query-bts cc config-files compress email humbe...@example.com smtphost reportbug.debian.org verify -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: (no subject)
fwiw: gftp crashes with the same symptoms, see #763371 - tim Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 1.0.9.1 ii python2.7.8-1 ii python-reportbug 6.5.1 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none pn debconf-utilsnone pn debsums none pn dlocate none pn emacs22-bin-common | emacs23-bin-common none ii file 1:5.19-2 ii gnupg1.4.18-4 pn postfix | exim4 | mail-transport-agent none ii python-gtk2 2.24.0-4 pn python-gtkspell none pn python-urwid none ii python-vte 1:0.28.2-5 ii xdg-utils1.1.0~rc1+git20111210-7.1 Versions of packages python-reportbug depends on: ii apt 1.0.9.1 ii python-debian 0.1.23 ii python-debianbts 1.12 pn python:anynone python-reportbug suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug: Can confirm, reportbug fails with GTK, not in text mode
Package: reportbug Version: 6.5.1 Followup-For: Bug #758619 Dear Maintainer, * What led up to the situation? Trying to report a bug on another package (pidgin-skype), which curiously fails with the exact same error message. Saw this exact same error unable to unlock mutex for the first time yesterday in pidgin and now in reportbug. * What exactly did you do (or not do) that was effective (or ineffective)? I configured reportbug to run in GUI mode. * What was the outcome of this action? reportbug crashes with Attempt to unlock mutex that was not locked * What outcome did you expect instead? reportbug starting -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/buster/.reportbugrc: reportbug_version 6.5.1 mode novice ui text email m...@bstr.eu smtphost bstr.eu smtpuser buster smtptls -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 1.0.9.1 ii python2.7.8-1 ii python-reportbug 6.5.1 pn python:anynone reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail none pn debconf-utilsnone pn debsums none pn dlocate none pn emacs22-bin-common | emacs23-bin-common none ii file 1:5.19-2 ii gnupg1.4.18-4 pn postfix | exim4 | mail-transport-agent none ii python-gtk2 2.24.0-4 ii python-gtkspell 2.25.3-13 pn python-urwid none pn python-vte none ii xdg-utils1.1.0~rc1+git20111210-7.1 Versions of packages python-reportbug depends on: ii apt 1.0.9.1 ii python-debian 0.1.23 ii python-debianbts 1.12 pn python:anynone python-reportbug suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: The fix was intended/verified for a non graphical useage
At least the fix, solves this use case (at least for me). And as the bug is in pygtk2 which is dead, maybe the bug should be reassigned. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#758619:
This bug now exists in Testing (glib2.0-2.42.0 has just been migrated to Testing). reportbug --ui=text xxx still works. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
On 21/09/14 22:47, Sandro Tosi wrote:
On Thu, Aug 21, 2014 at 10:38 AM, Simon McVittie s...@debian.org wrote:
+gtk.set_interactive (0)
gtk.gdk.threads_init ()
sadly this patch didnt fix the problem, and I can replicate it in a
clean sid chroot. do you have any other suggestions?
The next best ideas I have are:
* ask the gtk2 maintainers to apply upstream commit
fbf38d16bcc26630f0f721d266509f5bc292f606 (attached) to work around
pygtk2 being an example of the wrong code mentioned in that commit;
and/or
* ask the pygtk2 maintainers to stub out the interactive code in
pygtk2, slightly breaking interactive use of pygtk2 but maybe nobody
will actually notice; and/or
* switch reportbug to using Gtk3 via python-gi
I realise that last one is not trivial, but pygtk2 is dead upstream and
gtk2 is not a whole lot better, so it would be a good idea for jessie+1
regardless.
S
From fbf38d16bcc26630f0f721d266509f5bc292f606 Mon Sep 17 00:00:00 2001
From: Emmanuele Bassi eba...@gnome.org
Date: Tue, 26 Aug 2014 12:07:34 +0100
Subject: [PATCH] threads: Do not release the GDK lock if it hasn't been
acquired yet
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Since GLib ⥠2.41, attempting to release an unlocked mutex will abort(),
as it happens on most systems already.
Given the lack of proper documentation on how to use GDK with threads,
there is code in the wild that does:
gdk_threads_init ();
gdk_init ();
...
gtk_main ();
instead of the idiomatically correct:
gdk_threads_init ();
gdk_threads_enter ();
gtk_init ();
...
gtk_main ();
...
gdk_threads_leave ();
Which means that gtk_main() will try to release the GDK lock, and thus
trigger an error from GLib.
we cannot really fix all the wrong code everywhere, and since it does
not cost us anything, we can work around the issue inside GDK itself, by
trying to acquire the GDK lock inside gdk_threads_leave() with
trylock().
https://bugzilla.gnome.org/show_bug.cgi?id=735428
---
gdk/gdk.c | 24 +++-
1 file changed, 23 insertions(+), 1 deletion(-)
diff --git a/gdk/gdk.c b/gdk/gdk.c
index 0106d8a..f722dbf 100644
--- a/gdk/gdk.c
+++ b/gdk/gdk.c
@@ -434,7 +434,29 @@ static void
gdk_threads_impl_unlock (void)
{
if (gdk_threads_mutex)
-g_mutex_unlock (gdk_threads_mutex);
+{
+ /* we need a trylock() here because trying to unlock a mutex
+ * that hasn't been locked yet is:
+ *
+ * a) not portable
+ * b) fail on GLib ⥠2.41
+ *
+ * trylock() will either succeed because nothing is holding the
+ * GDK mutex, and will be unlocked right afterwards; or it's
+ * going to fail because the mutex is locked already, in which
+ * case we unlock it as expected.
+ *
+ * this is needed in the case somebody called gdk_threads_init()
+ * without calling gdk_threads_enter() before calling gtk_main().
+ * in theory, we could just say that this is undefined behaviour,
+ * but our documentation has always been *less* than explicit as
+ * to what the behaviour should actually be.
+ *
+ * see bug: https://bugzilla.gnome.org/show_bug.cgi?id=735428
+ */
+ g_mutex_trylock (gdk_threads_mutex);
+ g_mutex_unlock (gdk_threads_mutex);
+}
}
/**
--
2.1.0
Bug#758619: more complete backtrace
Hello Simon, On Thu, Aug 21, 2014 at 10:38 AM, Simon McVittie s...@debian.org wrote: --- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 + +++ gtk2_ui.py 2014-08-21 09:29:02.843495121 + @@ -35,6 +35,7 @@ except: has_spell = False +gtk.set_interactive (0) gtk.gdk.threads_init () import sys sadly this patch didnt fix the problem, and I can replicate it in a clean sid chroot. do you have any other suggestions? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
This grave bug is still present in reportbug 6.5.1 on fully patched sid, preventing all bug reporting: $ reportbug Attempt to unlock mutex that was not locked Aborted Kind regards, -- Ben Caradoc-Davies b...@wintersun.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619:
Hi Version 6.5.1 is installed on my system and the bug is still there. = apt show reportbug Package: reportbug Version: 6.5.1 Installed-Size: 226 kB Maintainer: Reportbug Maintainers reportbug-ma...@lists.alioth.debian.org Depends: python, python:any (= 2.6~), apt, python-reportbug (= 6.5.1) Suggests: postfix | exim4 | mail-transport-agent, gnupg | pgp, debconf-utils ( 1.1.0), debsums (= 2.0.47), file ( 1.30), dlocate, python-urwid, python-gtk2, python-vte, python-gtkspell, xdg-utils, emacs22-bin-common | emacs23-bin-common, claws-mail (= 3.8.0) Homepage: http://alioth.debian.org/projects/reportbug/ Tag: devel::bugtracker, implemented-in::python, interface::commandline, mail::smtp, network::client, protocol::http, protocol::smtp, role::program, scope::utility, suite::debian, use::TODO, works-with-format::plaintext, works-with::bugs Section: utils Priority: standard Download-Size: 122 kB APT-Manual-Installed: yes APT-Sources: http://http.us.debian.org/debian/ unstable/main amd64 Packages Description: reports bugs in the Debian distribution reportbug is a tool designed to make the reporting of bugs in Debian and derived distributions relatively painless. Its features include: . * Integration with mutt and mh/nmh mail readers. * Access to outstanding bug reports to make it easier to identify whether problems have already been reported. * Automatic checking for newer versions of packages. * Optional automatic verification of integrity of packages via debsums. * Support for following-up on outstanding reports. * Optional PGP/GnuPG integration. . reportbug is designed to be used on systems with an installed mail transport agent, like exim or sendmail; however, you can edit the configuration file and send reports using any available mail server. . This package also includes the querybts script for browsing the Debian bug tracking system. = On execution : l@leonardo ~ % reportbug Attempt to unlock mutex that was not locked zsh: abort reportbug l@leonardo ~ % echo $? 134 l@leonardo ~ % signature.asc Description: This is a digitally signed message part
Bug#758619: [reportbug/master] uninstall GTK+ readline hook, this prevent a crash in reportbug; thanks to Eric Valette for the report and to Simon McVittie for the GTK+-side analysis and patch; Closes
tag 758619 pending tag 758619 pending thanks Date: Thu Sep 4 23:14:37 2014 +0100 Author: Sandro Tosi mo...@debian.org Commit ID: 0d118098881a15a92a089ed20ba3e2eb08cfc4b7 Commit URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff;h=0d118098881a15a92a089ed20ba3e2eb08cfc4b7 Patch URL: http://anonscm.debian.org/gitweb/?p=reportbug/reportbug.git;a=commitdiff_plain;h=0d118098881a15a92a089ed20ba3e2eb08cfc4b7 uninstall GTK+ readline hook, this prevent a crash in reportbug; thanks to Eric Valette for the report and to Simon McVittie for the GTK+-side analysis and patch; Closes: #758619 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: Why still not fixed!
It means almost nobody can report bug on unstable. A working patch is available -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
forwarded 758619 https://bugzilla.gnome.org/show_bug.cgi?id=735141 found 758619 glib2.0/2.41.2-1 notfound 758619 glib2.0/2.40.0-4 thanks On 20/08/14 22:50, Eric Valette wrote: Because I use the glib/gtk from experimental I guess. Thanks, yes, it's that. Specifically, this change: https://bugzilla.gnome.org/show_bug.cgi?id=731986 In particular, the abort on incorrect locking is new; the original plan seems to have been for it to be runtime-optional. I've sent this upstream to ask whether runtime-optional is feasible. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
On 08/21/2014 10:26 AM, Simon McVittie wrote: In particular, the abort on incorrect locking is new; the original plan seems to have been for it to be runtime-optional. I've sent this upstream to ask whether runtime-optional is feasible. Well instead of correcting the symptom, I would prefer to correct the bug itself. If locking mecahnism is hazardous, then it eman beahavior is hazardous and that could lead to other bugs later. Searching for the bug, I saw that, in the past, the very same undefined behavior caused crash instead of and assert. But I have no time (and probably not the gtk/glib basic knowledge) to search for a solution. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
On 08/21/2014 10:37 AM, Eric Valette wrote: Searching for the bug, I saw that, in the past, the very same undefined behavior caused crash instead of and assert. http://debian.2.n7.nabble.com/Bug-671785-segfaults-when-running-reportbug-td548240.html meaning the bug is not new and was triggered before evn with the pthread lock mechanism. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: Much simpler code to trigger the problem (extract from bug #671785)
On 08/21/2014 10:52 AM, Eric Valette wrote: cat test.py #!/usr/bin/python import gtk gtk.gdk.threads_init() raw_input(If this didn't crash, hit enter.) 2 r-x-ceva6380:~-python test.py If this didn't crash, hit enter.Attempt to unlock mutex that was not locked Aborted #!/usr/bin/python import gtk gtk.gdk.threads_init() gtk.gdk.threads_enter() = fixes the problem raw_input(If this didn't crash, hit enter.) python test.py If this didn't crash, hit enter. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
# the real bug is #671785 but it's easy to avoid it in reportbug reassign 758619 reportbug tags 758619 + patch thanks On 21/08/14 09:37, Eric Valette wrote: Well instead of correcting the symptom, I would prefer to correct the bug itself. If locking mecahnism is hazardous, then it eman beahavior is hazardous and that could lead to other bugs later. Indeed. I think it's pygtk that is getting this wrong, and as you pointed out in another mail, we have already had a bug to track that, #671785, since 2012. The upstream bug has had no activity since 2012 either, until today. However, reportbug can easily work around it, whereas a solution in pygtk is rather more involved (and might never happen, since pygtk is deprecated upstream); so I think it would be best if the reportbug maintainers apply the one-line workaround, which is to turn off the broken feature with the patch that can be found at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671785#53 (the functional part is reproduced at the end of this mail). Let's use bug number 758619 to track that. I now realise that the steps to reproduce the bug are: * you have either GLib from experimental on Linux, or kFreeBSD, so the locking error is fatal; * you have python-gtk2 and $DISPLAY is set, so reportbug's gtk2 UI module can load; as a side-effect, python-gtk2 registers the faulty PyOS_InputHook implementation; * but you *do not* use the gtk2 UI module, so reportbug calls raw_input(), which results in the PyOS_InputHook being called and with that information, I can reproduce it in an experimental chroot with xvfb-run reportbug reportbug. The patch below fixes it. As much as I'd like to say this is release-critical for python-gtk2, which is also dead upstream, so let's remove it from Debian and tell everyone to use Gtk 3 via pygi, I don't think the maintainers of its 300 reverse dependencies would be very impressed. S --- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 + +++ gtk2_ui.py 2014-08-21 09:29:02.843495121 + @@ -35,6 +35,7 @@ except: has_spell = False +gtk.set_interactive (0) gtk.gdk.threads_init () import sys -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
--- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 + +++ gtk2_ui.py2014-08-21 09:29:02.843495121 + @@ -35,6 +35,7 @@ except: has_spell = False +gtk.set_interactive (0) gtk.gdk.threads_init () import sys I confirm this also fixes the bug for me. Thanks for the support. -- eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
On Tue, 19 Aug 2014 at 12:08:39 +0200, Jan Binder wrote: reportbug just aborts with exit code 134 when it is started. ... Attempt to unlock mutex that was not locked I can't reproduce this: reportbug reportbug (with the default text-mode UI) and reportbug --ui=gtk2 reportbug both seem to work fine here. For those who can reproduce it, a backtrace with libgtk2.0-0-dbg, libglib2.0-0-dbg and python-gtk2-dbg installed, using thread apply all bt instead of just bt, would be useful information. It would also be useful if someone who can reproduce this could send the output of these commands run in a terminal: reportbug --template libgtk2.0-0 reportbug --template reportbug which I think will work despite this bug. On Tue, 19 Aug 2014 at 11:15:31 +0100, Sandro Tosi forwarded: (gdb) bt #0 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x76f297e8 in __GI_abort () at abort.c:89 #2 0x72cdc85d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x719f4bbf in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #4 0x720a7d54 in ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so #5 0x74148a99 in ?? () from /usr/lib/python2.7/lib-dynload/readline.x86_64-linux-gnu.so #6 0x00448d04 in PyOS_Readline () This looks more like a bug in Gtk2 or python-gtk2 than a GLib bug. Frame 3 is in gtk_main(), frame 2 is in GLib which just issued a message Attempt to unlock mutex that was not locked, and frame 1 is abort(): this indicates that it was probably frame 3 (gtk_main()) that behaved incorrectly. The only way to address this bug from within GLib would be to remove the check that says unlocking a mutex that isn't locked is not allowed, or reduce it from fatal to non-fatal but keep the spam to stderr. If something is unlocking a mutex that isn't locked, that's a symptom of a serious multi-threading bug somewhere (which could equally easily manifest as a thread releasing a lock that it does not actually hold, causing unsafe actions elsewhere), so I think it is correct that it is fatal to make it as visible as possible. I notice with some trepidation that /usr/share/pyshared/reportbug/ui/gtk2_ui.py uses both Gtk and threads. I wonder whether the root cause of this bug might be something like the first use of Gtk2 happened to be from a non-main thread? S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: requested additional info
reportbug --template libgtk2.0-0 *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Eric Valette eric2.vale...@orange.com' as your from address. Getting status for libgtk2.0-0... Will send report to Debian (per lsb_release). Maintainer for libgtk2.0-0 is 'Debian GNOME Maintainers pkg-gnome-maintain...@lists.alioth.debian.org'. Looking up dependencies of libgtk2.0-0... Rewriting subject to 'libgtk2.0-0: none' Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Eric Valette eric2.vale...@orange.com To: Debian Bug Tracking System sub...@bugs.debian.org Subject: libgtk2.0-0: none Reply-To: eric2.vale...@orange.com Package: libgtk2.0-0 Version: 2.24.24-1 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.15.10 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF8) Shell: /bin/sh linked to /bin/bash Versions of packages libgtk2.0-0 depends on: ii libatk1.0-0 2.12.0-1 ii libc6 2.19-9 ii libcairo2 1.12.16-2 ii libcups2 1.7.5-1 ii libfontconfig1 2.11.0-6 ii libfreetype6 2.5.2-1.1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.41.2-1 ii libgtk2.0-common 2.24.24-1 ii libpango-1.0-0 1.36.6-1 ii libpangocairo-1.0-0 1.36.6-1 ii libpangoft2-1.0-0 1.36.6-1 ii libx11-6 2:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxcursor1 1:1.1.14-1 ii libxdamage1 1:1.1.4-2 ii libxext6 2:1.3.2-1 ii libxfixes3 1:5.0.1-2 ii libxi6 2:1.7.4-1 ii libxinerama1 2:1.1.3-1 ii libxrandr2 2:1.4.2-1 ii libxrender1 1:0.9.8-1 ii multiarch-support 2.19-9 ii shared-mime-info 1.3-1 Versions of packages libgtk2.0-0 recommends: ii hicolor-icon-theme 0.13-1 ii libgtk2.0-bin 2.24.24-1 Versions of packages libgtk2.0-0 suggests: pn gvfs none ii librsvg2-common 2.40.3-1 -- no debconf information If you want to provide additional information, please wait to receive the bug tracking number via email; you may then send any extra information to n...@bugs.debian.org (e.g. 999...@bugs.debian.org), where n is the bug number. Normally you will receive an acknowledgement via email including the bug report number within an hour; if you haven't received a confirmation, then the bug reporting process failed at some point (reportbug or MTA failure, BTS maintenance, etc.). toto:~-reportbug --template reportbug *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Eric Valette eric2.vale...@orange.com' as your from address. Getting status for reportbug... Will send report to Debian (per lsb_release). Maintainer for reportbug is 'Reportbug Maintainers reportbug-ma...@lists.alioth.debian.org'. Looking up dependencies of reportbug... Getting status for related package python-reportbug... Looking up 'depends' of related package python-reportbug... Looking up 'suggests' of related package python-reportbug... Getting changed configuration files... Rewriting subject to 'reportbug: none' Gathering additional data, this may take a while... Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Eric Valette eric2.vale...@orange.com To: Debian Bug Tracking System sub...@bugs.debian.org Subject:
Bug#758619: more complete backtrace
gdb --args python /usr/bin/reportbug -b --no-check-available libpulse0 GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1 Copyright (C) 2014 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 x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from python...Reading symbols from /usr/lib/debug//usr/bin/python2.7...done. done. (gdb) run Starting program: /usr/bin/python /usr/bin/reportbug -b --no-check-available libpulse0 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Eric Valette eric2.vale...@orange.com' as your from address. Getting status for libpulse0... Will send report to Debian (per lsb_release). Maintainer for libpulse0 is 'Pulseaudio maintenance team pkg-pulseaudio-de...@lists.alioth.debian.org'. Looking up dependencies of libpulse0... Getting changed configuration files... Briefly describe the problem (max. 100 characters allowed). This will be the bug email subject, so keep the summary as concise as possible, for example: fails to send email or does not start with -q option specified (enter Ctrl+c to exit reportbug without reporting a bug). Attempt to unlock mutex that was not locked Program received signal SIGABRT, Aborted. 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) thread apply all bt Thread 1 (Thread 0x77fc0700 (LWP 17124)): #0 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x76f297e8 in __GI_abort () at abort.c:89 #2 0x72cdc85d in g_mutex_unlock_slowpath (mutex=optimized out, prev=optimized out) at /build/glib2.0-MHsCdQ/glib2.0-2.41.2/./glib/gthread-posix.c:1327 #3 0x719f4bbf in IA__gtk_main () at /build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkmain.c:1256 #4 0x720a7d54 in _loop () at /build/buildd-pygtk_2.24.0-3+b1-amd64-HH_0XF/pygtk-2.24.0/gtk/gtk.override:126 #5 0x74148b21 in readline_until_enter_or_signal (signal=synthetic pointer, prompt=optimized out) at /build/python2.7-WkYSEh/python2.7-2.7.8/Modules/readline.c:996 #6 call_readline (sys_stdin=optimized out, sys_stdout=optimized out, prompt=optimized out) at /build/python2.7-WkYSEh/python2.7-2.7.8/Modules/readline.c:1088 #7 0x0044a06f in PyOS_Readline (sys_stdin=0x772974e0 _IO_2_1_stdin_, sys_stdout=sys_stdout@entry=0x772972a0 _IO_2_1_stdout_, prompt=prompt@entry=0x7434f84c ) at ../Parser/myreadline.c:207 #8 0x004453e2 in builtin_raw_input.lto_priv.1351 (self=optimized out, args=optimized out) at ../Python/bltinmodule.c:2060 #9 0x004c8265 in call_function (oparg=optimized out, pp_stack=optimized out) at ../Python/ceval.c:4021 #10 PyEval_EvalFrameEx () at ../Python/ceval.c:2667 #11 0x004c6ab9 in PyEval_EvalCodeEx () at ../Python/ceval.c:3253 #12 0x004c877c in fast_function (nk=optimized out, na=optimized out, n=optimized out, pp_stack=optimized out, func=optimized out) at ../Python/ceval.c:4117 #13 call_function (oparg=optimized out, pp_stack=optimized out) at ../Python/ceval.c:4042 #14 PyEval_EvalFrameEx () at ../Python/ceval.c:2667 #15 0x004c6ab9 in PyEval_EvalCodeEx () at ../Python/ceval.c:3253 #16 0x004c877c in fast_function (nk=optimized out, na=optimized out, n=optimized out, pp_stack=optimized out, func=optimized out) at ../Python/ceval.c:4117 #17 call_function (oparg=optimized out,
Bug#758619: more complete backtrace
Did you upgrade a package recently that could have triggered this, i.e.
related to Python, GLib, Gtk 2 or reportbug? I would be interested to
know why this is new.
Some analysis below. I think this is probably a pygtk bug, but there is
a workaround that reportbug could use.
On 20/08/14 12:15, VALETTE Eric OLNC/OLPS wrote:
#2 0x72cdc85d in g_mutex_unlock_slowpath (mutex=optimized
out, prev=optimized out)
at
/build/glib2.0-MHsCdQ/glib2.0-2.41.2/./glib/gthread-posix.c:1327
#3 0x719f4bbf in IA__gtk_main () at
/build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkmain.c:1256
#4 0x720a7d54 in _loop
()
at
/build/buildd-pygtk_2.24.0-3+b1-amd64-HH_0XF/pygtk-2.24.0/gtk/gtk.override:126
#5 0x74148b21 in readline_until_enter_or_signal
(signal=synthetic pointer, prompt=optimized out)
at
/build/python2.7-WkYSEh/python2.7-2.7.8/Modules/readline.c:996
_loop() is pygtk's implementation of PyOS_ImportHook, which takes the
Python GIL and calls gtk_main():
gstate = PyGILState_Ensure();
gtk_main();
PyGILState_Release(gstate);
gtk_main() releases the GDK mutex before calling g_main_loop_run(), and
reacquires it afterwards:
if (g_main_loop_is_running (main_loops-data))
{
GDK_THREADS_LEAVE ();
g_main_loop_run (loop);
GDK_THREADS_ENTER ();
gdk_flush ();
}
which means it is not safe to call gtk_main() without holding the GDK
mutex (it is documented that only the thread holding the GDK mutex can
safely call Gtk functions, so that seems reasonable).
However, pygtk doing this in an input hook seems wrong, because I don't
see anything that would guarantee that all invocations of Python's
readline wrapper will be done from a thread that currently holds the GDK
mutex. There is also nothing to say that invocations of the readline
wrapper *won't* be done from a thread that holds the GDK mutex; so there
doesn't seem to be any way this can be done safely?
I don't know what code in reportbug is triggering this hook. One
possible solution would be for reportbug to call gtk.set_interactive(0)
to avoid registering this hook, since the hook's intended use seems to
be for the interactive Python prompt rather than real applications, so
reportbug probably gets nothing useful from it.
pygtk is deprecated upstream, and python-gi does not have this hook, so
I think it's rather unlikely that this hook will be fixed in pygtk,
except possibly via deletion.
I don't think GLib is really doing anything wrong by crashing here: the
C code in pygtk is asking to unlock a mutex that is not actually locked,
which is a symptom of doing locking in a way that can't possibly be
reliable, so I would be inclined to put it in the category of undefined
behaviour.
The only way I can think of to make this hook reliable would be for
pygtk to use gdk_threads_set_lock_functions() before gdk_threads_init(),
to replace gdk_threads_enter and gdk_threads_leave with functions that
use a recursive mutex:
GRecMutex rmutex;
init()
{
gdk_threads_set_lock_functions (enter, leave);
gdk_threads_init ();
}
enter()
{
g_rec_mutex_lock (rmutex);
}
leave()
{
g_rec_mutex_unlock (rmutex);
}
and then make _loop() ensure that the rmutex is locked while it calls
gtk_main(). However, it would be necessary to be rather careful about
lock acquisition order between rmutex and the GIL, to avoid deadlocking
between one thread that is holding rmutex and wants the GIL, and another
thread that is holding the GIL and wants rmutex; so this plan is
probably flawed too.
Regards,
S
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: more complete backtrace
On 20/08/2014 22:46, Simon McVittie wrote: Did you upgrade a package recently that could have triggered this, i.e. related to Python, GLib, Gtk 2 or reportbug? I would be interested to know why this is new. Because I use the glib/gtk from experimental I guess. And you could have noticed it by reading the other info I have been requested to report. --eric -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked
Package: reportbug Version: 6.5.0+nmu1 Severity: grave reportbug just aborts with exit code 134 when it is started. $ reportbug Please enter the name of the package in which you have found a problem, or type 'other' to report a more general problem. Attempt to unlock mutex that was not locked zsh: abort reportbug -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#758619: [Reportbug-maint] reportbug is broken due to glib
control: reassign -1 libglib2.0-0 control: affects -1 reportbug Hello, thanks for the trace; I'm forwarding this info to the bug report and reassign it to glib. Regards, Sandro On Mon, Aug 18, 2014 at 4:13 PM, VALETTE Eric OLNC/OLPS eric2.vale...@orange.com wrote: gdb --args python /usr/bin/reportbug -b --no-check-available libpulse0 GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1 Copyright (C) 2014 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 x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from python...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/python /usr/bin/reportbug -b --no-check-available libpulse0 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. *** Welcome to reportbug. Use ? for help at prompts. *** Note: bug reports are publicly archived (including the email address of the submitter). Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'Eric Valette eric2.vale...@orange.com' as your from address. Getting status for libpulse0... Will send report to Debian (per lsb_release). Maintainer for libpulse0 is 'Pulseaudio maintenance team pkg-pulseaudio-de...@lists.alioth.debian.org'. Looking up dependencies of libpulse0... Getting changed configuration files... Briefly describe the problem (max. 100 characters allowed). This will be the bug email subject, so keep the summary as concise as possible, for example: fails to send email or does not start with -q option specified (enter Ctrl+c to exit reportbug without reporting a bug). Attempt to unlock mutex that was not locked = Program received signal SIGABRT, Aborted. 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x76f28407 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x76f297e8 in __GI_abort () at abort.c:89 #2 0x72cdc85d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x719f4bbf in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #4 0x720a7d54 in ?? () from /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/_gtk.so #5 0x74148a99 in ?? () from /usr/lib/python2.7/lib-dynload/readline.x86_64-linux-gnu.so #6 0x00448d04 in PyOS_Readline () #7 0x0044413c in ?? () #8 0x004c347d in PyEval_EvalFrameEx () #9 0x004c1d29 in PyEval_EvalCodeEx () #10 0x004c3963 in PyEval_EvalFrameEx () #11 0x004c1d29 in PyEval_EvalCodeEx () #12 0x004c3963 in PyEval_EvalFrameEx () #13 0x004c3c12 in PyEval_EvalFrameEx () #14 0x004c3c12 in PyEval_EvalFrameEx () #15 0x004c1d29 in PyEval_EvalCodeEx () #16 0x004fb43f in ?? () #17 0x004f0c72 in PyRun_FileExFlags () #18 0x004efdc4 in PyRun_SimpleFileExFlags () #19 0x00492398 in Py_Main () #20 0x76f14b45 in __libc_start_main (main=0x491e50 main, argc=5, argv=0x7fffe3f8, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffe3e8) at libc-start.c:287 #21 0x00491d7d in _start () (gdb) -- eric ___ Reportbug-maint mailing list reportbug-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
