[wiki] Collecting debug information

This wikis intention is a work-in-progress to provide a handy and up-to-date list on how to collect debugging information (mainly logs). Everyones contributions are welcome!

This is maybe better placed in the sfos docs.

If something like this already exists, please let me know.

Basics:

Audio

  • systemctl status pulseaudio and journalctl -u pulseaudio

bluetooth

  • systemctl status mpris mpris is responsible for actions (play,pause,…)
  • systemctl status bluetooth and journalctl -u bluetooth

Android

  • systemctl status aliendalvik and journalctl -u aliendalvik

EMail

Mobile Data / Calling

  • logs journalctl -u ofono
7 Likes

Additionally for monitoring low memory behaviour it is good to monitor warnings sent my mce, from here: Mce | Sailfish OS Documentation
You will probably need devel-su pkcon install dbuslog-tools
The current state can be queried via:

dbus-send --system --type=method_call --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.get_memory_level

And tracked via:

dbus-monitor --system sender=com.nokia.mce,interface=com.nokia.mce.signal,member=sig_memory_level_ind

Also general useful Linux commands that can be useful here too is just running dmesg -w to see kernel messages, to diagnose boot for example.
And sudo journalctl -b -1 -r is useful to see what happened last boot, for example if phone restarted and we don’t know why.

2 Likes