Version: (using KDE KDE 3.4.2) Installed from: Debian testing/unstable Packages OS: Linux A recent commit to SVN, 432431, in which the amount of code run in kdm as 'nobody' was increased, has had the following curious effect. User faces set by the admin (/usr/share/apps/kdm/faces/whatever) work, but faces set by the user, $HOME/.face.icon, aren't displayed. Reducing the amount of code run as 'nobody' fixes this. I'll attach the patch that did this. That said, I didn't look too closely for the exact reason why increasing and decreasing the code run as 'nobody' has had these effects. This problem appears to be different from Bug 108257 (I couldn't figure out that guy's problem either when he reported it, and he first mentioned it long before the recent 'nobody' commit), but perhaps they are related. Perhaps not. Thanks, Christopher Martin
Created attachment 12225 [details] Patch which seems to fix this bug.
not a bug. see http://lists.kde.org/?l=kde-core-devel&m=112091390101721&w=2 and the rest of the thread.
Related to this report: When setting user face images in the login manager section of kcontrol in administrator mode, the permissions on the files put in $KDEHOME/share/apps/kdm/faces are sometimes not set correctly (e.g. if your umask is set restrictively). If the user.face.icon is not readable by nobody, it won't show up (or the default will show if it has correct permissions). When user face.icons are created, the permissions should probably be set explicitly to world-readable. I was going to report this as a separate bug but there were a lot of invalid/duplicate reports about user faces based on misconfigurations of KDM and wasn't sure if I should contribute to the mess.
re comment 3: fixed
*** Bug 135181 has been marked as a duplicate of this bug. ***