Hello, On Tue, Apr 2, 2013 at 4:28 AM, Miles Bader <[email protected]> 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. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi _______________________________________________ Reportbug-maint mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reportbug-maint
