linuxmint / linuxmint/warpinator
Warpinator's do not connect to each other after cloning of installation.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.6k
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Description
Version and configuration:
ALL
Issue
After I cloned the installation from PC to Laptop Warpinator's did not found each other on network.
Issue is caused by unique identifier stored in /home/user/.config/warpinator/.group that does not change or is removed even after apt purge of Warpinator.
Steps to reproduce
Clone installation to other computer and use Warpinator.
Expected behaviour
apt purge warpinator* should remove unique identifier from /home/user/.config/warpinator/.groupfor reinstall.
Or better unique identifier could be cleared and regenerated in Warpinator settings.
Other information
Unique identifier in /home/user/.config/warpinator/.group that is not visible to user causes problems even after reinstall.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Warpinator creates and reads /home/user/.config/warpinator/.group, then compare that lifecycle with apt purge and reinstall behavior. Reproduce the issue by cloning an installation to another computer; done means cloned installations no longer share the identifier, and the identifier can be removed or regenerated as specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100