It's definitely not a security issue, nor one of data loss... merely inconvenience with the network.
The issue seems to be a misconfiguration caused by one of the other samba configurators that I was using (Smb4K ... and before you ask, I have both Gnome and KDE on the same machine just for complexity's sake). My architecture is AMD64, so it's not a platform-specific bug, apparently. However, the nvidia driver is common between the two systems. I use the non-free one due to productivity needs. I noticed that the word "spoolss" was in the Samba config file, and on its own line. Additionally, I just had to run the recovery console to fix the sudoers file. In both cases, the issue was caused by the same piece of software which (rather than gracefully allowing for alterations) appears to be causing Samba to crash. I was hoping it would speed up my changes to the Samba config... apparently that is not the case. Ran the normal Samba config in order to try to detect/correct errors, but it crashed. Very inconvenient, since I'm on a deadline and need to pull stuff from the Windows-only company-owned laptop (as well as put it back when I'm done). Thus, any time taken to correct this bug is greatly and sincerely appreciated. -- system-config-samba.py crashed with SystemError in __init__() https://bugs.launchpad.net/bugs/185543 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
