Hi there,

can anyone please give me a hand how to get rid of these ugly messages *PER TRACK*:

Code: Select all

void Phonon::MediaObject::setCurrentSource(const Phonon::MediaSource&)  QUrl( "" ) 
setSource
setSource Error: MediaSource is empty.
void Phonon::MediaObjectPrivate::_k_currentSourceChanged(const Phonon::MediaSource&)
void Phonon::MediaObject::setCurrentSource(const Phonon::MediaSource&)  QUrl( "file:///media/sdb1/COLL2/billboard/Hall + Oates - Maneater.mp3"  ) 
setSource
setSource yeap, 'tis a local file or url "file"
stateChangedInternal newState: "BufferingState" previousState: "StoppedState"
loadMediaInternal "file:///media/sdb1/COLL2/billboard/Hall + Oates - Maneater.mp3"
stateChangedInternal newState: "StoppedState" previousState: "BufferingState"
void Phonon::MediaObjectPrivate::_k_currentSourceChanged(const Phonon::MediaSource&)
QString::arg: Argument missing: /PendingTrack, /org/mpris/MediaPlayer2
play
updateMetaData(): artist: 
updateMetaData(): title: Hall + Oates - Maneater.mp3
updateVolume Volume changed to -  20  From  20
stateChangedInternal newState: "PlayingState" previousState: "StoppedState"
updateDuration Length changing from  0  to  273471
updateDuration Length changing from  273471  to  274100
stateChangedInternal newState: "PlayingState" previousState: "PlayingState"

This is absolutely insane, unless you're a developer and you really want to dive in-depth into the matter.
But for the end-user? Come on...
I know I CANNOT blame Amarok nor its team for that, because it comes from the framework itself (or even directly somewhere from KDE or Qt core, who knows).

Yet I'd like to know how to get rid of this surge of messages.

The next attempt did not work at all:

Code: Select all

declare -x PHONON_BACKEND_DEBUG="0"
declare -x PHONON_DEBUG="0"
declare -x PHONON_VLC_DEBUG="0"
amarok

Phonon simply ignored my environment variables completely, and happily keeps printing all its junk...

Well, check your ~/.bashrc, apparently you added these at some point. See also http://techbase.kde.org/Development/Tut ... _Variables

And why do you run Amarok in debug mode? Just starting it with Alt+F2 is enough if you really only need the user mode. Don't run it from a konsole, then you will have no messages. That is what the end user is supposed to do.

No, there are even end users that only use the mouse for launching applications if they really must.
I do so much stuff in the console and once I'm into typing something else, I will NOT take the mouse and search for some stupid icon! No way!

And why do you run Amarok in debug mode?

Because I define "debug mode" as

Code: Select all

amarok --debug

and I don't expect Amarok to be in debug mode "just" because I decide to run it as "amarok" (without parameters) from the command line interface. That's my decision whether I type in the app name into the console, or type it in the Windoze-ish "Run" menu or even double-click with the mouse for each and everything like a WinDozer-to-the-core.

I have nothing against some debug output, but at this extent it is way too much.

Well, check your ~/.bashrc, apparently you added these at some point.

Why should I check my .bashrc?
Whether I type in the export lines manually or load them in indirectly via bashrc is swings and roundabouts. They'll get set as environment variables in either way. Hence, I don't quite get the deeper sense of your "hint".

If you added these variables in your ~/.bashrc then they will form part of the KDE Workspace environment - which will then be used to launch all proceeding applications, including Amarok.

If they are present in ~/.bashrc then you will need to logout and back in again in order for the environment to be reset.

Well, I don't use the mouse to start Amarok if I use Alt+F2, type Amarok there and hit the return key....
All these are purely keyboard actions, so please, stop being so aggressive and try it

You can silence most (not all, depends on how the code is handled) KDE debug output by using "kdebugdialog" and check "Disable debug output completely" (might not be the exact wording, but I don't use an en locale), followed by "OK". Notice that you may have to restart the application for the settings to take effect.