Comment 51 for bug 270781

Revision history for this message
In , Marius (marius-redhat-bugs) wrote :

The app that corrupted /dev/null is Vodafone Mobile Connect client, installed with the package vodafone-mobile-connect-1.99.17-8.noarch. I didn't used it, therefore the issue dissapeared.

I have pam updated to the latest version: pam-1.0.4-4.fc10.i386.

Now, testing again by corrupting /dev/null char device:

# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 2009-04-18 14:59 /dev/null
#
# rm -f /dev/null; touch /dev/null; ls -l /dev/null
-rw-r--r-- 1 root root 0 2009-04-20 15:04 /dev/null
#

"Lock Screen" works fine! No related messages are generated in /var/log/messages or /var/log/secure. I just created back the device as designed:

# ls -l /dev/null
-rw-r--r-- 1 root root 0 2009-04-20 15:04 /dev/null
#
# rm -f /dev/null; mknod -m 666 /dev/null c 1 3
#
# ls -l /dev/null
crw-rw-rw- 1 root root 1, 3 2009-04-20 15:12 /dev/null
#

I consider this problem solved!
Again, thank you very much for the support and the quick feedback. It was a pleasure to help the community support to improve the experience!

Keep up the good work!