Package: libqmi Version: 1.18.0-1 Severity: normal Dear Maintainer,
libqmi 1.18.0-1 introduced a new function called __qmi_utils_get_driver in qmi-utils.c, which in turn calls g_file_test. This ends up being called during the test setup for test-generated suite. The problem is that g_file_test might receive a NULL path and glib2 version 2.53 (or later) introduced a non-NULL assert on it, causing the test setup to fail with: GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed. Upstream has already fixed it in commit 07da0340043b3b4d3ffc005e0a10b4776157a0fe [1], althoghno mention is made to the failed test it works just as well. [1] https://cgit.freedesktop.org/libqmi/commit/src/libqmi-glib/qmi-utils.c?id=07da0340043b3b4d3ffc005e0a10b4776157a0fe -- System Information: Debian Release: stretch/sid APT prefers artful APT policy: (500, 'artful'), (400, 'artful-proposed') Architecture: amd64 (x86_64) Kernel: Linux 4.10.0-21-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
