Greetings, I am experiencing an annoying problem with pam. I have an encrypted file system that is mounted at system boot time. I am using the standard mapper crypto_luks encryption. At boot time, the system asks for a password to unlock and mount this filesystem. When I provide the password I get an error message (something about modprobe not finding or loading a module). However, when the system is fully booted, the encrypted filesystem is actually mounted and works fine. The error at boot time seems bogus. The other thing is I see password - KDE daemon window asking me for a password to unlock the encrypted file system that is already mounted! I have only one encrypted filesystem so this dialog is bogus too. Now, if I do not provide a password to unlock the crypto_luks file system at boot time, the system eventually completes booting up and I can log in and of course the encrypted file system is not mounted. If I go to Dolphin and click on the encrypted file system and provide the password it fails and I cannot mount this file system! Seems like something is broken. I have all packages updated to the most current versions so it must be something else that is broken. Anyone experience this or have an idea where to look to fix this? Thanks, Vahe Avedissian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org