If it's easy, send a patch to bugs.kde.org. If it's got no downside in other
use cases, I'll advocate they accept it. I suspect that Canonical/Ubuntu's
wishes aren't much of a priority for them, so sending a patch is probably the
only way this gets done.
--
You received this bug notification
@ seb128: Generally when I've worked with KDE based upstreams on these kinds
of issues they've been very open to resolving them when Canonical provided
patches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Which completely ignores that the entire world is not Ubuntu with sound
menus.
--
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 n
No. They have absolutely no ability to change Amarok. That's the point.
Amarok isn't going to be customized for Unity at the expense of it's primary
user base. How Unity needs to deal with that is up to them.
** Also affects: canonical-design
Importance: Undecided
Status: New
--
Sorry about that. I made a bad assumption based on what was in the bug.
--
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 notifica