cutter/docs/common-errors.md

34 lines
1.7 KiB
Markdown
Raw Normal View History

2017-09-27 21:40:54 +00:00
# Common errors
2018-09-30 11:38:53 +00:00
This page lists common issues met by our users.
2017-09-27 21:40:54 +00:00
2018-09-30 11:38:53 +00:00
# AppImage crashes
2018-03-06 16:50:09 +00:00
2018-09-30 11:38:53 +00:00
If the linux AppImage binary crashes upon startup, make sure your `LD_LIBRARY_PATH` environment variable is empty. [#579](https://github.com/radareorg/cutter/issues/579)
2018-03-06 16:50:09 +00:00
2018-09-30 11:38:53 +00:00
# Compilation error
2017-09-27 21:40:54 +00:00
> r_core development package not found
If you installed radare2 and still encounter this error, could be your `PATH` environment variable is set improperly (doesn't contain `/usr/local/bin`). That can be, for example, due to `Qt Creator.app` being copied over to `/Applications`.
2018-09-30 11:38:53 +00:00
To fix this, append `:/usr/local/bin` to the `PATH` variable within the *Build Environment* section in Qt Creator. See the screenshot below should you encounter any problems.
2017-09-27 21:40:54 +00:00
2018-09-30 11:38:53 +00:00
On OS X you can also try:
2017-09-27 21:40:54 +00:00
2018-09-30 11:38:53 +00:00
- `PKG_CONFIG_PATH=$HOME/bin/prefix/radare2/lib/pkgconfig qmake`
- `PKG_CONFIG_PATH=$HOME/cutter/radare2/pkgcfg qmake` (for modern version and if radare2 was installed like the submodule)
2017-09-27 21:40:54 +00:00
2018-09-29 10:43:08 +00:00
![PATH variable settings](images/cutter_path_settings.png)
Or radare2 libs could be installed to `/usr/lib/pkgconfig/`, so you can add variable `PKG_CONFIG_PATH` with value `/usr/lib/pkgconfig/`
2017-09-27 21:40:54 +00:00
2018-09-30 11:38:53 +00:00
> OS X libjpeg error
On Mac, QT5 apps fail to build on QtCreator if you have the libjpeg lib installed with brew. Run this command to workaround the issue:
```
sudo mv /usr/local/lib/libjpeg.dylib /usr/local/lib/libjpeg.dylib.not-found
```
# Keyboard layout issue
2018-03-02 11:58:19 +00:00
Some people report that they have keyboard issues. Usually it is because the Xorg layout is wrong. You can check it with:
```setxkbmap -query``` Most of the time using ```setxkbmap us``` solves the issue, but it might not be enough and require some more advanced Xorg configuration.