On Thu, Sep 10, 2009 at 8:58 PM, Matthias Clasen <mclasen@xxxxxxxxxx> wrote: > On Thu, 2009-09-10 at 19:39 -0400, Paul W. Frields wrote: >> On Thu, Sep 10, 2009 at 06:57:43PM -0400, Matthias Clasen wrote: >> > On Thu, 2009-09-10 at 18:40 -0400, Tom "spot" Callaway wrote: >> > > On 09/10/2009 06:36 PM, Matthias Clasen wrote: >> > > > should get rid of it. The harder question is where to put that >> > > > command... >> > > >> > > %post for abrt-gui ? :) >> > >> > That doesn't help, since the gconf key is in your users gconf db. The >> > command has to be run inside your session to have the desired effect. >> > >> > Conceivably, abrt-applet could do it on startup. >> >> The fix, workaround, or decision not to provide either should >> definitely get a mention in the release notes. Just edit the wiki >> here: >> >> https://fedoraproject.org/wiki/Documentation_Desktop_Beat >> > > Yeah, I think I am just going to document the manual fix. It looks like > bug-buddy installs the schema for that key with a default of true, so > you will only have the key in your own GConf db if you manually modified > it - and if you did that, then you most likely set it to false, > anyway... > On second thought, this might not be such a great problem. I had a bug-buddy installation from F-11, and at some point installed bug-buddy.i686 so that running 32-bit GTK applications do not cause breakpad warnings. The bizarre thing is that after installing abrt-gui, somehow bug-buddy.i686 was still present. Removing bug-buddy completely solves the problem. -- Michel Alexandre Salim -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
