SFTtech / SFTtech/openage

Failed to add inotify watch for some asset.

Open
#260 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug lang: c++ os: linux
Dominant language
Python
Stars
14.4k
Forks
1.3k
PR merge metrics
No merged PRs in 30d

Description

Trying to build the debug build on Arch Linux. When starting:

$ make run
...
DBG Texture has been loaded from assets/converted/Data/graphics.drs/4015.slp.png
INFO Loading meta file: assets/converted/Data/graphics.drs/4015.slp.docx
 ERR Error: WARN cpp/assetmanager.cpp:62 (std::shared_ptr<Texture> openage::AssetManager::load_texture(const std::string &), thread 0): Failed to add inotify watch for assets/converted/Data/graphics.drs/4015.slp.png
INFO cleanup container
CRIT Exception: Error: WARN cpp/assetmanager.cpp:62 (std::shared_ptr<Texture> openage::AssetManager::load_texture(const std::string &), thread 0): Failed to add inotify watch for assets/converted/Data/graphics.drs/4015.slp.png
Makefile:46: recipe for target 'run' failed
make: *** [run] Error 1

Any ideas?

(Would be great if I could get it to run, we'll probably do a small openage dev hackathon in Switzerland in 2 weeks.)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start at cpp/assetmanager.cpp:62 and reproduce the failure with make run on Arch Linux, using the asset path shown in the report. Trace why adding the inotify watch fails; done means the debug build starts successfully without the reported asset-watch exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, linux
Domain
game-dev, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.