| Summary: | Show a better and more actionable error message when the sambashares path doesn't exist on disk or isn't accessible | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] kdenetwork-filesharing | Reporter: | `{third: "Beedell", first: "Roke"}`{.JSON5} <4wy78uwh> |
| Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | kfm-devel, nate, sitter |
| Priority: | NOR | Keywords: | usability |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | Pictographic depiction of what Dolphin states. | ||
|
Description
`{third: "Beedell", first: "Roke"}`{.JSON5}
2022-05-19 00:22:21 UTC
Urgh, yeah, I get it on Fedora too. This error message should really tell the user what *exactly* the problem is and how they can fix it. And if they can't, because it's a distro setup bug, it should tell them that too, and direct them to the distro bug report page, as Discover does in situations like this. (In reply to Nate Graham from comment #1) > Urgh, yeah, I get it on Fedora too. This error message should really tell > the user what *exactly* the problem is and how they can fix it. And if they > can't, because it's a distro setup bug, it should tell them that too, and > direct them to the distro bug report page, as Discover does in situations > like this. I wholeheartedly agree. I am thankful for your comment, because this is bothersomely problematic. Is testparm installed? Yes:
$ testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[I pressed enter]
# Global parameters
[global]
printcap name = cups
security = USER
workgroup = SAMBA
idmap config * : backend = tdb
cups options = raw
[homes]
browseable = No
comment = Home Directories
inherit acls = Yes
read only = No
valid users = %S %D%w%S
[printers]
browseable = No
comment = All Printers
create mask = 0600
path = /var/tmp
printable = Yes
[print$]
comment = Printer Drivers
create mask = 0664
directory mask = 0775
force group = @printadmin
path = /var/lib/samba/drivers
write list = @printadmin root
I feel like this is a variant of bug #425202 what happens if you actually enable usershares properly? From what I can see the only reason this cryptic message appears is if neither the share group nor the share path can be located - or simply put the plugin doesn't know what's wrong Not sure. I added "usershare max shares = 100" to the [global] section of /etc/samba/smb.conf and rebooted, but it didn't change anything. Was that the right way to do it, or is something else required? I honestly don't know I've only ever used distributions that set this stuff up. Not doing so in 2022 seems like a crime in its own right :( If "kdenetwork-filesharing" is installed, merely a cog is currently presented to me within the Share tab rather than the previously stated text. I have reinstalled my installation of Fedora, and I utilize Rawhide, so I expect that the default configuration of the operating-system and the code of the relevant packages is significantly different to what they were when I initially reported this problem. If useful, invocation of "testparm" by me provides: [root@1653307616 /]# testparm Load smb config files from /etc/samba/smb.conf Loaded services file OK. Weak crypto is allowed Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions # Global parameters [global] printcap name = cups security = USER workgroup = SAMBA idmap config * : backend = tdb cups options = raw [homes] browseable = No comment = Home Directories inherit acls = Yes read only = No valid users = %S %D%w%S [printers] browseable = No comment = All Printers create mask = 0600 path = /var/tmp printable = Yes [print$] comment = Printer Drivers create mask = 0664 directory mask = 0775 force group = @printadmin path = /var/lib/samba/drivers write list = @printadmin root [root@1653307616 /]# (In reply to BEEDELL ROKE JULIAN LOCKHART from comment #9) > If "kdenetwork-filesharing" is installed, merely a cog is currently > presented to me within the Share tab rather than the previously stated text. > I have reinstalled my installation of Fedora, and I utilize Rawhide, so I > expect that the default configuration of the operating-system and the code > of the relevant packages is significantly different to what they were when I > initially reported this problem. > > If useful, invocation of "testparm" by me provides: > > [root@1653307616 /]# testparm > Load smb config files from /etc/samba/smb.conf > Loaded services file OK. > Weak crypto is allowed > > Server role: ROLE_STANDALONE > > Press enter to see a dump of your service definitions > > # Global parameters > [global] > printcap name = cups > security = USER > workgroup = SAMBA > idmap config * : backend = tdb > cups options = raw > > > [homes] > browseable = No > comment = Home Directories > inherit acls = Yes > read only = No > valid users = %S %D%w%S > > > [printers] > browseable = No > comment = All Printers > create mask = 0600 > path = /var/tmp > printable = Yes > > > [print$] > comment = Printer Drivers > create mask = 0664 > directory mask = 0775 > force group = @printadmin > path = /var/lib/samba/drivers > write list = @printadmin root > [root@1653307616 /]# ...The label has reappeared, so ignore that section. I suppose that loading the configuration of Samba immediately subsequent to installation of the necessary package required some time. For posterity: how to enable it manually: https://wiki.archlinux.org/title/samba#Enable_Usershares *** This bug has been marked as a duplicate of bug 425202 *** |