Crash on open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 275
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I started fman on MacOS 10.12.6. and it crashed with no visible error message and this error in the logs.
Mar 27 11:00:52 isengard com.apple.xpc.launchd[1] (io.fman.fman.16656[4723]): Service exited with abnormal code: 255
Mar 27 11:01:04 isengard com.apple.xpc.launchd[1] (io.fman.fman.16656[4726]): Service exited with abnormal code: 255
Mar 27 11:03:21 isengard com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x10000050.fman[5250]): Service exited with abnormal code: 255
Mar 27 11:03:34 isengard com.apple.xpc.launchd[1] (io.fman.fman.16692[5262]): Service exited with abnormal code: 255
I started the app via terminal and saw this error
$ /Applications/fman.app/Contents/MacOS/fman
Traceback (most recent call last):
File "fman/main.py", line 11, in <module>
File "fman/main.py", line 7, in main
File "fman/impl/application_context.py", line 56, in run
File "fman/impl/application_context.py", line 408, in excepthook
File "fman/impl/application_context.py", line 214, in plugin_dirs
File "os.py", line 231, in makedirs
File "os.py", line 231, in makedirs
File "os.py", line 241, in makedirs
FileNotFoundError: [Errno 2] No such file or directory: '/Users/username/Library/Application Support/fman/Plugins'
[5530] Failed to execute script main
I recreated the directory ('/Users/username/Library/Application Support/fman/) to fix this. But it think it's better to inform the user somehow, why the app won't start, or just create the directory and move on.
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 in fman/impl/application_context.py at plugin_dirs and reproduce the startup failure on macOS when the fman application-support directory is absent. Determine the expected handling for the missing Plugins path, then verify that launching fman no longer exits with the reported FileNotFoundError or gives a visible error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100