Since the Ring GUI and daemon are separated processes, the easiest way to get logs from both is to start them one at a time, manually.
1. Ensure that no ring client or daemon instances are running with `ps aux | grep ring`
+Ring may still be running even if no windows are open depending on your preferences.
1. Ensure that no ring client or daemon instances are running with `ps aux | grep jami`
+Jami may still be running even if no windows are open depending on your preferences.
+ If either client or daemon are running, kill them with `kill PID`
2. On one terminal, start the daemon with `dring -d -c`
+ This executable is normally not in the PATH, and on the Ubuntu packages, it is located at `/usr/lib/x86_64-linux-gnu/dring -d -c` or `/usr/lib/ring/dring -d -c`
2. On one terminal, start the daemon with `jamid -d -c`
+ This executable is normally not in the PATH, and on the Ubuntu packages, it is located at `/usr/lib/x86_64-linux-gnu/jamid -d -c` or `/usr/libexec/jamid -d -c`
3. In another terminal, start the client with (here is a Gnome example) `jami-gnome -d`
For getting a backtrace, you can run the program inside gdb:
̀ gdb -ex run jami-qt` or ̀ gdb -ex run jami-gnome` or `gdb -ex run --args /usr/lib/ring/dring -cd` depending the part you need to debug
̀ gdb -ex run jami-qt` or ̀ gdb -ex run jami-gnome` or `gdb -ex run --args /usr/libexec/jamid -cd` depending the part you need to debug
When it does crash, you can type `bt` then press **Enter**. And copy the backtrace to the issue. (or `thread apply all bt` is event better)
