-
Notifications
You must be signed in to change notification settings - Fork 206
Debugging problems
Ilia Bozhinov edited this page Mar 8, 2018
·
8 revisions
First identify which component causes the bug. It can be:
- A plugin - if the problem happens while using a plugin or it doesn't happen when a plugin is disabled
- Libweston - If a program crashes or doesn't show up at all, try using it in Weston. If the bug is present also there, then it is quite possible that it is a bug in libweston(but this doesn't happen very often).
- Otherwise it is a general wayfire bug
Important: If the bug is actually a crash, recompile with debugging enabled:
cd build
cmake ../ -DCMAKE_BUILD_TYPE=Debug -DUSE_GLES32=False
make && sudo make install
Then, when starting wayfire as follows: /<path_to_wayfire_binary>/wayfire log.txt
. This will generate a log file named log.txt
. Reproduce the bug and send the log file.