Bug 381301 - Samba sharing turns off on its own
Summary: Samba sharing turns off on its own
Status: RESOLVED DUPLICATE of bug 334875
Alias: None
Product: kdenetwork-filesharing
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: VHI critical
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2017-06-17 02:02 UTC by Nate Graham
Modified: 2019-05-17 22:16 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2017-06-17 02:02:58 UTC 
Dolphin Version: 16.12.3
kdenetwork-filesharing version: 16.12.3
Samba version: 4.5.8
Linux Distro: Kubuntu 17.04


Steps to reproduce:
1. Right-click on your home directory and choose Properties
2. Go to the Share tab
3. When prompted to install Samba, click Install and let it install necessary Samba packages (this is awesome)
4. Click "Share with Samba (Microsoft Windows)"
5.Click OK and close the Properties window
6. Go do something else for 5 minutes
7. Open the properties window for that folder again and click on the Share tab


Expected results:
The folder is still shared; "Share with Samba (Microsoft Windows)" is still checked.


Actual results:
"Share with Samba (Microsoft Windows)" has become unchecked all on its own!


Regression:
- Sharing turns off on its own only after a few minutes; if you immediately re-open the Properties window, it will still be on. It seems to take 2-5 minutes for me.
- Also, items chosen from the dropdown menus for what users can do (Full Control, Read Only, Deny) are forgotten immediately when you close the properties window.
- None of this happens with other folders I've tried; only my home folder (which is local, not on a separate partition).
Comment 1 Elvis Angelaccio 2017-07-07 14:58:52 UTC 
Moving to the new kdenetwork-filesharing product.
Comment 2 Nate Graham 2018-09-28 19:33:38 UTC 
*** Bug 339787 has been marked as a duplicate of this bug. ***
Comment 3 Nate Graham 2019-01-20 02:45:03 UTC 
*** Bug 403385 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2019-05-17 22:16:11 UTC 
Found the problem. If you have the correct packages for a running Samba server (which kdenetwork-filesharing takes care of), but that Samba server doesn't actually have any users set up on it, then the new share isn't actually enabled at all. SO the next time you open the dialog, it correctly notices that there isn't a share set up. From the user perspective, it looks like the share was enabled, but turned itself off. What was really going on was that it was never actually enabled in the first place, but the setup GUI didn't handle that error properly and tell the user that something had gone wrong.

The dialog should handle this condition as well. Duping this to the bug that tracks that.

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