Well fms, as I'm talking to you we can go offline and go really academic if you want I have experts on that subject on the team, also phycologist and more and it's not about the bugs, but I really on my use testing. BUT I do understand what you say because I am the most disruptive with rules of them all but I really believe this doesn't apply to this case there's cases and cases, and the "learning factor" is also important, because even i f the doubt comes up, he soons realize that there was no mistake and this becomes a non-issue

Also, we could do a black theme with RED details every where (like somebodies favorite football team) that it wouldn't mean error / problem to the user who wanted to install it. I can assure you that. People have different perceptions and of course even with some " standarts" (yellow attention) they do adapt to changes when needed if the context shows no or small possibility of problem.

About the song problem: yes, this is the kind of problem. We know how to fix it, but we will need to write OUR media engine. It just a pain to rely on a third party application communication to it via dbus to have things working. A pain, believe me. If we had one person available I would place him doing the player right now. To make sure we can control this issues ( I have some really boring bugs bogging me : the play pause changing when changing songs, the track button appearing in the beginning and locking podcst playback, the time it takes to start up the media engine and much more )

Believe me I really "picky" to the errors also, and the dev guys get really pissed when I manage to find and ask like crazy to get them fixed.