On Sun, 2007-04-29 at 10:48 -0700, Joe Wreschnig wrote: > On Thu, 2007-04-26 at 21:51 +0200, Javier Kohen wrote: > > Package: quodlibet > > Version: 0.24-2 > > Severity: normal > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Since I upgraded from 0.23.1 yesterday, QuodLibet stopped responding to the > > multimedia keys (mmkeys). I still have quodlibet-ext installed and during > > the upgrade it pulled quodlibet-plugins along with it. > > > > The multimedia keys still work for other applications, such as Epiphany and > > gcalctool. > > Are there any other error messages, like "Error grabbing key 172, > 0x853bc00"? It seems GNOME may be intercepting all multimedia key > presses by default in some new version. In fact, they *shouldn't* work > in other applications -- the intention is that they work for Quod Libet > regardless of where your actual focus is.
Some relevant reading: https://bugs.launchpad.net/ubuntu/+source/quodlibet/+bug/43464 https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/32917 http://bugzilla.gnome.org/show_bug.cgi?id=395433 GNOME changed their multimedia key "API" in 2.18. Quod Libet isn't a GNOME application and wasn't using their API, but whatever they did seems to be breaking non-GNOME apps like Quod Libet and Amarok. So now we need to drink the GNOME kool-aid to get mmkey events. Or if we're lucky, this can be done as a plugin. It looks like it goes through D-Bus, but I can find absolutely zero documentation on it (which is not surprising, sigh). I fucking swear, I did just this a few days ago. And a few months before that. And a few months before that... Can someone on the release team please get the quodlibet package permission to ship an entire X + GTK + GStreamer implementation with the package, since clearly that's the only way to prevent these problems? -- Joe Wreschnig <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
