Bug 443527

Have you just used your root account? Is there a time out you have set? What does your /etc/sudoers look like? 

No, i am seldom using my root account.
If i need apps in rootmodus, i start them up.
That is why it struck me that yast2 comes without pw requester sometimes, it allways asked for it as long as i can remember..
At first  my 32 bit system had it, and now my 64 bit also, since the last update.

Default, never changed it.

# Defaults specification

# Prevent environment variables from influencing programs in an
# unexpected or harmful way (CVE-2005-2959, CVE-2005-4158, CVE-2006-0151)
Defaults always_set_home
Defaults env_reset
# Change env_reset to !env_reset in previous line to keep all environment variables
# Following list will no longer be necessary after this change

Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE"
# Comment out the preceding line and uncomment the following one if you need
# to use special input methods. This may allow users to compromise  the root
# account if they are allowed to run commands without authentication.
#Defaults env_keep = "LANG LC_ADDRESS LC_CTYPE LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE LINGUAS XDG_SESSION_COOKIE XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"

# In the default (unconfigured) configuration, sudo asks for the root password.
# This allows use of an ordinary user account for administration of a freshly
# installed system. When configuring sudo, delete the two
# following lines:
Defaults targetpw   # ask for the password of the target user i.e. root
ALL	ALL=(ALL) ALL   # WARNING! Only use this together with 'Defaults targetpw'!

# Runas alias specification

# User privilege specification
root	ALL=(ALL) ALL

# Uncomment to allow people in group wheel to run all commands
# %wheel	ALL=(ALL) ALL

# Same thing without a password
# %wheel	ALL=(ALL) NOPASSWD: ALL

# Samples
# %users  ALL=/sbin/mount /cdrom,/sbin/umount /cdrom
# %users  localhost=/sbin/shutdown -h now

What environment are we talking about? KDE (what version)? GNOME? Some other window manager? Just shell?

OS:  Linux 2.6.27.5-1-default x86_64
  Huidige gebruiker:  oddball@AMD64x2-sfn1
  Systeem:  openSUSE 11.1 Beta 4.6 (x86_64)
  KDE:  4.1.3 (KDE 4.1.3) "release 1.3"

It is mostly when i call systemmanagement, itc: Yast2.
A passwordrequester should appear before the config screen appears, but if i once filled in my rootpw, am finished, close yast2, but open it after some time, it opens without asking for rootpw again.
This i find strange...

OK, but how do you call it? From an xterm, or from GUI menu?

In this case it happens when using gui.

Well, you're still not making yourself clear. You can run yast GUI from both command line (xterm) and a GUI menu (the KDE application launcher). So i _guess_ you run yast from the KDE launcher, is that right?

In that case, yast logs would help. Please try to reproduce it and attach yast logs right after it happens.

Also note that the dialog for entering root password has a checkbox saying 'Remember password'. Have you checked that before?

(In reply to comment #7 from Ján Kupec)
> Well, you're still not making yourself clear. You can run yast GUI from both
> command line (xterm) and a GUI menu (the KDE application launcher). So i
> _guess_ you run yast from the KDE launcher, is that right?

The wrench with the yellow handle on the taskbar i use since in kde4.1 it is not yet very clear to me how to set a keyboard shortcut...
> 
> In that case, yast logs would help. Please try to reproduce it and attach yast
> logs right after it happens.
> 

I just updated to OS:  Linux 2.6.27.5-2-default x86_64
  Huidige gebruiker:  oddball@AMD64x2-sfn1
  Systeem:  openSUSE 11.1 Beta 5.1 (x86_64)
  KDE:  4.1.3 (KDE 4.1.3) "release 2.1"

> Also note that the dialog for entering root password has a checkbox saying
> 'Remember password'. Have you checked that before?
> 

No i never check that box, as i noticed earlier (since suse 9.2) that it won't remember it, and i think it is not sane or safe if it would.
I don't mind typing my pw to get root, in fact. i am so used to it, that if i am not asked i am surprised;) 

(In reply to comment #8 from Robby Verberne)
> (In reply to comment #7 from Ján Kupec)
> > In that case, yast logs would help. Please try to reproduce it and attach
> > yast logs right after it happens.
> > 
> 
> I just updated to OS:  Linux 2.6.27.5-2-default x86_64
>   Huidige gebruiker:  oddball@AMD64x2-sfn1
>   Systeem:  openSUSE 11.1 Beta 5.1 (x86_64)
>   KDE:  4.1.3 (KDE 4.1.3) "release 2.1"

Nice but this is not what i was asking for :O) I asked you to reproduce the problem and attach yast logs right after it happens. You neither did say whether you reproduced it nor you attached the logs (see http://en.opensuse.org/Bugs/YaST if you don't know which logs to attach).

(In reply to comment #9 from Jan Kupec)

> 
> Nice but this is not what i was asking for :O) I asked you to reproduce the
> problem and attach yast logs right after it happens. You neither did say
> whether you reproduced it nor you attached the logs (see
> http://en.opensuse.org/Bugs/YaST if you don't know which logs to attach).
> 

Indeed, it is not.
But what i was trying to say is, if it still persists;)
As soon as it happens again, i'll attach the logs.
I have an older log available, but i don't know if it meets your expectations, i'll attach it anyhow.

Created attachment 253913 [details]
yast2.tar.bz2 64bit

Oook.. now i realized yast logs won't help us, since the problem is _before_ actually starting it :O) sorry.

The problem must be somewhere in the sudo system or kdesu (the graphical root password dialog). If it happens again, please try to open an xterm and call 'kdesu yast2' (or any other application (except a virus :O)) as user, and tell us whether that asked for password or not.

I did not notice this anymore on both boxes.
Will close for now, and reopen if nessesary.