Inicio » Trisquel » Incidencias
Enviado por Marcus o Dom, 08/10/2014 - 11:23

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

Proxecto:Trisquel
Versión:7.0
Componente:Programs
Categoría:informe de erro
Prioridade:normal
Asignado:upstream
Estado:closed
Descrición

When trying to gain sudo rights e.g. using sudo bash, I got an error:

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

This is caused by libpam-smbpass and can be solved by removing the package (I guess it's not necessary on trisquel.)

Legimet:
Dom, 08/10/2014 - 21:30

This is an upstream bug:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1274680

So I believe this should be closed.

akfoss:
Mar, 09/23/2014 - 13:13

This bug is solved in upstream.

As stated in the following comment,
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186/comments/54

"I checked Samba changelog, the patch was included in Samba 4.1.10. It's scheduled for release with Trusty 14.04.2"

leny2010:
Mar, 10/14/2014 - 16:47

The bug legimet mentions above is now marked duplicate of:

https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186

I'm arranging for this issue to be assigned to 'upstream'.

SirGrant:
Mér, 10/15/2014 - 20:20
Asignado a:anonymous» upstream
leny2010:
Xov, 11/13/2014 - 19:38

To save users from looking it up on launchpad the upstream bug is scheduled to be fixed in 14.02.2 which is due February 2015.

Sasaki:
Dom, 11/16/2014 - 00:23

Looks like it's possible to fix it without removing libpam-smbpass. Just by running "sudo pam-auth-update" and remove "SMB password synchronization".
Source : http://ubuntuforums.org/showthread.php?t=2214042

jesse:
Dom, 02/15/2015 - 23:18

Sasaki's suggestion solved the issue for me, thank you.

leny2010:
Ven, 07/10/2015 - 16:50
Estado:active» fixed

The verified upstream fix is now in the repos. Please comment both on launchpad and here if this does not resolve the problem for you.

quidam:
Ven, 07/24/2015 - 16:55
Estado:fixed» closed

Automatically closed -- issue fixed for 2 weeks with no activity.