[Reportbug-maint] Bug#620225: reportbug: doesn't seem to be fixed yet... (?)

Sandro Tosi morph at debian.org
Sat Apr 20 21:40:54 UTC 2013


On Tue, Apr 2, 2013 at 4:28 AM, Miles Bader <miles at gnu.org> wrote:
> This bug was closed as "possibly fixed" in version 6.4.4, but 6.4.4
> still crashes for me, with what seems to be similar symptoms.
> One possibly differentiator:  I'm trying to run reportbug in a screen
> session, with DISPLAY unset, although my normal settings specify the
> GUI interface for reportbug.
> Although DISPLAY is unset, reportbug still attempts to start the GUI,
> resulting in a giant spew of python errors, and finally a "Floating
> Point Exception" (however, sometimes it's "Segmentation Fault").
> [I'm sending this report by explicitly specifying the "-utext" option]
> Maybe this is actually a different bug (if so, should I refile it?).

Yes, this is a completely different issue than the original one. Here
you're trying to use a graphical application while you can't do that
(DISPLAY is unset, either willfulness-ly or because on a tty).

I'm actually even unsure if it's the python GTK+ binding at fault
here, given I can import gtk but I can't use it.


Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

More information about the Reportbug-maint mailing list