[SOLVED] SWAT not talking to SMB anymore in ubuntu 12.04
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have ubuntu 12.04 on a few systems and I like to use SWAT to manage my SAMBA. However, since upgrading one machine to ubuntu 12.04 and recently on another machine with a fresh install of 12.04 SWAT doesnt work anymore. Specifically, SWAT is running and accessible but when I try to create a share I get a blank screen with nothing but SAMBA and a bar? I cannot view existing shares or globals either.
Its not the "root login" issue newbies often get. I can see all the options along the top after login.
Its not SAMBA because I can manually change my SMB.conf file and create new shares which are available and working.
Its not permissions on my smb.conf file because I tried setting that to 777.
Has anyone else lost functionality of swat like I have? (twice now on seperate machines) Anyone know what might have caused it and how to fix?
I'll try and attach a pic of the non-functional page (It appears after I select the basic or advanced button in "shares".
Given that the standard install methods posted (almost) everywhere for installing swat produce this "broken" form, I was truely surprised no one else had come across it. Then I found this bug report on the SAMBA site: https://bugzilla.samba.org/show_bug.cgi?id=8999
The upshot of which is that there is a bug in one of the SWAT dependancies but you can work around the bug with
sudo apt-get remove libpam-smbpass
NB: Your samba passwords will no longer be synced with your login passwords.
Last edited by mrpurple; 12-09-2012 at 06:22 PM.
Reason: spelling error