amarok "current" tab problem

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

r_iliev

Beginner

Posts: 3

Saturday, September 24th 2005, 8:02am

amarok "current" tab problem

Amarok recently began playing funny tricks on me. The most annoying:

After a song begins to play (clicking on it either from the playlist or from the entries under "context >> home"), the "context >> current" tab appears empty. If I try to switch to other tabs under "context" - "lyrics" or "wikipedia", then amarok stops responding. However, if I play a radio-stream from the pre-set radio stream playlist, then all tabs under the "context" bar work fine ("context" displays properly, and "lyrics" attempts to fetch lyrics, etc).

The problem occurs with all engines I have used: xine, helix and arts. It is most benign with the "helix" engine. I did not have this problem initially. I believe (but am not sure...) it appeared when I updated to amarok 1.3.0 Maybe a problem with musicbrainz?

Thanks in advance to anyone willing to help!

rado

Amarok 1.3.0 and KDE 3.4.2 (from KDE-RedHat.org) under Fedora Core 3

Go to the top of the page

seb

Professional

Posts: 622

Location: Sydney

Occupation: Student

Wednesday, October 5th 2005, 3:20pm

see if you can get a back trace, here are the instructions:

http://amarok.kde.org/amarokwiki/index.php/Debugging_HowTo

if it hangs and doesnt crash, press ctrl-c in gdb during the freeze

http://www.sebruiz.net/
http://amarok.kde.org

This post has been edited 1 times, last edit by "seb" (Oct 5th 2005, 3:21pm)

Go to the top of the page

r_iliev

Beginner

Posts: 3

Saturday, October 8th 2005, 4:07am

backtrace

Thanks for the instrucitons, Seb!
I tried GDB. Strangely enough, with amarok running under GDB, the "current" menu miraculously begins to display proper info for the first played track (but never changes when the next track is selected/played)! When I start amarok (or amarokapp) outside of the gdb environment, the problem recurs again.

Instead of generating a backtrace, I started amarok from konsole. This gives me the following message as soon as the "current" malfunctions (i.e. as soon as I select it):

"[New Thread -229389392 (LWP 4500)]
Very strange! got a DCOPReply opcode, but we were not waiting for a reply!"

If this does not help, I'll attach a backtrace generated at this point precisely (w/o amarok crashing, cause it doesn't anymore).

thanks again!
rado

(edited for spelling and grammar)

This post has been edited 2 times, last edit by "r_iliev" (Oct 8th 2005, 5:55pm)

Go to the top of the page

seb

Professional

Posts: 622

Location: Sydney

Occupation: Student

Saturday, October 8th 2005, 3:43pm

Do you have a processor with HT enabled?

Try disabling the 'retrieve similar artists' option, in the last.fm configuration page, we've been finding some problems with it lately.

Seems related to this bug:
http://bugs.kde.org/show_bug.cgi?id=110921

http://www.sebruiz.net/
http://amarok.kde.org

Go to the top of the page

r_iliev

Beginner

Posts: 3

Saturday, October 8th 2005, 6:32pm

Problem solved!

I did what you suggested. Disabling the audioscrobbler option solved the problem. The current tab displays properly upon track changes. I don't get the DCOP call error anymore.

Thanks, Seb!

P.S. Processor is AthlonXP 2800 (barton).
I will test with other engines and post to the bug tracker if I again encounter similar behavior as the user there.

Go to the top of the page

seb

Professional

Posts: 622

Location: Sydney

Occupation: Student

Saturday, October 22nd 2005, 5:09pm

no probs. you'll also be glad to know that the upcoming 1.3.4 release (hopefully sunday) contains fixes to these problems.

http://www.sebruiz.net/
http://amarok.kde.org

Go to the top of the page