Bug 213450

Summary: Make Samba easy to disable and enable
Product: [Frameworks and Libraries] kdenetwork-filesharing Reporter: KDE Brainstorm Submissions <brainstorm>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description KDE Brainstorm Submissions 2009-11-06 18:50:18 UTC
Version:            (using KDE 4.3.3)
Installed from:    I Don't Know

Hi all,

This is one thing that I think should be easy but it isn't: disabling Samba. In Windows, there is a checkbox for disabling file sharing, why not KDE?

Under Kubuntu 8.10, KDE 4.2.2 in System Settings, there is no place to find a checkbox that essentially says: "Enable/Disable Samba". Even the detailed "Samba" System Settings panel can configure everything else about Samba, but not this.

This kind of request has popped up over time, as searching Google for advice on how to disable Samba produces this top-rated page. It solves the problem by advising to uninstall Samba, which is what I had to do too. This doesn't seem intuitive, usable or safe ("will my settings be preserved if I want to reinstall?" "will I mess up the uninstallation process and harm my system?" are thoughts I had.) I tried looking for a CLI way to disable Samba, but gave up after I realized that it was out of the scope of my experience.

It would seem that the most logical place to put an "Enable Samba" checkbox would be in the System Settings -> Sharing panel. Actually, it would be more clear to say, "Enable file and printer sharing with Windows users", as the term "Samba" is a technical term that means nothing to newbies, myself included when I came to the Linux ecosystem.



This feature request was originally submitted through KDE Brainstorm, and has been submitted to Bugzilla due to popular demand. Original idea: http://forum.kde.org/brainstorm.php?mode=idea&i=61594
Comment 1 Nate Graham 2020-01-28 16:51:00 UTC

*** This bug has been marked as a duplicate of bug 288281 ***