Samba broken after latest security update 11.2

After the latest security update for the samba package was installed I can no longer login to my domain account.

Here’s the log entry:

Mar 25 09:29:45 mybox winbindd[4781]: [2010/03/25 09:29:45, 0] lib/fault.c:46(fault_report)
Mar 25 09:29:45 mybox winbindd[4781]: ===============================================================
Mar 25 09:29:45 mybox winbindd[4781]: [2010/03/25 09:29:45, 0] lib/fault.c:47(fault_report)
Mar 25 09:29:45 mybox winbindd[4781]: INTERNAL ERROR: Signal 11 in pid 4781 (3.4.3-3.2.1-2306-SUSE-SL11.2)
Mar 25 09:29:45 mybox winbindd[4781]: Please read the Trouble-Shooting section of the Samba3-HOWTO
Mar 25 09:29:45 mybox winbindd[4781]: [2010/03/25 09:29:45, 0] lib/fault.c:49(fault_report)
Mar 25 09:29:45 mybox winbindd[4781]:
Mar 25 09:29:45 mybox winbindd[4781]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Mar 25 09:29:45 mybox winbindd[4781]: [2010/03/25 09:29:45, 0] lib/fault.c:50(fault_report)
Mar 25 09:29:45 mybox winbindd[4781]: ===============================================================
Mar 25 09:29:45 mybox winbindd[4781]: [2010/03/25 09:29:45, 0] lib/util.c:1480(smb_panic)
Mar 25 09:29:45 mybox winbindd[4781]: PANIC (pid 4781): internal error
Mar 25 09:29:45 mybox winbindd[4781]: [2010/03/25 09:29:45, 0] lib/util.c:1584(log_stack_trace)
Mar 25 09:29:45 mybox winbindd[4781]: BACKTRACE: 19 stack frames:
Mar 25 09:29:45 mybox winbindd[4781]: #0 /usr/sbin/winbindd(log_stack_trace+0x1a) [0x7f97ccedbd5a]
Mar 25 09:29:45 mybox winbindd[4781]: #1 /usr/sbin/winbindd(smb_panic+0x1f) [0x7f97ccedbe1f]
Mar 25 09:29:45 mybox winbindd[4781]: #2 /usr/sbin/winbindd [0x7f97ccecb75d]
Mar 25 09:29:45 mybox winbindd[4781]: #3 /lib64/libc.so.6 [0x7f97ca651560]
Mar 25 09:29:45 mybox winbindd[4781]: #4 /usr/sbin/winbindd(rpc_pipe_np_smb_conn+0x4) [0x7f97ccfbc4e4]
Mar 25 09:29:45 mybox winbindd[4781]: #5 /usr/sbin/winbindd(rpccli_set_timeout+0x8) [0x7f97ccfb5358]
Mar 25 09:29:45 mybox winbindd[4781]: #6 /usr/sbin/winbindd(winbindd_lookup_names+0xb1) [0x7f97cce4d5e1]
Mar 25 09:29:45 mybox winbindd[4781]: #7 /usr/sbin/winbindd [0x7f97cce4d76f]
Mar 25 09:29:45 mybox winbindd[4781]: #8 /usr/sbin/winbindd [0x7f97cce4eb58]
Mar 25 09:29:45 mybox winbindd[4781]: #9 /usr/sbin/winbindd [0x7f97cce4f107]
Mar 25 09:29:45 mybox winbindd[4781]: #10 /usr/sbin/winbindd [0x7f97cce38fca]
Mar 25 09:29:45 mybox winbindd[4781]: #11 /usr/sbin/winbindd(winbindd_lookup_sid_by_name+0x23) [0x7f97cce2cc83]
Mar 25 09:29:45 mybox winbindd[4781]: #12 /usr/sbin/winbindd(winbindd_dual_lookupname+0xb1) [0x7f97cce59791]
Mar 25 09:29:45 mybox winbindd[4781]: #13 /usr/sbin/winbindd [0x7f97cce571c0]
Mar 25 09:29:45 mybox winbindd[4781]: #14 /usr/sbin/winbindd [0x7f97cce57728]
Mar 25 09:29:45 mybox winbindd[4781]: #15 /usr/sbin/winbindd [0x7f97cce5acf2]
Mar 25 09:29:45 mybox winbindd[4781]: #16 /usr/sbin/winbindd(main+0xd1d) [0x7f97cce24f8d]
Mar 25 09:29:45 mybox winbindd[4781]: #17 /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f97ca63da7d]
Mar 25 09:29:45 mybox winbindd[4781]: #18 /usr/sbin/winbindd [0x7f97cce22869]
Mar 25 09:29:45 mybox winbindd[4781]: [2010/03/25 09:29:45, 0] lib/fault.c:326(dump_core)
Mar 25 09:29:45 mybox winbindd[4781]: dumping core in /var/log/samba/cores/winbindd
Mar 25 09:29:45 mybox winbindd[4781]:

Any help would be greatly appreciated.

I assume you got version 3.4.3-3.2.1-2306-SUSE-SL11.2 from opensuse update which replaced version 3.4.2-1.1.3.1-2229-SUSE-SL11 from opensuse OSS. Several people in the forum including me had the same problems with Samba after the update. You need to downgrade all files back to 3.4.2-1.1.3.1-2229-SUSE-SL11 from opensuse OSS and all should be back to normal.

You could elevate the priority of opensuse-OSS in your repositories (giving a lower number) and then upgrade all files that show up on a samba search + cifs, that would work. For any file loaded in openSUSE, you can check the version tab and pick a different version up or down by file as an alternative. If you do not have the opensuse-OSS repository present, you need to add it back.

James,

Thanks for the reply. Downgrading the package fixed the problem. Now I just have the annoyance of yast prompting me to reinstall the security update that caused the problem, but I guess I can live with that.

Jim

I just had a similar problem. My problem was that it was asking for a login when I didn’t have one before. It was trying to treat my home network as a domain and asking for a login.

Took everything back for Samba and Cifs and everything works great again.

Thanks jdmcdaniel3.

Has anyone reported this I see the problem here too?

tried unix extensions = no

still not working and asks for log on to network when network is simple peer to peer

Can see Linux machine from Windows no problem.

Edit)
also web page 901 is not working

I have not reported the problem to anyone outside of talking about it here in the forum. I have duplicated the issue on two different computers with the solution still the same, down grading the Samba version. Oddly, the issue seems to kill the Samba Client from being able to browse the Workgroup even as Samba the Server still serves up your shared folders for everyone else to use.

Thank You,

I have got exactly the same issue. After upgrade I can’t browse through the Samba shares anymore because of the security issue. Thanks for this thread, this saved me a lot of border.

I have not down graded yet since I have been hoping that a fix may be forth coming.

I am quite new to Linux but how can you find out when there is a new update available that will fix this error ?

Well, if you have the updater running in the system tray it will tell you. Or go to Yast-Software Updates and manually check.

Thanks! I do have the updater running, but what is the risc off ending up with the same issue when run the updater. Or can you see that this error is fixed before you run the updater?

According to bugzilla the problem is known and fixed and just waiting to be tested and packaged. Got no idea about a time line. If you must have the functionality you need to drop back to the previous version and lock the package(s) but then you won’t get notified when the ultimate fix comes along, and you will just have to check every once in a while manually.

Do you have an ID on the bugzilla bug report?

591636

:wink:

You could use this method: Fixing “Authorization Dialog” bug in Samba for 11.2 - openSUSE Forums