I tried it with a UID 1001:
root:> chmod o-r /etc/shadow
MyUserName:> su - jstest
works:
Jan 22 08:38:48 xpcubXYZ su[10286]: Successful su for jstest by MyUserName
Jan 22 08:38:48 xpcubXYZ su[10286]: + /dev/pts/0 MyUserName:jstest
Jan 22 08:38:48 xpcubXYZ su[10286]: pam_unix(su:session): sessio
On Di, Jan 19, 2010 at 02:26:50 - Chris Coulson wrote:
> Does anything get logged in /var/log/syslog when you try to unlock the
> screen?
Yes, i have anonimized it a bit
Jan 19 09:12:11 xpcubXYZ gnome-screensaver-dialog:
pam_unix(gnome-screensaver:auth): unix_chkpwd abnormal exit: 11
Jan 19
I got the hint here:
https://bugzilla.novell.com/show_bug.cgi?id=204364#c22
Hello Caudio, maybe friday I had 2 hours to try to reinstall some gnome
packages at my pc at work.
Now I'm at home with the same revision. Here genome-screensaver unlocks
fine (but here I have a german keybord, here is De
Shit I got it.
ro...@pcub255:/root> ll /etc/shadow
-rw-r- 1 root shadow 1,5K 2010-01-12 11:32 /etc/shadow
ro...@pcub255:/root> chmod a+r /etc/shadow
I found it in a suse forum. It is really ugly to open the permissions.
Before karmic it works.
Jürgen
--
[Karmic] gnome-screensaver does not
I have the same problem in karmic. Also in xscreensaver where I come from.
I run fvwm not gnome.
Behind the password field I see a "GBr" which I can change to "??"
I think this is the keyboard level. Yes I try both.
If I switch to "??" and kill the screensaver the xterm left the way the AltGr
