Bug#683951: reportbug crashes unless ran from the terminal.
Package: reportbug Version: 4.12.6 Severity: normal As I've said above unless I run reportbug from the terminal it crashes after it has me look over other bugs related to the package I'm about to report, when I hit continue it crashes after that screen. But solong as I run it from the terminal it does not crash. Since it doesn't crash from the terminal, I don't know of anyway to debug the thing, but it only crashes if I don't run it from the terminal. -- Package-specific info: ** Environment settings: INTERFACE=gtk2 ** /home/macarthur/.reportbugrc: reportbug_version 4.12.6 mode standard ui gtk2 email 133794...@gmail.com no-cc header X-Debbugs-CC: 133794...@gmail.com smtphost reportbug.debian.org -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt0.8.10.3+squeeze1 Advanced front-end for dpkg ii python 2.6.6-3+squeeze7 interactive high-level object-orie ii python-reportbug 4.12.6Python modules for interacting wit reportbug recommends no packages. Versions of packages reportbug suggests: pn debconf-utilsnone (no description available) pn debsums none (no description available) pn dlocate none (no description available) pn emacs22-bin-common | none (no description available) ii exim44.72-6+squeeze2 metapackage to ease Exim MTA (v4) ii exim4-daemon-light [ 4.72-6+squeeze2 lightweight Exim MTA (v4) daemon ii file 5.04-5+squeeze2 Determines file type using magic ii gnupg1.4.10-4GNU privacy guard - a free PGP rep ii python-gtk2 2.17.0-4Python bindings for the GTK+ widge pn python-gtkspell none (no description available) pn python-urwid none (no description available) ii python-vte 1:0.24.3-3 Python bindings for the VTE widget ii xdg-utils1.0.2+cvs20100307-2 desktop integration utilities from -- Configuration Files: /etc/reportbug.conf changed: submit query-bts cc config-files compress editor nano 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#683951: reportbug crashes unless ran from the terminal.
Hello, On Sun, Aug 5, 2012 at 7:26 PM, macarthur 133794...@gmail.com wrote: As I've said above unless I run reportbug from the terminal it crashes after it has me look over other bugs related to the package I'm about to report, when I hit continue it crashes after that screen. But solong as I run it from the terminal it does not crash. Since it doesn't crash from the terminal, I don't know of anyway to debug the thing, but it only crashes if I don't run it from the terminal. Do you mean the graphical UI of reportbug crashes while the textual one works? If so, can you run reportbug --ui=gtk2 from the terminal and report the backtrace? 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#683951: reportbug crashes unless ran from the terminal.
On 08/05/2012 01:29 PM, Sandro Tosi wrote: Hello, On Sun, Aug 5, 2012 at 7:26 PM, macarthur 133794...@gmail.com wrote: As I've said above unless I run reportbug from the terminal it crashes after it has me look over other bugs related to the package I'm about to report, when I hit continue it crashes after that screen. But solong as I run it from the terminal it does not crash. Since it doesn't crash from the terminal, I don't know of anyway to debug the thing, but it only crashes if I don't run it from the terminal. Do you mean the graphical UI of reportbug crashes while the textual one works? If so, can you run reportbug --ui=gtk2 from the terminal and report the backtrace? Regards, The graphical UI works from the terminal, but if I don't run the graphical ui from the terminal it crashes. That's the thing that confuses me most, since the gtk reportbug still works from the terminal but not if ran normally and by normally I mean(since I'm using GNOME), Applications-System Tools-Reportbug. the command for that one is. reportbug --exit-prompt --ui gtk2 and when I run it from the terminal it's just reportbug and it still does the gtk ui. I don't know why it defaults to that, but it seems to be. So the thing crashes. It also doesn't seem to crash all of the time. Only on certain packages here it's fuse-utils. And when I tried it again(after it was working after it crashed with it from the command line) I got two errors. the first was. *** glibc detected *** /usr/bin/python: munmap_chunk(): invalid pointerSegmentation fault and the second was Gdk:ERROR:/scratch/build-area/gtk+2.0-2.20.1/gdk/gdkregion-generic.c:1108:miUnionNonO: assertion failed: (y1 y2) Aborted I don't know what error was causing the crash with fuse-utils, and then reportbug, but it seems to happen randomly except when ran from the terminal. But now it seems to be crashing with no indication as to why. It seems to crash repeatedly for different reasons if it crashes once, but if I make it do one that I know _won't_ crash it, it'll work just fine. For example, I did gnome-about, and then quit normally. Did reportbug, and fuse-utils. Both worked just fine. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683951: reportbug crashes unless ran from the terminal.
On Sun, Aug 5, 2012 at 7:45 PM, macarthur 133794...@gmail.com wrote: On 08/05/2012 01:29 PM, Sandro Tosi wrote: Hello, On Sun, Aug 5, 2012 at 7:26 PM, macarthur 133794...@gmail.com wrote: As I've said above unless I run reportbug from the terminal it crashes after it has me look over other bugs related to the package I'm about to report, when I hit continue it crashes after that screen. But solong as I run it from the terminal it does not crash. Since it doesn't crash from the terminal, I don't know of anyway to debug the thing, but it only crashes if I don't run it from the terminal. Do you mean the graphical UI of reportbug crashes while the textual one works? If so, can you run reportbug --ui=gtk2 from the terminal and report the backtrace? Regards, The graphical UI works from the terminal, but if I don't run the graphical ui from the terminal it crashes. That's the thing that confuses me most, since the gtk reportbug still works from the terminal but not if ran normally and by normally I mean(since I'm using GNOME), Applications-System Tools-Reportbug. the command for that one is. reportbug --exit-prompt --ui gtk2 and when I run it from the terminal it's just reportbug and it still does the gtk ui. I don't know why it defaults to that, but it seems to be. because you chose so when reportbug was executed the first time. You can change it either running it with --configure or editing ~/.reportbugrc So the thing crashes. It also doesn't seem to crash all of the time. Only on certain packages here it's fuse-utils. And when I tried it again(after it was working after it crashed with it from the command line) I got two errors. the first was. *** glibc detected *** /usr/bin/python: munmap_chunk(): invalid pointerSegmentation fault this is new, and it's probably something broken on your system. and the second was Gdk:ERROR:/scratch/build-area/gtk+2.0-2.20.1/gdk/gdkregion-generic.c:1108:miUnionNonO: assertion failed: (y1 y2) Aborted This is a known issue, we still hadn't find the cause and fix it 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
