Bug 623593

Description of problem:

Well the Idea here is when an end user installs or updates and package and that update/install triggers warning or errors abrt would detect that and allow the end user to file bug report against that component. 

So when it encounters an error it takes the component and the release and the error from yum.log? and offers the end user to report that to bugzilla.

Note these needs to cats bugs encounter either by running yum via cli or if it's run by some graphical tool like packagekit.

To give you an hint on how many bugs it can catch and ease the reporters life 
the following 7 bugs were encountered in last nights-compose...

Installing: fedora-release-notes         ################### [  83/1077]/var/tmp/rpm-tmp.bsyB7L: line 2: touch: command not found

Installing: plymouth-theme-charge        ################### [ 635/1077]warning: %post(plymouth-theme-charge-0.8.4-0.20100723.1.fc14.i686) scriptlet failed, exit status 1 

Installing: nautilus                     ################### [ 939/1077]WARNING: Failed to parse default value `' for schema (/schemas/apps/nautilus/preferences/navigation_window_saved_maximized)

Installing: empathy                      ################### [1042/1077]I/O warning : failed to load external entity "/etc/gconf/schemas/empathy.schemas"
Failed to open `/etc/gconf/schemas/empathy.schemas': No such file or directory

Installing: simple-scan                  ################### [1053/1077]gconfd-2: no process found

Installing: gnome-panel                  ################### [1068/1077]I/O warning : failed to load external entity "/etc/gconf/schemas/notification_area_applet.schemas"
Failed to open `/etc/gconf/schemas/notification_area_applet.schemas': No such file or directory

Installing: gnome-panel                  ################### [1068/1077]I/O warning : failed to load external entity "/etc/gconf/schemas/notification_area_applet.schemas"
Failed to open `/etc/gconf/schemas/notification_area_applet.schemas': No such file or directory
 
Watch out for legit warnings. . . 

Installing: plymouth                     ################### [ 918/1077]warning: /etc/dracut.conf created as /etc/dracut.conf.rpmnew

If package was used to install or update then all the 7 above errors would get unreported. 

Reporters only encounter these errors if they run yum from cli and are actually watching it while it's installing/updating and then it's on a whim if the reporter would file it. 

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: