Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => dirteat

Hi there,
could you give a test case such that I can reproduce. I don't see any of those locally.

Thanks!
cheers,
chris.

First you need Mageia 2 (just to be sure you are not testing on Mageia 3 or Cauldron :P). Then I don't know exactly the conditions, it's quite common to see the message.

Since it seems that my link above to the patch is no longer valid, I think the best is looking up the exact error message in a search engine. It shows the exact problem in fedora, suse, debian. Tell me if it's enough information for you, otherwise I'll try to dig more (it's been one year since I created the bug report, I've forgotten the details :))

Here you go,
new pam_mount is landing in updates_testing, please check that you don't get anymore this message in the logs.

Suggested advisory:
========================

Updated pam_mount packages to fix spurious log messages at each login.

========================

Updated packages in core/updates_testing:
========================

lib(64)cryptmount0-2.13-1.2.mga4
pam_mount-2.13-1.2.mga4
lib(64)cryptmount-devel-2.13-1.2.mga4

Cheers.

Assignee: dirteat => qa-bugs

By the way, if someone sees that on mga3, complain here.
In the meanwhile, I won't push anything if the virgin Mary of computing has magically muted those log messages on mga3 :)

CC: (none) => dirteat

Did you mean mga2 for the packages Chris?

Oops, sorry!! Yes

lib(64)cryptmount0-2.13-1.2.mga2
pam_mount-2.13-1.2.mga2
lib(64)cryptmount-devel-2.13-1.2.mga2

Testing on mga2 x86_64, I've got a problem. The update solves the bug it is supposed to solve, but I get a new error message, as if the behaviour of pam_mount had changed with this update.

Here is log with pam_mount from core_updates (don't worry about the errors, I think I have a poorly designed pam_mount configuration, so it fails because the directories are already mounted)

tech009 login: samuel.verschelde
Password:
ehd_logctl: feature 1 is already zero
ehd_logctl: feature 1 is already zero
(mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(16): Device or resource busy
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
(pam_mount.c:522): mount of production failed
(mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(16): Device or resource busy
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
(pam_mount.c:522): mount of general failed

With new pam_mount:
tech009 login: samuel.verschelde
Password:
(pam_mount.c:101): unknown pam_mount option "use_first_pass"
(mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(16): Device or resource busy
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
(pam_mount.c:522): mount of production failed
(mount.c:68): Messages from underlying mount program:
(mount.c:72): mount error(16): Device or resource busy
(mount.c:72): Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
(pam_mount.c:522): mount of general failed

See new message? "(pam_mount.c:101): unknown pam_mount option "use_first_pass"". That looks like a behaviour change. Or maybe the "use_first_pass" option already was incorrect but the bug prevented the message to show up?

Whiteboard: (none) => feedback

According to https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/332833 use_first_pass is deprecated, so it is actually better that pam_mount shows the message now.

Testing complete on MGA x86_64

Whiteboard: feedback => MGA2-64-OK

The package's documentation still mentions use_first_pass (man page, faq...), so I had no choice but to open you a new bug report :), see bug 11085

Don't know if patches exist for that.

Hi there,
bug reported upstream; although in faq.txt, there is an explicit mention of it which more or less ask to user to RTFM if use_first_pass does not work:


+     The exact option name for other modules may be different from
+    "use_first_pass", so be sure to check their documentation.


Unless the developper makes some effort, that bug has a low probability of being solved soon....

Cheers.

Testing complete mga2 32

I didn't notice any errors by just having this installed so I think it must require a particular use case. Done reboots, ssh login, tty login, root/user etc.

No regressions noticed after updating and given Samuel says it's ok for him, testing complete mga2 32.

Whiteboard: MGA2-64-OK => MGA2-64-OK mga2-32-ok

SRPM: pam_mount-2.13-1.2.mga2.src.rpm

Validating. Advisory uploaded.

Could sysadmin please push from 2 core/updates_testing to updates

Thanks!

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Update pushed:
http://advisories.mageia.org/MGAA-2013-0092.html

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED