(→How to install ABRT)
|Line 212:||Line 212:|
| [[User:twaugh]] || Catching Python traceback
| [[User:twaugh]] || Catching Python traceback
Revision as of 14:37, 20 August 2009
|2009-08-20||From 12:00 to 21:00 UTC (8am - 5pm EDT, 14:00 - 23:00 CET)||#fedora-test-day (webirc)|
What to test?
Today's installment of Fedora Test Day will focus on Automated Bug Reporting Tool (ABRT). This tool should help non-power users with bug reporting, making it as easy as a few mouse clicks. ABRT is a daemon that watches for application crashes. When a crash occurs, it collects the crash data (core file, application's command line etc.) and takes action according to the type of application that crashed and according to the configuration in the abrt.conf configuration file. Bottom line: do not hunt the bugs with a pitchforks, rather use bugzappers/big light source to draw them from the dark and kill them easily at close range.
ABRT should be easy for users and very useful for developers and admins. Ease of crash/bug reporting and quick response from maintainers based on info from ABRT should make Fedora more stable and thus more attractive for users.
The following people will be available for testing, workarounds, bug fixes, and general discussion:
- Development - Zdeněk Přikryl (zprikryl), Jiří Moskovčák (jmoskovc)
- Quality Assurance - David Pravec (dpravec), Kamil Páral (kparal), James Laska (jlaska), Michal Nowak (mnowak)
What's needed to be able to test
- A system with some kind of network connection
- Fully updated Rawhide or Fedora 11 installation with ABRT installed or special ABRT TestDay Live image (i686 or x86_64)
How to install ABRT
If you do not use the provided LiveCD, but you use your own Fedora 11 or Rawhide installation, you need to install latest ABRT packages by running following commands:
First add correct repository:
- Fedora 11:
curl -o /etc/yum.repos.d/abrt.repo http://jmoskovc.fedorapeople.org/abrt.repo
curl -o /etc/yum.repos.d/abrt-rawhide.repo http://jmoskovc.fedorapeople.org/abrt-rawhide.repo
Now install/update ABRT:
su rm -f /var/cache/abrt/abrt-db yum remove kerneloops yum install abrt-desktop reboot
Please do not forget to reboot. It's needed after installing ABRT.
Optionally, you may download a non-destructive rawhide live image for your architecture with latest ABRT pre-installed. Tips on using a live image are available at FedoraLiveCD. For Fedora on USB flash disk consult FedoraLiveCD/USBHowTo.
How to test
Follow each of following ABRT Test Cases and sum up the results in the tables below. Report your findings also in Bugzilla or ABRT Trac (enter FAS username/password). Please provide links to bugreports in results table.
- QA:Testcase_ABRT - default crash report
- QA:Testcase_ABRT_Logger - Logger plugin
- QA:Testcase_ABRT_Bugzilla - Bugzilla plugin
- QA:Testcase_ABRT_Mailx - Mailx plugin
- QA:TestCase ABRT BlackList - package blacklist
- QA:Testcase ABRT GPG check - reporting crashes of signed packages only
- QA:TestCase ABRT GPG Keys - additional keys for signing packages
- QA:Testcase ABRT Actions and Reporters - testing of action/reporting plugins
- QA:Testcase ABRT Cron - periodical plugins using Cron
- QA:Testcase ABRT Plugins - configuring plugins
- QA:Testcase ABRT CLI - CLI interface
- QA:Testcase ABRT kernel - kernel oops
- QA:Testcase ABRT python - python tracebacks
Consult list of active tickets before reporting an issue. The most common issues are listed below:
- Applet (or other icons) in notification area is not visible - that's a known bug in Rawhide, please try to run
killall notification-area-appletand reload it a few times, it may help
- Recreate report for same crash - if you want to recreate a report of same crash, you have to delete it using button in GUI and make a crash gain
- Nothing happened? - if it seems to do nothing, try to disable PGP checking and restart daemon
- Graphical warnings - gui writes some gtk warnings (it's gtk's fault)
- rpm %requires - it needs rpm >= 4.7.0-1
- bug-buddy or other crash catching tools might take precedence over ABRT if you are using them. ABRT will catch only crashes which are not caught by other tools.
- Cannot catch OpenOffice.org, KDE and Java - these applications have a built-in method for capturing failures so it is the same as with BugBuddy etc.
- if you're updating from version <= 0.0.5-6 - make sure you remove /var/cache/abrt/abrt-db (we've changed the db format and not yet implemented automatic updating mechanism)
- GUI doesn't inform you about success of failure of a reporting. - But you can find results in ABRT's db (default path /var/cache/abrt, it is sqlite3 db, table name is "abrt") - it should be fixed, but in case it's not try to look for these files
Issues that were identified
Don't report duplicates, thanks :) Just write a comment to the bugzilla that you have also noticed the bug.
|Tester||Description||Bug references||BZ status|
|User:kparal||Right click on applet hides the applet but does nothing||RHBZ #518386|
|User:guaneryu||OpenGPGCheck option takes no effect||RHBZ #518396|
|User:czhang||testcase #1: no item can be selected after clicked abrt-gui icon if other user's application crashes.||RHBZ #518409||CLOSED NOTABUG|
|User:mhlavink||continuous reporting of one kernel oops||RHBZ #518413|
|User:mhlavink||ordinary user's applet shows up for root owned crashes||RHBZ #518420|
|User:mhlavink||abrt silently starts when plugin is configured but not installed||RHBZ #518422|
|User:hdong||testcase #8: CCpp:<APPNAME> doesn't work||RHBZ #518414|
|User:azelinka||report window larger that screen (no horizontal scrolling)||RHBZ #518425|
|User:azelinka||bugzilla plugin can't detect correct component for a bug||RHBZ #518438|
|User:tpelka||RunApp do not work - abrt-plugin-runapp installed||RHBZ #518465|
|User:tpelka||cannot use # in bugzilla password||RHBZ #518459|
|User:dpravec||it would be nice for some admins to be able to catch and process crashes of theirs own compiled (unpackaged, unsigned) applications. Not for Bugzilla plugin, but for some custom reporting/actions.||Trac#73|
|User:dpravec||when abrt is upgrading from older version, the old database is making it confused. Dont force users to rm the file manually, detect this during upgrade and migrate the database, or just backup it.||Trac#74|
|User:tpelka||Wouldn't be cool use keyring except plaintext passwords?||TBD|
|User:azelinka||user configuration of plugins doesn't survive service restart||RHBZ #518457|
Things that work alright
|User:kparal||testcase #1 worked ok|
|User:czhang||testcase #2~#5, #9~#12 work as what expected.|
|User:twaugh||Catching Python traceback|
|User:mvadkert||testcase #2~#5 work as what expected.|