https://bugzilla.novell.com/show_bug.cgi?id=443132 User aj@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=443132#c1 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |guillaume.gardet@opensuse.org --- Comment #1 from Andreas Jaeger 2008-11-09 05:59:17 MST --- Please add the YaST log files as explained at http://en.opensuse.org/Bugs/YaST -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443132 Andreas Jaeger changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |locilka@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=443132 User swerdna@opensuse-forums.org added comment https://bugzilla.novell.com/show_bug.cgi?id=443132#c4 John Andrews changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |swerdna@opensuse-forums.org --- Comment #4 from John Andrews 2008-12-20 18:34:08 MST --- How is this resolved please? It still exists as a bug, or at least it does for me. The only way I can allow Samba in openSUSE 11.1 is via Yast's etc/Sysconfig editor (or using a text editor on the config file). Since that's too hard for normal users, the bug makes Samba unusable in 11.1. Normal users think they have opened the firewall -- but they haven't. Why can't I see the progress in the "duplicate" bug 247344 or get some other knowledge of what's happening with this major bug? Please assist me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.