Description of problem: gdm[XXXX]: (null): cannot open shared object file: No such file or directory Version-Release number of selected component (if applicable): 2.16.0 How reproducible: always present in /var/log/messages after system boot Steps to Reproduce: 1.boot system 2.grep "(null)" /var/log/messages 3. Actual results: gdm[XXXX]: (null): cannot open shared object file: No such file or directory Expected results: no oputput expected from grep Additional info: Fedora Core 6 -> https://bugzilla.redhat.com/show_bug.cgi?id=221835
Sixteen months on and not even acknowledged. :-( So have a bump.
Hi Alan, What is output of rpm -q gdm coolkey pam_pkcs11 pcsc-lite ?
(In reply to comment #2) > Hi Alan, > > What is output of > > rpm -q gdm coolkey pam_pkcs11 pcsc-lite > > > ? Ray, My apologies for the delay in attending to this. The notification e-mail was somehow missed by me. Sorry. I should say that this issue is now historic and can be closed as "fixed in update" (or whatever is considered to be appropriate). For completeness, this is the event time-line -- Installed 5.0 and (eventually) noticed the message in the log file. Did nothing about investigating it. Ooops. Updated to 5.1 and rediscovered the message. Opened this bug report. On talking with a Fedora hacker, I was advised to install the coolkey package (but didn't do so). Sometime between the update to 5.1 and the subsequent update to 5.2 the coolkey package was installed as a requirement of yet another package. As a result, this issue was fixed. So, in essence, it appears that there was a problem with the original 5.0 installation as it did not install the coolkey package as a requirement. Regards, Alan.
Alright, thanks.