Sebastien, I'd like to point out that, as I said in comment #3, even if we sidestep the question regarding the sanity of the specification itself, it's definitely a bug that the Rhythmbox package in Ubuntu currently implements the specification only partially, leading to inconsistent behaviour. The package does implement the part about exiting if the window is closed while not playing, but does not implement the part about maintaining state across sessions. I'm inclined to believe that the latter part was added to the specification exactly because it would otherwise severely disrupt the consistency of behaviour and the user's flow. See comment #3 for a real-world scenario; I can give more if you're not convinced.
I argue that, as far as any single application goes, the specification should only be implemented either fully or not at all. This particularly applies to a high-prevalence application such as Rhythmbox. If you consider this particular one not to be a bug, should we instead open a new one for the Rhythmbox in Ubuntu not implementing the specification fully? In relation to that, what's your understanding of how this inconsistency is going to be solved in the future? Is it just going to go away by itself in a future transition to Gnome 3? Or is the specification going to be fully implemented by Rhythmbox in Natty, thus perhaps making the behaviour consistent? Is that a realistic goal, seeing that Rhythmbox itself does little or nothing to implement full preservation of state? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658590 Title: Rhythmbox will not minimize to sound-indicator if music is not playing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
