Help testing latest abrt-0.0.10-12.fc12

[Jiri Moskovcak]

On 11/03/2009 12:56 AM, Clyde E. Kunkel wrote:
> On 11/02/2009 02:27 PM, James Laska wrote:
>> Greetings,
>>
>> Jiri Moskovcak has asked for help testing the latest ABRT packages for
>> Fedora 12.
>
> <snip>
>>
>> 1. Confirm the fix for
>> https://bugzilla.redhat.com/show_bug.cgi?id=531347
>> 2. Kill a c/c++ application and see if abrt catches it -
>> https://fedoraproject.org/wiki/QA:Testcase_ABRT_CCPP
>
> Caught the crash, downloaded needed files for the report but refused to
> report saying that the bugzilla reporter plugin not properly
> configured.a Strange since I had configured it properly and used it
> successfully. Gave me an opportunity to populate the bz reporter fields
> and I did, but lost the entries somewhere saying field empty. Here is
> what appeared on the terminal:
> # abrt-gui
> Update >>Starting report creation...<<
> Our job for UUID 6e47676889724d39ebfb1e04e43281a441dec920 is done.
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Can't connect to Gnome Keyring daemon
> Update >>Starting report creation...<<
> Update >>Checking for duplicates...<<
> Update >>Bug is already reported: 532441<<
> Update >>Logging into bugzilla...<<
> Warning >>Report(): Empty login and password. Please check Bugzilla.conf<<
> Update >>Reporting via 'Bugzilla' was not successful: Empty login and
> password. Please check Bugzilla.conf<<
> Update >>Creating a report...<<
>
> So, looked in Bugzilla.conf and the entries were blank. Filled them in
> and retried, same results.
>
>

Abrt needs g-keyring to save/load passwords, this could happen when you 
run abrt-gui after you "$ su" to other user. If that was the case abrt 
failed to connect to keyring and tried to use the defaults from 
/etc/abrt/plugins/, please keep in mind that ~/.abrt/ is not used anymore.

>
>> 3. Introduce an unhandled python exception, and see if it catches
>> it - https://fedoraproject.org/wiki/QA:Testcase_ABRT_python
>
> got the crash...abrt didn't budge.
>

Maybe the old config file /etc/abrt/abrt.conf it should read:

EnabledPlugins = SQLite3, CCpp, Logger, Bugzilla, Python

You can try to run abrtd -d from console and watch for
abrtd: Plugin Python (0.0.1) succesfully loaded and check if you have 
abrt-addon-python installed (this should be pulled in by abrt-desktop):

rpm -q abrt-addon-python


>> 4. Report a crash to bugzilla -
>> https://fedoraproject.org/wiki/QA:Testcase_ABRT_Bugzilla
>
> Hmmmm....now working. Went back to 2 and resend and now it works.
>
>
> Here is what I think happened: the testing instructions for each case
> say "service abrt restart". This was not working and I didn't tumble to
> the fact that the instructions should have said "service abrtd restart".
> Once I did that then reporting worked. Repeated 3 properly and it still
> doesn't work.
>
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: jmoskovc.vcf
Type: text/x-vcard
Size: 134 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-test-list/attachments/20091103/3a62379d/attachment.vcf>