Bug#956379: mumble: DBus call to getCurrentUrl responds with empty string

2020-04-11 Thread Chris Knadle
Florian Snow: > Hi Chris, > > Let me say first that this is my first time filing a bug with Debian and > I am not completely familiar with the process yet. So if I made a > mistake, please accept my apologies. Being that this is your first bug report please let me extend my thanks for taking the

Bug#956379: mumble: DBus call to getCurrentUrl responds with empty string

2020-04-11 Thread Florian Snow
Hi Chris, Let me say first that this is my first time filing a bug with Debian and I am not completely familiar with the process yet. So if I made a mistake, please accept my apologies. Chris Knadle writes: > I'd like to know what risks and/or problems this bug poses, in order to > understand

Bug#956379: mumble: DBus call to getCurrentUrl responds with empty string

2020-04-11 Thread Chris Knadle
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

Bug#956379: mumble: DBus call to getCurrentUrl responds with empty string

2020-04-10 Thread 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: d