** Changed in: sudo (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)'
Well, excuse me for the last post that I wrote, but for me the problem
was solved... Another time I'll don't do that. But now I have another
problem, with uswsusp and the log says that: Sessions still open, not
unmounting pam_mount(spawn.c:128): error setting uid to 0 Sessions still
open, not
And sorry, but I have to chage the state of the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)' failed.
** Changed in: libpam-mount (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
I've just reported the bug in uswsusp package:
https://bugs.launchpad.net/ubuntu/+source/uswsusp/+bug/35
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417:
This bug was fixed in the package sudo - 1.8.3p1-1ubuntu3.1
---
sudo (1.8.3p1-1ubuntu3.1) precise-proposed; urgency=low
* Fix Abort in some PAM modules when timestamp is valid. (LP: #927828)
-- TJ (Ubuntu Contributions) ubu...@tjworld.net Mon, 30 Apr 2012 18:05:21
+0100
**
That seems like a bug in pam_mount for not having sensible reference
counting behavior for mounts used by multiple sessions, and not a bug in
the sudo patch. How does this work if you try to log in twice over ssh
to the same account?
--
You received this bug notification because you are a
Ah, but if this is only with sudoedit and not with sudo, something else
may be wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion
I donwgraded to version sudo=1.8.3p1-1ubuntu3:
shell:~$ sudoedit test
reenter password for pam_mount:
pam_mount(mount.c:69): Messages from underlying mount program:
pam_mount(mount.c:73): crypt_activate_by_passphrase: File exists
pam_mount(pam_mount.c:521): mount of
Steve,
two simultaneous ssh's to a server with already mounted encrypted partitions do
not print errors for the user.
However, auth.log records the following lines:
May 8 23:11:17 myserver sshd[8]: Accepted password for myuser from
xxx.xxx.xxx.xxx port 36342 ssh2
May 8 23:11:17 myserver
I filed a bug #996806 against sudo in ubuntu for the sudoedit and
pam_mount bug. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count:
I have sudo 1.8.3p1-1ubuntu3.1 from precise-proposed and I use pam_mount
for mounting encrypted partitions at login.
While the original bug is fixed with the 1ubuntu3.1 version of sudo,
'sudoedit' command triggers pam_mount to enquire the password of the
encrypted partition, trying to mount it
Jari, thank-you.Did sudoedit behave like this before the upgrade in
-proposed? Please report this as a new bug against sudo and let me know
the bug #. I'll investigate and pass it upstream if necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If you don't want to enable the proposed repository, here's a quick
way to install the fixed sudo:
sudo -i # this helps work around the bug in the current version of sudo
wget -c -t 0
** Branch linked: lp:ubuntu/precise-proposed/sudo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)' failed.
To
Fantastic...
'sudo id' does not crash might desktop anymore...
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
Works :-).
Btw: the workaround in #4 kills samba user authentication too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user !=
I can confirm that minimally installing patched sudo in precise-
proposed, 1.8.3p1-1ubuntu3.1, onto an affected system otherwise cleanly
upgraded from beta2 makes the assertion go away immediately after
installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I installed the sudo from precise-proposed and the annoying pam_mount
umount messages are gone when using sudo.
** Tags added: verification-done
** Also affects: libpam-mount (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: sudo (Ubuntu Precise)
Importance:
Another workaround is to set the timestamp_timeout option in /etc/sudoers to
0.
This way, sudo always asks for the password which apparently avoids the error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sudo (Ubuntu)
Assignee: TJ (intuitivenipple) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user
This bug was fixed in the package sudo - 1.8.3p1-1ubuntu4
---
sudo (1.8.3p1-1ubuntu4) quantal; urgency=low
* Fix Abort in some PAM modules when timestamp is valid. (LP: #927828)
-- TJ (Ubuntu Contributions) ubu...@tjworld.net Mon, 30 Apr 2012 17:55:27
+0100
** Changed in: sudo
** Branch linked: lp:ubuntu/sudo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)' failed.
To manage
apt-cache policy sadms
sadms:
Installed: (none)
Candidate: 2.0.15.repack-0ubuntu2
Version table:
2.0.15.repack-0ubuntu2 0
500 http://ubuntu-archives.mirror.nexicom.net/ precise/universe amd64
Packages
Same results as others above.
--
You received this bug notification
Please fix this problem ASAP.
I am using encrypted home using tools from this package
/sbin/umount.crypt
/sbin/mount.crypto_LUKS
/sbin/umount.crypto_LUKS
/sbin/mount.crypt_LUKS
/sbin/umount.crypt_LUKS
But sometime I have more severe outcome.
My Unity crashes and goes to loging screen wnen I run
More.. It started to happen when I upgraded to 12.04...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)' failed.
sadms is not installed here; not an AD environment. Version table as for
the users above.
sadms:
Installed: (none)
Candidate: 2.0.15.repack-0ubuntu2
Version table:
2.0.15.repack-0ubuntu2 0
500 http://gb.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages
Presents here on
Brett, thanks. The reason for the request was I was discussing the issue
with Colin Watson on IRC and he pointed out the package isn't pulled in
by default. So aside from explicit manual installations as in your case
we wan't to figure out how it got installed - since it is the only PAM
module we
** Description changed:
- When running sudo it executes properly the first time during a session
- but, after credentials are cached, further attempts result in an error:
+ Stable Release Update request
+
+ [Impact]
+ Pluggable Authentication Module (PAM) pam_open_session() is not called by
apt-cache policy sadms
sadms:
Installed: (none)
Candidate: 2.0.15.repack-0ubuntu2
Version table:
2.0.15.repack-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apt-cache policy sadms
sadms:
Installed: (none)
Candidate: 2.0.15.repack-0ubuntu2
Version table:
2.0.15.repack-0ubuntu2 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages
according to my package history
libpam-mount was installed on my system
Commit Log
** Changed in: sudo (Ubuntu)
Status: Confirmed = In Progress
** Changed in: sudo (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Felix: that isn't a proposed fix - it is simply a work around that
Francesco discovered, but it caused pam_denied to run so all
authorisations fail.
I now have a patch that fixes the issue that works with the current
upstream tip (1.8.5 release candidate), thanks to a swift response by
its author
I've modified the upstream fix for 1.8.5-RC so it applies to 1.8.3p1.
I've linked my bazaar branch that contains the fix:
sudo (1.8.3p1-1ubuntu4) precise; urgency=low
* Fix Abort in some PAM modules when timestamp is valid. (LP: #927828)
-- TJ (Ubuntu Contributions) ubu...@tjworld.net Sat,
The package is now in my PPA and will be published for user testing
shortly.
https://launchpad.net/~intuitivenipple/+archive/ppa?field.series_filter=precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sudo (Ubuntu)
Status: In Progress = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)'
Since this bug only seems to affect systems with libpam-mount installed,
and that isn't installed by default, we're trying to determine which
package causes its installation.
Could those affected please report the result of:
apt-cache policy sadms
--
You received this bug notification because
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sudo (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo:
** Changed in: sudo (Ubuntu)
Status: Confirmed = Triaged
** Changed in: sudo (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo:
For me, I installed libpam-mount explicitly long ago in order to auto
mount encfs volumes on login. I don't have sadms installed, but here's
the policy run anyway as requested by TJ:
$ apt-cache policy sadms
sadms:
Installed: (none)
Candidate: 2.0.15.repack-0ubuntu2
Version table:
The crux of the problem is that sudo in Precise (v1.8.3p1) is a
massively re-factored code-base compared to v1.7.4p6 in Oneiric.
From what I've been able to deduce sudo has been massively re-written to
use a 'plugin' architecture to easily support many different
authorisation mechanisms. This
Updated bug-tracker to upstream project
** Bug watch added: Gratisoft Bugzilla #553
http://www.gratisoft.us/bugzilla/show_bug.cgi?id=553
** Changed in: sudo
Status: New = Unknown
** Changed in: sudo
Remote watch: Debian Bug tracker #648698 = Gratisoft Bugzilla #553
** Changed in:
The proposed fix of changing [default=1] to [default=0] in '/etc/pam.d
/common-session-noninteractive' causes problems with 'cron'.
Cron jobs are no longer executed. Syslog entry says 'CRON[process id]:
Permission denied'.
--
You received this bug notification because you are a member of Ubuntu
This appears to be caused by pam_mount.c::pam_sm_close_session().
When there are no volume list items the code that explicitly gets the
user name is skipped over:
if (Config.volume_list.items == 0) {
w4rn(No volumes to umount\n);
goto out;
}
which results
Upstream bug tracker:
https://sourceforge.net/tracker/?func=detailaid=3519691group_id=41452atid=430593
** Bug watch added: SourceForge.net Tracker #3519691
http://sourceforge.net/support/tracker.php?aid=3519691
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I also experience this running 12.04 beta2.
pam_mount tries to unmount all of my encrypted volumes listed in
pam_mount.conf.xml after I run sudo. After that, I get:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.
Aborted
--
You received this bug notification
Running sudo the first time, pam_mount tries to unmount my home dir ...
pam_mount(mount.c:69): umount messages:
pam_mount(mount.c:73): umount: ~: not found
pam_mount(mount.c:752): unmount of
/dev/disk/by-uuid/bb50645a-08c7-4c85-98b7-af0f8c9de98b failed
(my home dir is mounted via pam_mount on
Reset to confirmed. Please don't set to fix-released because of a
workaround/fix - it needs the package to be fixed to be set to fix-
released
** Changed in: libpam-mount (Ubuntu)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Not fixed in precise. I am getting this on a fresh upgrade to precise
from oneiric.
example
sudo cat /etc/issue
Ubuntu precise (development branch) \n \l
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.
Aborted
--
You received this bug notification because you
The first command that I run with sudo from a terminal when it asks for the
passord does not give me this error but if i run sudo after that when it does
not ask for a password it will give me
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.
Aborted
at the end.
I've just solved this bug. To solve it, someone has to login in with
root account with 'sudo bash' in a terminal emulator, and open
/etc/pam.d/common-session-noninteractive with 'gedit /etc/pam.d/common-
session-noninteractive', and he or she has to look for the line n°16 and
he or she has to
I've just changed the status from Comfirmed to Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)'
** Bug watch added: Debian Bug tracker #648698
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648698
** Also affects: sudo (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648698
Importance: Unknown
Status: Unknown
** Description changed:
When running sudo it
** Changed in: sudo
Status: Unknown = New
** Changed in: sudo (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417:
Hy!
Commenting out session optional pam_mount.so from
/etc/pam.d/common-session-noninteractive
I don't understand why it's included there in the first place? Can anyone
explain? I can't found a reason in the changelog :(
Also if that's the real reason, the bug should reassigned to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libpam-mount (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927828
Title:
sudo: pam_mount.c:417: modify_pm_count: Assertion `user != ((void
*)0)' failed.
To manage notifications about this bug go to:
57 matches
Mail list logo
