sudo no talloc stackframe at ../source3/param/loadparam.c:4831, leaking memory

Bug #1274680 reported by Bruce Pieterse
320
This bug affects 73 people
Affects Status Importance Assigned to Milestone
sudo (Ubuntu)
Confirmed
Critical
Unassigned

Bug Description

I receive this message "no talloc stackframe at ../source3/param/loadparam.c:4831, leaking memory" if I run sudo for the first time in a new terminal.

Steps
1. Open Terminal
2. Type sudo <command>
3. Enter password
4. Command runs and outputs above message after successful verification
5. Close terminal. Repeat if necessary.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: sudo 1.8.9p4-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 30 21:56:21 2014
InstallationDate: Installed on 2013-08-30 (153 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: sudo
UpgradeStatus: Upgraded to trusty on 2014-01-30 (0 days ago)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/README: parsed OK
modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers']
modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README']

Revision history for this message
Bruce Pieterse (octoquad) wrote :
Revision history for this message
Bruce Pieterse (octoquad) wrote :

Still present with the latest sudo package update today (1.8.9p4-1ubuntu2)

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in sudo (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

Are you using smb for authentication?

It looks like this is a dupe of 157186

Revision history for this message
Javier López (javier-lopez) wrote :

This bug may only affect a Desktop installation, I was unable to reproduce the problem with sudo (1.8.9p4-1ubuntu2) on a minimalist setup (without X)

---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in sudo (Ubuntu):
importance: Undecided → Critical
Revision history for this message
G. Del Duca (djbeppe) wrote :

Still present even in ubuntu server 14.04 night build on 2014-03-06

Revision history for this message
Viktor Suprun (popsul1993) wrote :

I've the same bug on 14.04 with latest updates.

Revision history for this message
23W (pcnr) wrote :

I have same error on server version of 14.04

Revision history for this message
zob (zob) wrote :

I get this error on ubuntu server 14.04 when I log in (without doing anything else). It's written just above the "Last Login.... Welcome to Ubuntu Trusty" - message.
Below the "Welcome message" there is another error written.
error: config file /etc/landscape/client.conf can't be read
run-parts: /etc/update-motd.d/50-landscape-sysinfo exited with return code 1.

(I didn't choose landscape to handle updates during the install).

Happens on two different machines. One is virtual, the other is not.

Revision history for this message
Ryan Beisner (1chb1n) wrote :

This duplicate bug (and its original) exist in Trusty Server ISO 2014-APR-02.

I'm getting this error upon each login, and periodically during my console sessions:

     no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory

Reference:
Duplicate (this bug): https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1274680
Original bug: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186

Nominated the original bug for Trusty series.

Revision history for this message
PrivateUser132781 (privateuser132781-deactivatedaccount) wrote :

I get this on a brand new Ubuntu 12.04 server install, so def. not only affecting installs with X

Revision history for this message
Will Rouesnel (w-rouesnel) wrote :

This is happening to me too. This really needs to be fixed as I had a server move into reporting very strange out of memory conditions for the kernel after a couple of weeks of uptime, and this is the only real outstanding issue.

Revision history for this message
Gerald Drouillard (gerald-drouillard) wrote :

Looks like the folks at Samba have address the bug and have it staged for the next release:
https://bugzilla.samba.org/show_bug.cgi?id=8449

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.