15 month old bug

[cackles]

Hi, so instead of upgrading I decided to do a fresh install -this has lead to great regret. You can see all the upgrades I have done over the last seven years and in my divine wisdom I had a thought (dangerous) and it was just to start afresh, new hardware and went from 32 to 64 bit.

Anyways, the jist of it is I am getting an error;

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

This bug has been around since the backend of 2013. I've worked around it by removing the offending package. But between this and another few long term bugs it is making simple setup and deployment problematic.

Is there anyone that can get things like this kicked up the chain?

[kerry_s]

Is there anyone that can get things like this kicked up the chain?

i'll see what i can do.

[tgalati4]

Perhaps tell us the package and the hardware that you are having problems with. Have you updated the bug report?

[Doug S]

Anyways, the jist of it is I am getting an error;

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

This bug has been around since the backend of 2013.

I entered the bug report on 2013.12.02, during trusty daily testing. It does seem to be taking an excessive amount of time to fix. That being said, I still have never noticed any issue other than the message itself.

[kerry_s]

so the answers on #14
Fix:
run "pam-auth-update" and remove "SMB password synchronization".

apparently not a bug but a feature. lol

[cackles]

so the answers on #14
Fix:
run "pam-auth-update" and remove "SMB password synchronization".

apparently not a bug but a feature. lol

lol, yup

It is better if you don't install Samba from options during the initial setup, well, means less work. Seems they have it disabled when you apt-get samba. So someone-somewhere is aware of it.