On Thu, 2013-10-17 at 23:01 +0200, Christian Boltz wrote:
Hello,
Am Donnerstag, 17. Oktober 2013 schrieb lynn:
Thanks, yes, it is apparmor. Stopping it resolves the issue and smbd fires up OK. However, I already have the latest apparmor package 2.8.2-4.3.1 according to Yast at least.
It looks like the updated package was not published yet.
You should have
# rpm -q --changelog apparmor-profiles |head -n4 * Tue Oct 15 2013 opensuse@cboltz.de - add apparmor-profiles-samba4.diff - various profile additions for samba 4.x (bnc#845867, bnc#846054) - update usr.sbin.winbindd for samba 4.x (bnc#845867, bnc#846054)
Is there a workaround?
Install the apparmor-profiles package from the security:apparmor repo and reload the profiles with "rcapparmor reload".
Hi I have this: # rpm -q --changelog apparmor-profiles |head -n4 * Sun Sep 29 2013 opensuse@cboltz.de - update apparmor-init.py-gsoc.diff to the final GSoC apparmor/__init__.py * Fri Sep 20 2013 opensuse@cboltz.de That's not it I don't think. Will the patch(es) get into 13.1 without need for the security repo if I keep zypper dup'ing? Also, there is another error: Oct 17 23:25:46 altea smbd[546]: [2013/10/17 23:25:46.809451, 0] ../source3/printing/nt_printing.c:164(nt_printing_init) Oct 17 23:25:46 altea smbd[546]: nt_printing_init: error checking published printers: WERR_ACCESS_DENIED Thanks for your help, L x -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org