On Tue, Nov 9, 2010 at 23:20, Dan 'Da Man' <heymr...@gmail.com> wrote: > Nice try? You assume I'm trying to pull a fast one on you, I just neglected > to see and use the updated version. I have installed > python-reportbug-4.12.6 and reportbug-4.12.6, and I'm still experiencing the > same crashing/unresponsiveness.
No, you installed the *ubuntu* version of those, that I don't maintain (and I wont, nor either care about reportbug in ubuntu). And, let's look at the dependencies: ii file 5.03-1ubuntu1 Determines file type using "magic" ii gnupg 1.4.9-4ubuntu7 GNU privacy guard - a free PGP rep ii python-gtk2 2.16.0-0ubuntu1 Python bindings for the GTK+ widge ii python-gtkspell 2.25.3-3ubuntu1.9.10.1 Python bindings for the GtkSpell l ii python-vte 1:0.22.2-0ubuntu2.1 Python bindings for the VTE widget oooh look at them: all the GTK+ stack is customized by ubuntu. That + no-one in Debian reported this "problem" it makes the issue be ubuntu specific, and I don't care fixing it for you.. > Since this is a python script I am not > aware of a way to initialize the program with gdb, I can attach gdb to the > process once I have already started reportbug. Can you advised on a way to > debug python script so I could possibly provide a more informative > backtrace? > Attached is a backtrace after reportbug has already started and crashed. run 'reportbug --ui=gtk2' on the command line and you'll see error in the console, if any (that's not python specific error resolution though, but basic debug). > Please reopen this bug report. No way, sorry. Goodbye, -- 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
