Florian Snow: > Package: mumble > Version: 1.3.0~git20190125.440b173+dfsg-2 > Severity: normal > Tags: patch upstream > > When calling the DBus method getCurrentUrl, it responds with an empty > string instead of a Mumble URL, like the call to getTalkingUsers > responds with a list of talking users. Here is the call I used: > > dbus-send --print-reply --session --type=method_call \ > --dest=net.sourceforge.mumble.mumble / \ > net.sourceforge.mumble.Mumble.getCurrentUrl > > The bug is also present in testing and sid. I fixed it upstream and I > am hoping for a point release so this can hopefully go into stable > updates or backports.
I'd like to know what risks and/or problems this bug poses, in order to understand how important this bug is and to figure out how it needs to be handled. If this is a security related bug, an upload for that would need to be coordinated with the Debian Security Team. Mumble-server / Murmur defaults to not using DBUS, and does not depend on it either for the package in Debian in order to allow not having DBUS installed. There shouldn't be an issue for default configurations, as far as I know. Mumble currently only has an "oldstable" backport right now, and no "stable" backport. For a bugfix to a backport to be allowed, the bug is required to be fixed in "testing" first, and the only way to get a package to "testing" is to upload it to "unstable". Any fix to "stable" requires the bug to be fixed in "unstable" first, and the bug has to be of more than "normal" severity and be a targeted-only fix with the individual patch provided in the request to the release team, with a detailed description of the issue and what problems it causes, as well as what testing the fix has had. Mumble upstream just released a 1.3.1-rc1 tarball today, so it's clear they're actively preparing a bugfix release. -- Chris -- Chris Knadle chris.kna...@coredump.us
