[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

ABRT for f12 status



Hi internets,

I was looking at the current state of ABRT (I tested on F11).  The
core capturing seems to work well.  In brief, I propose to apply the
(attached) patch to comps-f12.xml.in.

For upgrades, we'll need to add a Conflicts: bug-buddy, correct?

ABRT is a big step forward from bug-buddy in that the crashes are
stored sanely in a persistent manner, and it captures crashes in the
core OS as well.

Concerns:

== Getting the Data ==
My main concern is ensuring that we get the data reliably to the eyes
of Fedora developers.  The current abrt-desktop virtual package[1]
depends on abrt-plugin-bugzilla, which has a default BugzillaURL =
https://bugzilla.redhat.com/.  To be able to successfully submit data,
you have to go to:  Edit->Preferences, click Bugzilla, click
"Configure Plugin" and enter a username/password; there's no provision
for creating a Bugzilla account here.

I suggest that Fedora infrastructure instead provide a service where
the data in /var/cache/abrt can be submitted via HTTP post as a
tarball, anonymously.  Then the crash UI can be just

"A problem has been detected in [whatever].  Do you want to send this
data to Fedora? [Submit] [ See Data ] [ Cancel ]":

On the server side then we can later write tools to analyze the crash
data (reuse kerneloops?  socorro?  write custom code?).

Secondary concerns:

== kernel/GNOME developer feedback ==

We should ensure Fedora is still sending crashes from the kernel to
kerneloops.org; does ABRT handle this?  Also, ideally on the server
side there would be a web page where a GNOME developer (hi!) could go
to http://crashes.fedoraproject.org/package/gnome-panel and see a list
of crashes sorted by number.

== Privacy ==

ABRT needs some explanation that the crash data may contain private
information.  We may need to restrict visibility of the data to only
Fedora account holders by default or the like, to at least prevent any
future effects like a Slashdot link to a trace where the submitter was
viewing pornography or the like (yes, this happened with GNOME
bugzilla).

But in general, thanks for the work on ABRT, we should get this in by
default for the F12 desktop target.

[1] For RPM/dependency graph people: Why does this exist?  I thought
virtual packages were disallowed?  Should just be in comps I think.
Index: comps-f12.xml.in
===================================================================
RCS file: /cvs/pkgs/comps/comps-f12.xml.in,v
retrieving revision 1.98
diff -u -r1.98 comps-f12.xml.in
--- comps-f12.xml.in	27 Aug 2009 14:49:40 -0000	1.98
+++ comps-f12.xml.in	28 Aug 2009 21:13:54 -0000
@@ -360,7 +360,7 @@
       <packagereq type="default">firstboot</packagereq>
       <packagereq type="default">glx-utils</packagereq>
       <packagereq type="default">gnome-packagekit</packagereq>
-      <packagereq type="default">kerneloops</packagereq>
+      <packagereq type="default">abrt-desktop</packagereq>
       <packagereq type="default">krb5-auth-dialog</packagereq>
       <packagereq type="default">openssh-askpass</packagereq>
       <packagereq type="default">plymouth-system-theme</packagereq>
@@ -2462,7 +2462,6 @@
       <packagereq type="conditional" requires="scim">scim-bridge-gtk</packagereq>
       <packagereq type="default">at-spi</packagereq>
       <packagereq type="default">brasero-nautilus</packagereq>
-      <packagereq type="default">bug-buddy</packagereq>
       <packagereq type="default">cheese</packagereq>
       <packagereq type="default">compiz-gnome</packagereq>
       <packagereq type="default">dasher</packagereq>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]