[Reportbug-maint] Bug#620225: GTK+ UI errors: segfaults, floating-point exceptions, pango error

Sandro Tosi morph at debian.org
Sat Oct 15 08:42:40 UTC 2011


GTK+ UI doesn't crash for anyone, but only for a minor part of its
users. So stop whining or do something to get this fixed. End of the
story.

On Sat, Oct 15, 2011 at 10:33, Camaleón <noelamac at gmail.com> wrote:
> 2011/10/14 Sandro Tosi <morph at debian.org>:
>> On Fri, Oct 14, 2011 at 22:32, Camaleón <noelamac at gmail.com> wrote:
>>> [27738.795946] reportbug[5947]: segfault at b51fc000 ip b63d29ca sp bf968f98
>>> error 4 in libgdk-x11-2.0.so.0.2400.4[b63a5000+98000]
>>
>> As you can probably guess, a segfault in libgdk is none of reportbug
>> fault. GTK+ stack maintainers are not interested in debugging this
>> issue and none of the maintainer of reportbug can replicate it. We're
>> stuck.
>
> If GTK+ maintaintainers are not interested in dealing with these
> problems (?) which in the end render reportbug unusable when you use
> the GTK+ UI, then why not removing that option? I wonder what could be
> the reason for keeping an option that depends on something that cannot
> be reported against.
>
> It's a waste of time (for bug reporters and for reportbug maintainers)
> having a GTK+ UI that breaks in almost every launch, so why not
> removing the UI entry from the menu and set the default to something
> that a) does not crash so often and b) can be properly debugged when
> it does?
>
> I am referring, of course, to change the "--ui gtk2" from reportbug
> ".desktop" file and make it run on the default console by means of
> "--ui text". Also, adding a BIG warning in reportbug man page where
> the user can read the "--ui gtk2" crashes very often and most of the
> time cannot be properly debugged so better not using it.
>
> --
> Camaleón
>



-- 
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