# Core Update 191 and Samba **URL:** \ **Category:** Add-Ons\ **Created:** [3 February 2025 23:30 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549 "2025-02-03T23:30:14Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![shazaam](https://community.ipfire.org/user_avatar/community.ipfire.org/shazaam/32/10034_2.png) [@shazaam](https://community.ipfire.org/u/shazaam)\ **Post date:** [3 February 2025 23:30 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/1 "2025-02-03T23:30:14Z")
At first I thought libtalloc had gone walkabout with core 191, Yet looking at the error, it seems to be a mere typo. nmbd smbd & winbind all fail to load the talloc library from: /usr/lib//samba/libtalloc.so.2 `TALLOC\_2.3.5’ Note the //samba Seems a path issue & a fix would be ever so nice. ---
**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\ **Post date:** [4 February 2025 07:02 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/2 "2025-02-04T07:02:57Z")
Which arch did you use and on which pakfire tree you are? At my systems samba is working. (there was a libtalloc problem in the testing phase but this should be fixed with samba pak 107) Also current version of samba should build against libtalloc 2.4.2 not 2.3.5 ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [4 February 2025 07:09 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/3 "2025-02-04T07:09:57Z")
> [@shazaam](#): > > Note the //samba A double slash in Linux is just ignored and not treated as an error. It is just treated as a single slash. ---
**Author:** ![shazaam](https://community.ipfire.org/user_avatar/community.ipfire.org/shazaam/32/10034_2.png) [@shazaam](https://community.ipfire.org/u/shazaam)\ **Post date:** [4 February 2025 13:34 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/4 "2025-02-04T13:34:07Z")
Just used Pakfire to install the updates. Nothing special going on. Old computer. The version error must be from the 191 update as 190 worked. ![Samba2](https://community.ipfire.org/uploads/default/original/2X/3/392b1dd331258fc36f7a67fa4510f57fdd869c45.png) ---
**Author:** ![shazaam](https://community.ipfire.org/user_avatar/community.ipfire.org/shazaam/32/10034_2.png) [@shazaam](https://community.ipfire.org/u/shazaam)\ **Post date:** [4 February 2025 13:34 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/5 "2025-02-04T13:34:47Z")
System ID: ![Samba1](https://community.ipfire.org/uploads/default/original/2X/e/ea506136dd22d78e79c911ee091db645f81be66c.png) ---
**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\ **Post date:** [4 February 2025 17:08 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/6 "2025-02-04T17:08:40Z")
I have again tried to reproduce this. Installed a fresh core190 and samba and then update to core191. Samba works without problems. ---
**Author:** ![digiz222](https://community.ipfire.org/user_avatar/community.ipfire.org/digiz222/32/15358_2.png) [@digiz222](https://community.ipfire.org/u/digiz222)\ **Post date:** [5 February 2025 00:06 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/7 "2025-02-05T00:06:02Z")
Yes update from 190 to 191 works. Samba is not working in 191 clean install. Can not change workgropup, wgui service shows warning. ---
**Author:** ![shazaam](https://community.ipfire.org/user_avatar/community.ipfire.org/shazaam/32/10034_2.png) [@shazaam](https://community.ipfire.org/u/shazaam)\ **Post date:** [5 February 2025 21:21 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/8 "2025-02-05T21:21:51Z")
OK, so looking like a clean install w/190 might be the fix. 191 has issues… ---
**Author:** ![arne\_f](https://community.ipfire.org/user_avatar/community.ipfire.org/arne_f/32/12760_2.png) [@arne\_f](https://community.ipfire.org/u/arne_f)\ **Post date:** [6 February 2025 06:47 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/9 "2025-02-06T06:47:21Z")
> [@digiz222](#): > > Samba is not working in 191 clean install. Can not change workgropup, wgui service shows warning. I cannot reproduce this. Also samba is an addon and has nothing to do with core190 or 191. At a fresh install the same samba-\*-107 addon will installed. ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [6 February 2025 16:22 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/10 "2025-02-06T16:22:08Z")
I did a fresh install of CU191 and then installed samba and had no problems. It installed and started. I also cannot reproduce the issue being talked about. ---
**Author:** ![digiz222](https://community.ipfire.org/user_avatar/community.ipfire.org/digiz222/32/15358_2.png) [@digiz222](https://community.ipfire.org/u/digiz222)\ **Post date:** [6 February 2025 18:32 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/11 "2025-02-06T18:32:04Z")
I saved settings before disabled samba, maybe this is a cause. I disabled samba next time, but it was to late. ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [6 February 2025 19:29 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/12 "2025-02-06T19:29:43Z")
> [@shazaam](#): > > nmbd smbd & winbind all fail to load the talloc library from: > > /usr/lib//samba/libtalloc.so.2 `TALLOC\_2.3.5’ I think you need to show us the actual error message that you got. libtalloc.so.2 is not in /usr/lib/samba/ it is in /usr/lib/ What do you get when you run the commands ```auto ls -hal /usr/lib/libtalloc* ls-hal /usr/lib/samba/libtalloc* ``` These will show the libtalloc libraries installed on the system you are having problems with. What do you get when you run ```auto ldd /usr/sbin/smbd | grep libtalloc ``` This will show which libtalloc libraries samba is linked to and where they are located. > [@digiz222](#): > > I saved settings before disabled samba, maybe this is a cause. You do not have to disable samba before doing a backup. I never have and have not had any problem when doing a backup or a restore. The backup does not save any of the libraries, so doing a restore will not change any of the libraries. ---
**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\ **Post date:** [6 February 2025 20:47 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/13 "2025-02-06T20:47:36Z")
> [@shazaam](#): > > /usr/lib//samba/libtalloc.so.2 `TALLOC\_2.3.5’ The more I investigate the more peculiar your error message is. IPFire updated libtalloc in the following steps: ```auto Core Update 173 1.3.1 to 1.3.4 Core Update 184 1.3.4 to 2.4.1 Core Update 190 2.4.1 to 2.4.2 ``` So version 2.3.5 has never been built in IPFire. I then went and looked in the [https://www.samba.org/ftp/talloc/](https://www.samba.org/ftp/talloc/) directory where the libtalloc source files are stored and version 2.3.5 has never existed. ![Screenshot_2025-02-06_21-38-17](https://community.ipfire.org/uploads/default/original/2X/c/ceecdbd3e77053f47d573af40d00e2818ee10d80.png) You need to make your system give that error message and then post the complete error message as it is shown. ---
**Author:** ![shazaam](https://community.ipfire.org/user_avatar/community.ipfire.org/shazaam/32/10034_2.png) [@shazaam](https://community.ipfire.org/u/shazaam)\ **Post date:** [9 February 2025 16:23 UTC](https://community.ipfire.org/t/core-update-191-and-samba/13549/14 "2025-02-09T16:23:38Z")
Well, I reloaded a fresh 191 & all is well. I have no idea how a bad version got there. This machine was last loaded w/2.27 & a long series of updates since then,