Bug 1225522 - sharing a folder in nautilus gives a usershare failed error
Summary: sharing a folder in nautilus gives a usershare failed error
Status: NEW
Alias: None
Product: openSUSE Aeon
Classification: openSUSE
Component: Desktop Environment (show other bugs)
Version: Current
Hardware: x86-64 Other
: P5 - None : Minor
Target Milestone: ---
Assignee: Richard Brown
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-28 16:22 UTC by Müller
Modified: 2024-06-03 11:49 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
rbrown: needinfo? (hotel-brot.0z)
hotel-brot.0z: needinfo?


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Müller 2024-05-28 16:22:31 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:126.0) Gecko/20100101 Firefox/126.0
Build Identifier: 

sharing a folder in nautilus gives a usershare failed error:
Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled



Reproducible: Always

Steps to Reproduce:
1.create any folder for testing
2.right click on folder in nautilus -> Sharing Options -> Share this folder -> Create Share
Actual Results:  
Called "net usershare info" but it failed: »net usershare« returned error 255: net usershare: usershares are currently disabled

Expected Results:  
successful sharing of a folder

journalctl does not show more than the same error given above
Comment 1 Richard Brown 2024-05-28 16:41:21 UTC
According to https://www.suse.com/support/kb/doc/?id=000015945 that feature can only work if the machine is part of a domain

Does it work when part of a windows domain membership?
Comment 2 Müller 2024-05-28 16:45:30 UTC
unfortunately i can't test it, but at least the bug is registered now, at some point someone will surely test it
Comment 3 Richard Brown 2024-06-03 11:49:23 UTC
Reducing severity as suspicion this is not a bug but a misunderstanding how usersharing is meant to work and the mandatory requirement to join a Windows domain