Created attachment 712071 [details] gzip'd tar of the named abrt files Description of problem: Troubleshooter will not come up (posts notification) and system log displayer will not come up - working before this update today (3/18/13) - new kernel 3.8.3-201.fc18.x86_64. Version-Release number of selected component (if applicable): not sure How reproducible: Consistent everytime. Steps to Reproduce: 1. attempt to bring up either system-tools: SELinux Troubleshooter or System Log Actual results: troubleshooter posts an error and notifies me - that's ALL System-log asks for my password (me==admin) - accepts it, then nothing happens Expected results: both tools were working before this mornings "yum update" and reboot Additional info: Not sure if this is the right stuff, but I see this in /var/log/messages Mar 18 11:29:43 rainbow dbus-daemon[579]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Mar 18 11:29:43 rainbow dbus-daemon[579]: ** Message: entering main loop Mar 18 11:30:14 rainbow dbus-daemon[579]: ** Message: No devices in use, exit Mar 18 11:30:32 rainbow abrt: detected unhandled Python exception in '/usr/bin/sealert' Mar 18 11:30:32 rainbow abrtd: New client connected Mar 18 11:30:32 rainbow abrtd: Directory 'pyhook-2013-03-18-11:30:32-2502' creation detected Mar 18 11:30:32 rainbow abrt-server[2505]: Saved problem directory of pid 2502 to '/var/spool/abrt/pyhook-2013-03-18-11:30:32-2502' Mar 18 11:30:32 rainbow abrtd: Duplicate: core backtrace Mar 18 11:30:32 rainbow abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2013-03-18-11:27:41-2415 dump of directory named included, not sure what else to do or try
updated using yum today - troubleshooter (more important) WORKS now, system-log viewer still dead (work around is to view /var/log/messages so not as bad)
new yum update today 3/28/13 - problem persists (trouble shooter seems OK, but cannot bring up System Tools -> System Log - asks for my password and then nothing more happens workaround - look at /var/log/messages
3/31/13 yum update run - reboot and problem persists
4/5 -3.8.5-201.fc18.x86_64 update - no change
Just checked again 6/10/2013 after another yum update: troubleshooter ok, system log still dead will continue to check after yum updates (weekly minimum)
7/1/2013 - system log viewer still does not come up (asks password and stops) This leaves vim as the only tool. I tried tail -s /var/log/messages while I did this: Jul 1 10:54:36 rainbow dbus-daemon[606]: ** Message: entering main loop Jul 1 10:55:06 rainbow dbus-daemon[606]: ** Message: No devices in use, exit This does not help me and looks irrelevant, but maybe it has meaning to you.
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle. Changing version to '20'. More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20
Now running Fedora 20 - 64 and 32 bit versions trouble shooter works fine system log views NOT so good window comes up to get authorization End of Story I had used this tool before, now just using vim - oh wel
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.