Bilal, You may not be familiar with this, but in Ubuntu there has been a tradition of not flapping bug status back and forth, so I think that reverting the reassignment without discussion was inappropriate (so I'm putting it back). While you're certainly entitled to your opinion about what Amarok should do, you've got an Amarok upstream telling you that's not the case.
Personally, I don't think it's reasonable for indicator-sound to expect the entire world to adjust to its notions of how things should work and indicator-sound should handle cases like this more gracefully, but the indicator-sound may not care to do that. I can see three possible package/status combinations that might be reasonably applied here: Amarok - Won't Fix Indicator Sound - New Indicator Sound - Won't Fix (if they choose not to address this case). Given that Amarok upstream has told you they don't view this as a bug, I do not think keeping it on the books as an open amarok bug is useful. ** Package changed: amarok (Ubuntu) => indicator-sound (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992262 Title: sound indicator not working after amarok close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/992262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
