Você está na página 1de 20

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

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

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

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

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

3 of 20

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

Changed in samba (Ubuntu):


importance:Undecided Medium

Changed in samba (Debian):


status:Unknown New

Status changed to 'Confirmed' because the bug affects multiple


users.
Changed in samba (Ubuntu):
status:New Confirmed

Changed in samba:
importance:Unknown Medium
status:Unknown Confirmed

this "problem" appears after installation of libpam-smbpass and


disappears when this program is removed

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

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

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

This bug exists 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
Nominated for Trusty series.

Confirmed to jonkers post #5 removing libpam-smbpass removes the


error.

Confirmed I have same issue with 14.04 x64 beta updated as well.

Issue exists in Trusty server ISO 2014-APR-09.


Workaround confirmed, but I've not explored other potential effects
of removing this package:
sudo apt-get remove libpam-smbpass
tags:added: trusty

Confirming this issue on 14.04 release (x64, if it's important).

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

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

when restart apache


no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory
* Restarting web server apache2 [ OK ]

Confirmed with 14.04 (x86) and latest updates.


Fresh install with minimal iso; afterwards in tasksel selected
"Basic Ubuntu Server", "OpenSSH server", "Mail-Server" and "Samba
file server".
When sudo-ing the first time after running tasksel, the error
occured.
Fix:
run "pam-auth-update" and remove "SMB password synchronization".

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#

Confirmed, solution of Thomas works for me, thanks.

I have had the same issue since upgrading 13.10 to 14.04. Thomas
solution did not work for me.

Upgraded 13.10 x64 server to 14.04. Consistently seeing this


message whenever running sudo. For example,
xxx@xxx:/$ sudo -e testfile

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

6 of 20

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

[sudo] password for xxx:


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

Confirming this issue on 14.04 LTS release (x64).

Im upgrade of Ubuntu 13.10 2 ubuntu 14.04 yesterday and,


im ever at use a sudo comand . receive its message:
wylnux@expariom:/$ sudo su
[sudo] password for wylnux:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory
and im proced to uninstall "libpam-smbpass" with:
wylnux@expariom:/$ sudo apt-get remove libpam-smbpass
and work perfectly... thanks so much
Comfirm this solution work...
Changed in samba (Ubuntu):
status:Confirmed Fix Committed
status:Fix Committed Confirmed
assignee:nobody wilpgam (wilpgam)

Although removing the package may fix the message, libpam-smbpass


is required to sync user accounts with samba passwords. Removing
that packaging removes that functionality.

Reproduced on a fresh Trusty cloud image. Steps to reproduce:


1. apt-get install libpam-smbpass
2. sudo passwd ubuntu
Expected result:
Enter new UNIX password:
Actual result:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

7 of 20

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

Enter new UNIX password:


This should help with verifying a fix.

@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

@pieterjanvu @Robie Basak... thanks 4 ur reply


obviously if I uninstall this functionality, entered into security
risk when working in large companies and ports are shared. but this
solution is only in my case because I work on a single network,
mine ....
and do not recommend it, but in my case to do this I lose the
functionality that provides security ... (sorry 4my Ingls)
My question: How fix
how to fix that this message appearing not more without disabling
lib?....
....

As Thomas (reusch) suggest in #14 :


____
Fix:
run "pam-auth-update" and remove "SMB password synchronization".
____
This isn't a security issue, simply you must remember that your
samba password may not match your system password.
In an enterprise enviroment, if ubuntu is used as samba server, i
bet it use kerberos tickets to verify the users identity throught
domain controller or alternative ldap infrastructure.

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

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

8 of 20

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

Changed in samba (Ubuntu Trusty):


milestone:none ubuntu-14.04.1
status:New Triaged
importance:Undecided Medium

Changed in samba (Ubuntu Trusty):


status:Triaged In Progress

I accidentally hit the status of this bug and changed it, now I
can't change it back. Sorry for the trouble!

Thomas: I've flipped it back.


Changed in samba (Ubuntu Trusty):
status:In Progress Triaged

This importance of this bug should probably be reexamined, because


it has impact on other softwares, like Netatalk. It prevents AFP
shares from being accessible and make Netatalk totally useless.
Here is a syslog trace where Netatalk crash because of this bug :
May 17 10:48:29 ace-of-spades afpd[3498]: =====================
==========================================
May 17 10:48:29 ace-of-spades afpd[3498]: INTERNAL ERROR: Signal 11
in pid 3498 (2.2.2)
May 17 10:48:29 ace-of-spades afpd[3498]: =====================
==========================================
May 17 10:48:29 ace-of-spades afpd[3498]: BACKTRACE: 3 stack
frames:
May 17 10:48:29 ace-of-spades afpd[3498]: #0 /usr/sbin/
afpd(netatalk_panic+0x1f) [0x7f4acaaf08bf]
May 17 10:48:29 ace-of-spades afpd[3498]: #1 /usr/sbin/
afpd(+0x549bc) [0x7f4acaaf09bc]
May 17 10:48:29 ace-of-spades afpd[3498]: #2 /lib/x86_64-linuxgnu/libc.so.6(+0x36ff0) [0x7f4ac9440ff0]
See this bug report : https://bugs.launchpad.net/ubuntu/+source/

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

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.

Changed in samba (Ubuntu):


status:Confirmed Triaged

I had been experiencing this bug until I set up RSA authentication


for all my console sessions, and disabled password notifications.
Once I did that, I have not seen any recurrences.

I should have said password authentications there- not password


notifications.

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.

I am affected with the same bug on my Trusty Thar but unfortunately


solution on post number 14 leads to unable to retrieve shares list
so have to turn the smb pass synchronization on to gain access to
samba shared folders.

after i run this command "sudo apt-get remove libpam-smbpass"


ubuntu doesnt start.
i see the Ubuntu logo with dots below and then a blank screen after
that.
if i close lid and open again i see button labeled with [OK] and
nothing happens.
please help.

"sudo pam-auth-update " did the trick for me.

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

10 of 20

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

confirming affects server 14.04 installed by netboot, with smb file


and print server, ssh server, selected.

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

On fresh 14.04 install with "Samba File Server" selected during


install...I hit the same "leaking memory" message when i 'sudo su'.
Confirmed was able to run 'pam-auth-update' and deselected "SMB
password synchronization" option in the pam-auth-update UI and the
"leaking memory" no longer appears. However, i don't know if this
actually prevents the memory leak or if there are any other
side-effects.

Changed in samba (Ubuntu):


importance:Medium High
Changed in samba (Ubuntu Trusty):
importance:Medium High

Changed in samba:
status:In Progress Fix Released

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

11 of 20

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

Changed in samba (Ubuntu Trusty):


milestone:ubuntu-14.04.1 ubuntu-14.04.2

tags:added: patch

summary:- memory leakage messages


+ memory leakage messages (no talloc stackframe)

Disabling the module with pam-auth-update makes the problem go away


for me. If I re-enable the problem comes back.
This should be a HIGH priority bug.
The problem will occur after a successful su command.
Running with all the available patches available today.

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 ?

It would be interesting to hear about timelines from upstream


Canonical support when the fix is finally integrated in the 14.04
LTS codebase.
Any updates on this?

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

12 of 20

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

No one can make a patch for this release?


We have to wait for ubuntu-14.04.2 ? really?
This MUST be a HIGH priority bug!

I also can't understand why it is not fixed already. Because on


14.10 the fix is already released ...so it exists one! :-(

Another Ubuntu user with the same memory leak issue.


Just like others said, how can it be that the LTS version hasn't
got the fix that was already released in July?
This is another one of these "Linux quirks" that makes you wonder
if using LTS was worth it?
Should be top priority but seemingly the devs do not care. I'm
puzzled.

On my machine message looks like this (i.e. when i sudo winecfg):


xxx@xxx-pc:~$ sudo winecfg
[sudo] password for xxx:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory
Ignoring unknown parameter "password level"
Ignoring unknown parameter "update encrypted"
wine: /home/xxx/.wine is not owned by you
I have all kind of samba packages installed, also the libpam stuff
and pam auth, took me 2 hours to get samba to browser my network,
then my user password was changed, when samba and ubuntu passwords
where synced, the i had to re-passwd my user, now samba works,
ubuntu works, but i get this message. i must say that samba has to
be considered completely broken on ubuntu 14.04 LTS as the "Local
network share"-feature in the File manager does nothing useful at
all, it just doenst bring samba to life, one has to install samba
by hand and go through the hole pain in the ass smb.conf procedure,
as sambe is a pure pain in the ass to configure.
gtz

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

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

13 of 20

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

Still broken in 14.04.2.


Changed in samba (Ubuntu Trusty):
status:Triaged Incomplete
status:Incomplete New

Changed in samba (Ubuntu Trusty):


status:New Confirmed

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...

Confirmed in Ubuntu 14.04.02 LTS after recent upgrade from Ubuntu


12.04 LTS.

Confirmed in Ubuntu 14.04.02 LST after fresh install.

Correction: make that 14.04.02 LTS Server.

I also get it when starting python:


Ignoring unknown parameter "password level"
Ignoring unknown parameter "update encrypted

Confirmed in Ubuntu 14.04.02 LST x64 after fresh install.

Confirmed in Ubuntu 14.04.02 LST x64.


I did not notice it until after I updated, but maybe it was there.

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

14 of 20

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

Confirmed in Ubuntu 14.04.02 LST x64.


Fresh install.

Still and issue. Ubuntu 14.04.2 LTS (GNU/Linux 3.16.0-37-generic


x86_64)
chad@server:~$ sudo su
[sudo] password for chad:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory
root@server:/home/chad#

Wow, this bug has a long history.


I can confirm the issue as well with 4.1.6 and 4.2.1 I've isolated
to the line:
auth optional pam_smbpass.so migrate
Configured in /etc/pam.d/common-auth
That line is added by libpam package installation and also by using
pam-auth-update to enable SMB Password Synchronization
For 4.2.1 the error however occurs in su:
*** Error in `su': double free or corruption (fasttop):
0x000000000110d800 ***
Aborted
Which happens after the password is entered.

This is happening still in 14.04.2.


I installed libpam-smbpass:amd64 2:4.1.6+dfsg-1ubuntu2.14.04.7
Whenever I do sudo commands and login in the issue shows up with
talloc.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

15 of 20

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

I think this should be easy to fix if Canonical can find anyone to


assign the bug to. I managed to fix it locally by following the
guide at https://help.ubuntu.com/community/UpdatingADeb to rebuild
the samba packages from source with the upstream patch applied. For
the final step, I used "sudo debi -u" instead of "sudo debi" to
only upgrade the existing packages instead of installing all of
them.

I can also confirm this is still an issue:


no talloc stackframe at ../source3/param/loadparm.c:4864, leaking
memory
SYSTEM SETTINGS:
Operating system : Linux Mint 17.1 Cinnamon 64bit
Cinnamon Version : 2.4.5
Linux Kernel : 3.13.0-37 generic
Confirmed no longer an issue once "libpam-smbpass" removed.

This should me moved to the https://launchpad.net/ubuntu/


+milestone/ubuntu-14.04.3 or https://launchpad.net/ubuntu/
+milestone/ubuntu-14.04.4 milestone.

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.

Xavier wrote that this needs to be moved somewhere else. Does


anyone know how to do that? If someone can explain to me what needs
to happen, I'll be happy to do it myself. Removing libpam-smbpass
is not an option for me, nor is it, in my opinion, an appropriate
"fix". I can't believe no one is looking at this.

Chad wrote:

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

16 of 20

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

>Xavier wrote that this needs to be moved somewhere else.


> Does anyone know how to do that?
> If someone can explain to me what needs to happen,
I changed the trusty target from 14.04.2 (which is in the past) to
14.04.3 (which is in the future, albeit, not far off)
Changed in samba (Ubuntu Trusty):
milestone:ubuntu-14.04.2 ubuntu-14.04.3

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 seems like
a critical bug to me and should be corrected as soon as possible in
a LTS server release...

> 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.

gollum53 wrote in comment #96:


> 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.
I had a quick go at trying to reproduce that to see if I could
install a modified libpam-smbpass to make the problem go away, but
I was unable to reproduce it. That was probably related to these
messages in my /var/log/auth.log:
Jun 23 11:33:20 ubuntu vsftpd: PAM unable to dlopen(pam_smbpass.
so): /lib/security/pam_smbpass.so: cannot open shared object file:
No such file or directory
Jun 23 11:33:20 ubuntu vsftpd: PAM adding faulty module:
pam_smbpass.so
as the PAM modules such as pam_smbpass.so are actually installed in
/lib/x86_64-linux-gnu/security/ on my 64-bit system, not
/lib/security/. This is a separate issue with vsftpd not worth
dwelling on in this bug, though I did try symlinking /lib/x86_
64-linux-gnu/security to /lib/security and got these errors
instead:
Jun 23 11:51:40 ubuntu vsftpd: PAM unable to dlopen(pam_smbpass.

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

17 of 20

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

so): libsamba-hostconfig.so.0: failed to map segment from shared


object: Cannot allocate memory
Jun 23 11:51:40 ubuntu vsftpd: PAM adding faulty module:
pam_smbpass.so
At that point I gave up trying to reproduce the problem with
vsftpd!

description:updated

I've confirmed that this is already fixed in Wily.

Changed in samba (Ubuntu):


status:Triaged Fix Released

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

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

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

Hello Doug, or anyone else affected,


Accepted samba into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/samba/2:
4.1.6+dfsg-1ubuntu2.14.04.8 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See https:/
/wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this
bug, mentioning the version of the package you tested, and change
the tag from verification-needed to verification-done. If it does
not fix the bug for you, please add a comment stating that, and
change the tag to verification-failed. In either case, details of
your testing will help us make a better decision.
Further information regarding the verification process can be found
at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank
you in advance!

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

19 of 20

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

Changed in samba (Ubuntu Trusty):


status:In Progress Fix Committed
tags:added: verification-needed

I did a dist-upgrade with trusty proposed and the leakage message


is gone for me...

libpam-smbpass 2:4.1.6+dfsg-1ubuntu2.14.04.8 fixes it for me.

tags:added: verification-done
removed: verification-needed

Unable to test at this time, too many umet dependencies

This bug was fixed in the package samba - 2:4.1.6+dfsg-1ubuntu2.


14.04.8
--------------samba (2:4.1.6+dfsg-1ubuntu2.14.04.8) trusty; urgency=medium
* Fix for "no talloc stackframe at" warning messages (LP:
#1257186)
-- Ryan Harper <email address hidden> Mon, 22 Jun 2015 08:48:37
-0500
Changed in samba (Ubuntu Trusty):
status:Fix Committed Fix Released

10/2/2015 7:10 PM

Bug #1257186 memory leakage messages (no talloc stackframe) : Bugs...

20 of 20

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

The verification of the Stable Release Update for samba has


completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug
report. In the event that you encounter a regression using the
package from -updates please report a new bug using ubuntu-bug and
tag the bug report regression-update so we can easily find any
regressions.

10/2/2015 7:10 PM

Você também pode gostar