Extraneous 0 1 2 after upgrading pam_mount

bruceg · 2025-10-13 05:05:25

After upgrading pam_mount last night to 2.21-1, I am seeing a number printed out at the start and end of when I run sudo and a few other commands. For example:

~> sudo id
2
uid=0(root) gid=0(root) groups=0(root)
1

Downgrading to 2.20-3 makes the problem go away.

From what I can tell, the output is coming from pmvarrun, which prints out the mount count for the user logging in/out, but that is supposed to be captured by the pam_mount module so I'm confused.

I checked the history for both the Arch package and the upstream sources but I don't see anything relevant. I thought I'd ask around here in case somebody else had seen this before I bug the author.

Thanks.

seth · 2025-10-13 09:34:11

https://codeberg.org/jengelh/pam_mount/ … 5328fb477a seems to do the straight opposite…?
Did you change the debug option? What if you explicitly set it to 0?
https://man.archlinux.org/man/pam_mount … l_tunables

bruceg · 2025-10-14 02:35:13

Thanks for the suggestion.

The config already has the debug option set to 0:

<debug enable="0" />

Paradoxically, removing that option makes the output more verbose, despite the man page saying that it defaults to 0. However, the numbers don't show up, at least not as-is.

~> sudo id
(pam_mount.c:562): pam_mount 2.21: entering session stage
(pam_mount.c:623): no volumes to mount
command: 'pmvarrun' '-u' 'root' '-o' '1' 
(pmvarrun.c:254): parsed count value 1
(pam_mount.c:435): pmvarrun says login count is 2
(pam_mount.c:654): done opening session (ret=0)
uid=0(root) gid=0(root) groups=0(root)
(pam_mount.c:700): received order to close things
(pam_mount.c:703): No volumes to umount
command: 'pmvarrun' '-u' 'root' '-o' '-1' 
(pmvarrun.c:254): parsed count value 2
(pam_mount.c:435): pmvarrun says login count is 1
(pam_mount.c:728): root seems to have other remaining open sessions
(pam_mount.c:737): pam_mount execution complete
(pam_mount.c:109): Clean global config (1073741824)

Also, I discovered after I posted the above that I am unable to login with pam_mount 2.21. GDM just spins after I enter the password, so it must be breaking with the extra output to stderr.

seth · 2025-10-14 08:06:59

The original output seems to come from https://codeberg.org/jengelh/pam_mount/ … run.c#L286 which however has been there forever and the intention seems for it to be redirected into pam_mount

GDM just spins after I enter the password

Downgrading to 2.20-3 makes the problem go away.

Did you only downgrade pam_mount (or everything, maybe incl. GDM)?

bruceg · 2025-10-14 13:21:43

seth wrote:

Did you only downgrade pam_mount (or everything, maybe incl. GDM)?

Nope, just pam_mount, using the "downgrade" tool.

I see that setting _PMT_DEBUG_LEVEL could turn on debugging, but there are no references to that in /etc nor is it set in sudo login sessions. I know that's a secondary issue, but it might point to a solution for the primary.

seth · 2025-10-14 13:28:30

The output is actually unconditional, but seems to be intended as stdin for pam_mount (from https://man.archlinux.org/man/pmvarrun.8 stdout)

marmis · 2025-10-14 22:18:32

I'm having the same issue. Is there an upstream issue for this? I didn't find any.

seth · 2025-10-15 06:06:43

Me neither - https://codeberg.org/jengelh/pam_mount/issues
Though it would be nice to know why this isn't going into pam_mount's stdin, it's also sth. for the author to figure.

Arch Linux

#1 2025-10-13 05:05:25

Extraneous 0 1 2 after upgrading pam_mount

#2 2025-10-13 09:34:11

Re: Extraneous 0 1 2 after upgrading pam_mount

#3 2025-10-14 02:35:13

Re: Extraneous 0 1 2 after upgrading pam_mount

#4 2025-10-14 08:06:59

Re: Extraneous 0 1 2 after upgrading pam_mount

#5 2025-10-14 13:21:43

Re: Extraneous 0 1 2 after upgrading pam_mount

#6 2025-10-14 13:28:30

Re: Extraneous 0 1 2 after upgrading pam_mount

#7 2025-10-14 22:18:32

Re: Extraneous 0 1 2 after upgrading pam_mount

#8 2025-10-15 06:06:43

Re: Extraneous 0 1 2 after upgrading pam_mount

Board footer