Description of problem: Following january 26th updates, ABRT does not start Version-Release number of selected component (if applicable): abrt-libs-1.0.4-1.fc12.i686 abrt-1.0.4-1.fc12.i686 abrt-addon-python-1.0.4-1.fc12.i686 abrt-plugin-bugzilla-1.0.4-1.fc12.i686 abrt-plugin-runapp-1.0.4-1.fc12.i686 abrt-gui-1.0.4-1.fc12.i686 abrt-addon-kerneloops-1.0.4-1.fc12.i686 abrt-plugin-logger-1.0.4-1.fc12.i686 abrt-addon-ccpp-1.0.4-1.fc12.i686 abrt-desktop-1.0.4-1.fc12.i686 How reproducible: Solid Steps to Reproduce: 1. Just reboot and look at in /var/log/messages 2. 3. Actual results: abrtd: can't load '/usr/lib/abrt/lib.so': /usr/lib/abrt/lib.so: Ne peut ouvrir le fichier d'objet partagé: Aucun fichier ou dossier de ce type Expected results: n/a Additional info: n/a
When trying to debug this, "service abrtd [re]start" would fail with "Registered Database plugin 'SQLite3'" followed by "can't load '/usr/lib64/abrt/lib.so': /usr/lib64/abrt/lib.so: cannot open shared object file: No such file or directory" Tried "abrt" (by mistake) followed by "abrt -f" <- One of these 'fixed' whatever was wrong and now "service abrtd [re]start" works
I downgraded to 1.0.3-1 and this fixed my problem. I upgraded a new time to 1.0.4-1 and I got the same problem again. I do not understand how you fixed this problem. Under my understanding there is no abrt command but just the abrtd daemon.
There were typos in Comment 1 To clarify, at a bash prompt, type: abrtd I then killed that job and restarted it with: abrtd -f This command runs abrtd in the foreground and displays messages on stdout It indicated that abrtd was Running Surprised, I killed that job, then ran: service abrtd restart which started successfully
Thanks Thom. I had the same problem and repeated your steps and it fixed my problem. The only difference was I used: # abrtd followed by # abrtd -d I guess that this could be a language problem.
Paul, you are right. I was flipping between screens in both cases. Interestingly, the problem did not occur on a similarly configured system. At least now there is a workaround...
Removed all abrt packages and reinstalled them. Now comes back up after reboot with abrtd running with no error (no RED siren icon and no error in var/log/messages). Wasn't sure which ones were previously installed so reinstalled them all: abrt-plugin-logger-1.0.4-1.fc12.x86_64 abrt-libs-1.0.4-1.fc12.x86_64 abrt-addon-python-1.0.4-1.fc12.x86_64 abrt-addon-ccpp-1.0.4-1.fc12.x86_64 abrt-plugin-bugzilla-1.0.4-1.fc12.x86_64 abrt-plugin-catcut-1.0.4-1.fc12.x86_64 abrt-gui-1.0.4-1.fc12.x86_64 abrt-plugin-mailx-1.0.4-1.fc12.x86_64 abrt-cli-1.0.4-1.fc12.x86_64 abrt-addon-kerneloops-1.0.4-1.fc12.x86_64 abrt-plugin-filetransfer-1.0.4-1.fc12.x86_64 abrt-desktop-1.0.4-1.fc12.x86_64 abrt-libs-1.0.4-1.fc12.i686 abrt-plugin-ticketuploader-1.0.4-1.fc12.x86_64 abrt-plugin-runapp-1.0.4-1.fc12.x86_64 abrt-1.0.4-1.fc12.x86_64 abrt-plugin-sosreport-1.0.4-1.fc12.x86_64
*** This bug has been marked as a duplicate of bug 560642 ***