Troubleshooting and Support#

Troubleshooting#

Check the "changes" note on the wiki for new dependencies.
Please ensure you've completed all the steps in the installation guide.
Please read the Help section in the installation guide
There are a couple of articles on (rare) serial issues on the wiki:
- Serial USB Checklist
- Serial USB Rarely asked questions

Support#

How, where#

GitHub Issues preferred
INAV discord (#off-topic)
- Most likely you will be requested to raise a GitHub Issue for non-trivial cases or if there is an Information requirement. Hint, you can easily cut out the middle-man here.
See also Information requirements. Without this information, it is unlikely that any, non-trivial, support can be given.

Supported OS#

Arch Linux
Debian Stable and later (testing, sid)
Ubuntu latest and latest LTS (prior release where latest is also LTS).
Fedora latest
FreeBSD latest RELEASE
Supported Desktop Enviroment / Window Managers: basically must comply with XDG standards, specifically GNOME, KDE, xfce, LXqt, labwc, wayfire.

Supported infrastructure#

Native hardware (x64_x86, ia32, aarch64, riscv64).
Non-proprietary video driver.
qemu/kvm virtualised instances.
Little endian (big endian never tested).
Recent release of mwp

Information requirements#

Clear description of the issue#

A step of steps to reproduce the issue
The actual and expected outcomes
Include mwp's console log, from your home directory, mwp_stderr_YYYY-MM-DD.txt, e.g. $HOME/mwp_stderr_2021-12-28.txt. Do not delete any information from this file; the contents are there for a purpose, or paste the terminal output into a file (or copy paste into the issue). The terminal output may include information from system components that are not the mwp log (e.g. GDK / GTK / Wayland messages).
If your issue concerns telemetry, include a sample of data that causes the issue. Raw logs may be captured with the --raw-log option.
If you're having a problem playing a blackbox log (or other flight log), include the problematic log.

Issues that do not meet these information requirements most likely be ignored / closed without explanation.

Unsupported#

Anything else!

Problem reports on non-supported platforms may receive some consideration, however it's unlikely that too much time be expended on such environments unless the problem can also be demonstrated on a supported platform (or it's an interesting issue). Compliance with the Information requirements above is mandatory.

Wayland / XLib#

Different behaviours may be experienced using different display environments.

mwp (and other applications) can have a problem with OpenGL and the (GNOME) Wayland compositor. Typically this is manifest by being unable to pick mission WP icons for large (>40 point) missions. This problem does not appear on other compositors (wlroots and derivatives, WSL).

You can force Wayland / XWayland by setting the GDK_BACKEND variable in cmdopts (or the environment). This will override mwp's Windows Manager defined default behaviour.

# set XWayland
GDK_BACKEND=x11
# ** or **
# set Wayland
GDK_BACKEND=wayland

If that improves matters, add the setting to the configuration file.

mwp used Gtk+-3.0 and a number of no longer maintained components (gdl, champlain). There are no suitable Gtk4 replacements for these, so mwp remains stuck on Gtk+-3.0.

This means you may see a raft of scary messages on stderr, such as:

(org.stronnag.mwp:526430): Gdl-CRITICAL **: 17:47:12.509: gdl_dock_item_grip_realize: assertion 'grip->priv->label != NULL' failed

(org.stronnag.mwp:526430): Gtk-CRITICAL **: 17:47:12.555: gtk_widget_get_preferred_height: assertion 'GTK_IS_WIDGET (widget)' failed

This is unfixable in the context of mwp. See also this Github discussion.

Troubleshooting and Support#