TiddlyWiki / TiddlyWiki/TiddlyDesktop
ERR_INVALID_URL
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.9k
- Forks
- 136
- PR merge metrics
- No merged PRs in 30d
Description
When I launch TiddlyDesktop with ./nw in its own directory (or from my desktop launcher) I get:
This site can’t be reached
The web page at file://./nw%20--mixed-context%20--enable-spell-checking%20--allow-file-acce ss-from-files%20--allow-file-access%20--allow-file-cookies%20--disable-features=SuppressDifferentOriginSubframeJSDialogs%20--user-data-dir=/home/jfcaron/.config/TiddlyDesktop%20--no-sandbox%20--no-zygote%20--flag-switches-begin%20--flag-switches-end%20--nwapp=/home/jfcaron/Software/TiddlyDesktop-linux64-v0.0.16 might be temporarily down or it may have moved permanently to a new web address.
ERR_INVALID_URL
This is on Linux Mint 21 LTS. It started happening after a reboot but without having applied any updates. It actually started on 0.0.15.prerelease.4 but I updated to 0.0.16 and it still occurs.
I tried running nw with an absolute path (/home/jfcaron/Software/TiddlyDesktop-linux64-v0.0.16/nw) and I get a different error:
Your file couldn’t be accessed
It may have been moved, edited or deleted.
ERR_FILE_NOT_FOUND
Any help would be appreciated. I use TiddlyDesktop to organize my teaching notes and course management stuff.
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
No source file or test is named. Start by reproducing the launch from the TiddlyDesktop-linux64-v0.0.16 directory and desktop launcher on Linux Mint 21, comparing ./nw with the absolute path and the reported nw.js arguments. Done means identifying why startup produces ERR_INVALID_URL or ERR_FILE_NOT_FOUND and restoring a working launch path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100