Re: abrt problems with 2.4.3.1 (was moving over to 2.6.1)
Hi Paul, Hi All,
On 01/31/2010 01:53 PM, Paul wrote:
Looking on BZ, it seems that abrt is causing all sorts of mayhem
with
mono applications, yet I'm still to get a single report over problems
with 2.6.1 and abrt.
I don't think that's a fair comparison:
1. abrt does not work in RAWHIDE at all:
https://bugzilla.redhat.com/show_bug.cgi?id=557386
http://lists.fedoraproject.org/pipermail/devel/2010-January/129823.html
So it is logical that there are no abrt reports for 2.6.1. ;-)
2. The abrt reports for mono does not always point to a problem in mono.
I'm sure a fair amount is only related to the mono applications itself
(e.g. if an exception is not caught (library not found, etc.) then this
will also generate an abrt report for mono...)
Just as an example: there are a couple of mono abrt bugs which do all
refer to a problem in banshee with playing videos. And in this case the
problem is the same with mono 2.4. and 2.6 (just tried it out).
3. Most people use the stable distribution, not rawhide.
4. Lots of bug reports are caused by segfaults in the native libraries
like gtk/gdk:
e.g. https://bugzilla.redhat.com/show_bug.cgi?id=559992
Sorry, but I don't see much proof here which indicates that mono 2.6.1
is much more stable then 2.4.3.1.
I would say this is a good enough reason in itself to move f12 to
2.6.1
so can we have a definitive vote - all those who say yes, raise their
right hands, left foot and anything lumpy.
;-)
I'm still quite convinced that an update to 2.6.1 would be riskier than
it would solve all abrt problems.... So I would still like to vote to
stick with 2.4.3.1 in the stable distribution.
It would be better, if we would go through all of these abrt reports and
in all cases, where it looks like that the application itself is causing
the bug, to assign it to the maintainer of this application. They should
then take the appropriate step to upstream the bug report, ask how it
can be reproduced etc. ...
Best regards,
Christian