Bug#348168: calling rhythmbox with options doesn't work

Hi, On Tue, Jan 17, 2006, Alex Papadopoulos wrote: > after installing dbus, I still have this "strange" behaviour. Can you > please try to see if you have it too (just launch rhythmbox, play > something, minimize it (or just unfocus it) and in a terminal use (let's > say) rhythmbox --ne

Bug#348168: calling rhythmbox with options doesn't work

Hi there, after installing dbus, I still have this "strange" behaviour. Can you please try to see if you have it too (just launch rhythmbox, play something, minimize it (or just unfocus it) and in a terminal use (let's say) rhythmbox --next. If it comes up, then we have ourselves another bug

Bug#348168: calling rhythmbox with options doesn't work

Hi, On Sun, Jan 15, 2006, Alexis Papadopoulos wrote: >Here's the output cached in the terminal when typing "rhythmbox >--next" when another session of rhythmbox is already running : > >(rhythmbox:10590): Rhythmbox-CRITICAL **: couldn't connect to session bus: > Unable to dete

Bug#348168: calling rhythmbox with options doesn't work

Package: rhythmbox Version: 0.9.2-2 Severity: normal Hi there, I'm used to control rhythmbox using my keyboard by having some keys mapped to commands like "rhythbox --next". Since I've upgraded to 0.9.2-2 I get a dialog saying that the application has quit unexpectedly (the usual gnom