Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

net usershare returned error 255

Open
#490 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
linux
Domain
networking

Research direction

Start by reproducing the failure on LM20.3 with package version 5.2.4, using Nemo to share ~/Public and inspecting the generated ~/Public/log.net output. Trace the net usershare invocation and determine why the path is rejected; done means sharing ~/Public succeeds without error 255 or the invalid-characters message.

Written by the indexing model from the issue text.

Description

Distribution

LM20.3 cinnamon

Package version

5.2.4

Frequency

Always

Bug description

Fresh install of LM20.3, then fully updated. Installed samba from software manger. Then shared my public folder, resulting in the error message in the title.

A file log.net was created in ~/Public with the content:
net usershare add: share name /home/andy/public contains invalid characters (any of %<>*?|/\+=;:",)

Further details can be found here:
https://forums.linuxmint.com/viewtopic.php?p=2357813#p2357813

Steps to reproduce

As in the description

Expected behavior

For it to behave like it always has, i.e. work, in all previous versions of mint and in the current LM21. As part of a fresh install I routinely share ~/Public.

Additional information

Suspect irrelevant but LM installed on a thinkpad T430.

Dominant language
C
Stars
487
Forks
171
Avg merge
10d 19h
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxmint/nemo-extensions

All issues in linuxmint/nemo-extensions

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.