Your message dated Sat, 21 Mar 2026 20:36:52 +0000
with message-id <[email protected]>
and subject line Bug#1034339: fixed in libpam-mount 2.22-3
has caused the Debian Bug report #1034339,
regarding libpam-mount: 'sudo -i' gives 'HXproc_run_async: pmvarrun: No such
file or directory'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1034339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034339
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libpam-mount
Version: 2.19-1
Severity: minor
Tags: patch
Dear Maintainer,
* What led up to the situation?
Running 'sudo -i' causes 'HXproc_run_async: pmvarrun: No such file or
directory' to be printed. The sudo call works without problem.
* What exactly did you do (or not do) that was effective (or
ineffective)?
sudo -i
* What was the outcome of this action?
'HXproc_run_async: pmvarrun: No such file or directory' was printed
* What outcome did you expect instead?
Not to see that message
Fix (but I don't know whether this is the best or correct fix):
--- /tmp/pam_mount.conf.xml.original 2023-04-13 09:23:42.587754765 +0100
+++ /etc/security/pam_mount.conf.xml 2023-04-13 09:16:31.053801290 +0100
@@ -38,4 +38,7 @@
<mkmountpoint enable="1" remove="true" />
+<!-- https://bugs.gentoo.org/330995 -->
+<pmvarrun>/usr/sbin/pmvarrun -u %(USER)</pmvarrun>
+
</pam_mount>
-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-security')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libpam-mount depends on:
ii libc6 2.36-8
ii libcryptsetup12 2:2.6.1-3~deb12u1
ii libhx32 4.10-1
ii libmount1 2.38.1-5+b1
ii libpam-runtime 1.5.2-6
ii libpam0g 1.5.2-6
ii libpcre2-8-0 10.42-1
ii libssl3 3.0.8-1
ii libxml2 2.9.14+dfsg-1.1+b3
Versions of packages libpam-mount recommends:
ii libpam-mount-bin 2.19-1
Versions of packages libpam-mount suggests:
ii cifs-utils 2:7.0-2
pn davfs2 <none>
ii fuse3 [fuse] 3.14.0-3
pn hxtools <none>
ii lsof 4.95.0-1
ii openssl 3.0.8-1
ii psmisc 23.6-1
ii sshfs 3.7.3-1.1
ii xfsprogs 6.1.0-1
-- Configuration Files:
/etc/security/pam_mount.conf.xml changed:
<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE pam_mount SYSTEM "pam_mount.conf.xml.dtd">
<!--
See pam_mount.conf(5) for a description.
-->
<pam_mount>
<!-- debug should come before everything else,
since this file is still processed in a single pass
from top-to-bottom -->
<debug enable="0" />
<!-- Volume definitions -->
<!-- pam_mount parameters: General tunables -->
<luserconf name=".pam_mount.conf.xml" />
<!-- Note that commenting out mntoptions will give you the defaults.
You will need to explicitly initialize it with the empty string
to reset the defaults to nothing. -->
<mntoptions
allow="nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other,credentials,uid,gid"
/>
<!--
<mntoptions deny="suid,dev" />
<mntoptions allow="*" />
<mntoptions deny="*" />
-->
<mntoptions require="nosuid,nodev" />
<!-- requires ofl from hxtools to be present -->
<logout wait="0" hup="no" term="no" kill="no" />
<!-- pam_mount parameters: Volume-related -->
<mkmountpoint enable="1" remove="true" />
<!-- https://bugs.gentoo.org/330995 -->
<pmvarrun>/usr/sbin/pmvarrun -u %(USER)</pmvarrun>
</pam_mount>
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libpam-mount
Source-Version: 2.22-3
Done: Jochen Sprickerhof <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libpam-mount, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jochen Sprickerhof <[email protected]> (supplier of updated libpam-mount
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 21 Mar 2026 21:22:40 +0100
Source: libpam-mount
Architecture: source
Version: 2.22-3
Distribution: unstable
Urgency: medium
Maintainer: Jochen Sprickerhof <[email protected]>
Changed-By: Jochen Sprickerhof <[email protected]>
Closes: 1034339
Changes:
libpam-mount (2.22-3) unstable; urgency=medium
.
* Move pmt-ehd and pmvarrun to bin/ (Closes: #1034339)
* Drop optional priority
* Bump policy version (no changes)
Checksums-Sha1:
4f1c00c5af9e190e3959567f69dc6ae3b92d907b 2323 libpam-mount_2.22-3.dsc
0d7f8926955677885cb81f38fff1aad4e8b04ee4 27832
libpam-mount_2.22-3.debian.tar.xz
Checksums-Sha256:
61c3f55fa363fde5c402b83d8b5131d515b0a1c8846d45d60ae362b80983b979 2323
libpam-mount_2.22-3.dsc
1a1458addd57b6a5f05bfba8ef29134dee364493e6586c399c70402e4cdc0a32 27832
libpam-mount_2.22-3.debian.tar.xz
Files:
e7a2420a6fec48bf9630d127b39e126a 2323 admin optional libpam-mount_2.22-3.dsc
d6e138f7c63afa82ddf7e0e8f915ba2c 27832 admin optional
libpam-mount_2.22-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmm+/mUACgkQW//cwljm
lDNrdA/+JlzlEUIChs7Ag/SVlTtJOJLfrFCowI2hlGss86KWluOg4FsRWWCsJRSo
0Ko88iENjCXPSczVx7Mfgui4uWLp5cEDyowzFZtnydQi+m5wmV3WUaNDKQtJN2O3
Y694MJqiC3ymAKKZ6f0l6Yc5kR9ZZf949bmCnpIlfYEBRF1qY0YHwzEbyWAVEKKJ
dqGq1LVAksuI/r+QL+2Ip7mTOxv6VytCrVXxLfaUnqnBKaN83odj15j9pqf97MvV
ZHTtXIu7RbzrPPVt9E/C3x4POKJHNJcVGWg81N6miD+ntuEfRjBBTxFdJBDATtko
341n+eRHAQn3ZX7Z8lFtmYwnEAJX5fBOnNfzdo8oOMd1ZwQUMSXr+fWzTfh4gl0j
oAa0NOe00LpIvSHq5Scyukey3cLbHwy1KGKbhRthtaQTl56qBeDZ96sq3fapmXeS
M3/RXIjHfVB563lA3VOu2E+pE3WNPLUvZvlDUVsnw6vNOfB6CQhDGu2P3qPgp7fW
OiQwxAmY6Jo0SxXfYqEH+2VBwc5zhnafYeLJ0c3nch/eeAJf+uMXw2LQkMqwcc3T
rufxRn5zcnBGcPMzqyZGA6LePGOI7JJie95OHzDnsgesut9BkkoOqkzIUb5bVL7R
lvPPJ0lAulRansZdX4+wcmFrI88NsLPJAW71GoC384zsG5O0/So=
=PlcI
-----END PGP SIGNATURE-----
pgpViIb1M07oh.pgp
Description: PGP signature
--- End Message ---
