After Zypper ref and dup, serveral programs cannot work properly.

English Install/Boot/Login
#1

i don’t know why serveral programs cannot work properly after upgrading opensuse 11.3 to 11.4 by zypper ref and dup yesterday.

samba:
i cannot see samba shared driver in window 7, or even in opensuse 11.4. using “smbclient -L //127.0.0.1”, it reply “Error NT_STATUS_CONNECTION_REFUSED”.

libreoffice:
I cannot type anything in Libreoffice writer, but it does not affect firefox.

digikam:
it cannot start anymore after upgrading

Sorry for my chinese-english

#2

samba:
i cannot see samba shared driver in window 7, or even in opensuse 11.4. using “smbclient -L //127.0.0.1”, it reply “Error NT_STATUS_CONNECTION_REFUSED”.

there is an error in the implementation of Samba in openSUSE 11.4, which should be fixed in due course. Here’s the bug reference: https://bugzilla.novell.com/show_bug.cgi?id=666450

A temporary workaround is to turn off AppArmour. Go to Yast → Novell AppArmour → AppArmour Control Panel → untick the “enable” box.
Then reboot the computer and check that the samba daemons are running by entering this command in a terminal window:

su -c "rcnmb status; rcsmb status"
#3

You don’t have to disable App Armour, you can switch smb/nmb to “Complain” mode in the App Armour configuration.

#4

:slight_smile: Thanks Swerdna and Chrysantine, your quick and detailed supporting recover samba service, it is working good Now…

#5

That’s even better, thanks Chrysantine.

#6

I just tried it with switching the offending daemon (smbd) only, and it’s fine that way, so I suppose that’s the least I have to do (in terms of better security) to get Samba up and running.

#7

Hi –

I tried to do this but didn’t find a place in the App Armor configuration to do that. Is this in the control panel?

#8

yast → AppArmor → AA Control Panel → configure profile modes → highlight usr.sbin.smbd → toggle top complain → done → done and exit

#9

Thank you! It works now. BTW, for anybody else following this thread, some installations may be a little different. In mine, you get to the AA Control Panel via yast → Novell AppArmor → AA Control Panel . . . .

#10

I’m glad it’s working. Also, you’re correct with the pathway, I had an error – fixed now