Escolar Documentos
Profissional Documentos
Cultura Documentos
1 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
[Impact]
* Warning messages related to memory leaks "no talloc stackframe
at"
are present at login and other PAM services when libpam-smbpass
is
installed.
* Backporting the fix resolves the warning messages and memory
leak.
* The upload incorporates the upstream fix from Samba.
[Test Case]
* On a Trusty 14.04 system:
1. sudo apt-get install libpam-smbpass
2. sudo passwd <user on the system>
3. if bug is present in samba, then the output looks like:
% sudo passwd <user>
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
10/2/2015 7:10 PM
2 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
memory
Enter new UNIX password:
4. After applying the updated packages the 'no talloc
stackframe at'
message is no longer present during step 2.
[Regression Potential]
* The changes are in the area of samba password authentication so
it would be worth exercising Samba client password manipulation.
[Original Description]
This message appears a lot as of a recent update to samba (Trusty
development branch):
no talloc stackframe at ../source3/param/loadparm.c:4831, leaking
memory
From this upstream bug report, I am lead to believe the issue is
in libpam-smbpass, but I don't really know for sure.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728666
I am filing this bug report mainly so that I can refer to it on
the testing tracker as an issue, while still setting the test case
to pass. Note that other than the error message itself, I am not
aware of any bad side effect.
doug@v32-serv04:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
Codename: trusty
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1257186
tags:added: iso-testing
10/2/2015 7:10 PM
3 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
Changed in samba:
importance:Unknown Medium
status:Unknown Confirmed
I also have this issue. It appears to have also been raised at the
samba bugzilla page:
https://bugzilla.samba.org/show_bug.cgi?id=10420
I can confirm James Dupin's post: gone after "sudo apt-get remove
libpam-smbpass".
See http://ubuntuforums.org/showthread.php?t=2214042 with my
experience before I saw this post.
PS:
10/2/2015 7:10 PM
4 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
So that Google will find it, I'll post my exact message with a
different (line?) number:
"no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory"
HTH
Changed in samba:
status:Confirmed In Progress
Confirmed I have same issue with 14.04 x64 beta updated as well.
10/2/2015 7:10 PM
5 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
Confirmed I also have same issue with 14.04 x64 beta updated as
well.
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory
Confirmed with 14.04 x64, every time i run the sudo command :
quentin@asus-N56VZ:~$ sudo su
[sudo] password for quentin:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory
root@asus-N56VZ:/home/quentin#
I have had the same issue since upgrading 13.10 to 14.04. Thomas
solution did not work for me.
10/2/2015 7:10 PM
6 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
10/2/2015 7:10 PM
7 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
@wilpgam
Do you intend to work on this yourself, or did you assign the bug
to yourself by accident? I'll assume the latter?
Changed in samba (Ubuntu):
assignee:wilpgam (wilpgam) nobody
I tried the patch in the upstream bug, but this did not fix my test
case. For the record, I'll attach the debdiff I attempted (that
doesn't work).
10/2/2015 7:10 PM
8 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
I accidentally hit the status of this bug and changed it, now I
can't change it back. Sorry for the trouble!
10/2/2015 7:10 PM
9 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
netatalk/+bug/810732
Disabling SMB password synchronization (for example with pam-authupdate) not onyl remove the error message of this bug but also
restore Netatalk behavior.
and after two error free days, the error returned after a
successful install and configuration of Minidlna...err...
ReadyMedia if the copyright police are lurking.
10/2/2015 7:10 PM
10 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
Hi,
I have a HP Microserver N40L and on a fresh installation of Ubuntu
Server 14.04 LTS i get the same Leaking Memory Problem.
Because im new using Ubuntu Server, can please someone please help
me on this and respond to 3 simple questions i have:
1- Besides removing "libpam-smbpass" is there any other solution
for this problem?
2- Until Ubuntu team releases a fix / update for this, can i still
use Ubuntu Server 14.04 LTS, without problems? How does this memory
leaking problem affects my system?
3- On the installation process i choose to install Samba. If i
don't install Samba will the Leaking Memory problem still happen?
Thanks
Changed in samba:
status:In Progress Fix Released
10/2/2015 7:10 PM
11 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
tags:added: patch
I installed the 14.04.1 LTS for my server. Samba was not selected
during the installation. I Installed it manually without a problem.
The problem occured immediately after installing the libpamsmbpass. My Samba version is 4.1.6-Ubuntu
This issue seems to be resolved by the samba team already in July
(https://bugzilla.samba.org/show_bug.cgi?id=8449). It says it has
been fixed in 4.1 but the fix is not in 4.1 for Ubuntu ?
Having a fix in 14.10 is not a resolution. 14.04 is a LTS for
(production) servers and must receive the fix through normal
package upgrades. Is this bug really "not assigned" in the Ubuntu
team ?
10/2/2015 7:10 PM
12 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
i really cant think how this could be waited so long to ship a fix.
this is really not acceptable.
10/2/2015 7:10 PM
13 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
This error makes my dovecot's auth-worker get down since I use both
system accounts and virtual mail boxes... So it's serious to me...
Probably, there occur such problems...
10/2/2015 7:10 PM
14 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
10/2/2015 7:10 PM
15 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
I'm not sure why unresolved bugs for missed milestones can't be
moved to the next milestone automatically. Less chance of them
being ignored that way!
Thank you #89. It's a PITA to do, but it does work as Ian described
and the error no longer appears when I use sudo.
Chad wrote:
10/2/2015 7:10 PM
16 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
> This bug also affects vsftpd functionality. When SMB password
synchronisation is selected in pam-auth-update, vsftpd can not
authenticate users and segfaults with OOPS message.
This sounds like bug 1348972 in vsftpd and I don't think a fix to
this samba bug will affect it.
10/2/2015 7:10 PM
17 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
description:updated
SRU from Ryan Harper sponsored and uploaded. Thanks! Now awaiting
review from the SRU team.
Changed in samba (Ubuntu Trusty):
status:Confirmed In Progress
Would someone explain the last several updates? What is the SRU
team and what kind of review are they performing? Finally (and
possibly most importantly), how can the status be "In Progress"
when the ticket is still "Unassigned"?
Thanks in advance!
On Thu, Jun 25, 2015 at 7:44 PM, Chad <email address hidden> wrote:
> Would someone explain the last several updates? What is the SRU
team
>
and what kind of review are they performing? Finally (and possibly
most
Hi, I think most of your questions will be answered by looking at
10/2/2015 7:10 PM
18 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
the
Stable Release Update wiki page:
https://wiki.ubuntu.com/StableReleaseUpdates
I've applied and tested the upstream fix for this issue to the
Samba
package in trusty.
I've confirmed that the fix that's upstream in Samba is not present
in the
current development release (Wily)
And I've packaged up the fix for trusty and submitted for the SRU
team to
review. If approved, there will be
a test package published to be verified and if all goes well it
will be
released into the
Trusty updates stream.
importantly), how can the status be "In Progress" when the ticket
is
> still "Unassigned"?
>
Work is under-way, specially the Trusty SRT task is in progress;
bug
assignment isn't required AFAIK.
Hope that helps,
Ryan
10/2/2015 7:10 PM
19 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
tags:added: verification-done
removed: verification-needed
10/2/2015 7:10 PM
20 of 20
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1257186
10/2/2015 7:10 PM