Summary: | Scrobbling stops working after system crash kills amarok | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Benjamin M <alvanx> |
Component: | Services/Last.fm | Assignee: | Amarok Bugs <amarok-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dmeltzer.devel, kde, lfranchi |
Priority: | NOR | ||
Version First Reported In: | 2.3.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.3.2 | |
Sentry Crash Report: |
Description
Benjamin M
2010-09-11 19:09:40 UTC
This is a duplicate crash of the one in bug 245513. Please see comment #27 and try again, this should be solved already. The only applet mentioned in #27 that I use would be the album applet, so I guess I will have to disable it to prevent the crash (the only other applet I use wikipedia). But does that also mean that the last.fm problem would be fixed? It seems this is a seperate problem triggered by the crash, but you didn't say if it is also caused by the crash. I don't care about the crash and I can wait until 2.3.2, but I would like scrobbling to work... Sorry, I might have sounded as if this scrobbling problem were solved, but only intended to give you a workaround to prevent the crash. The problem is to find out why the scrobbling doesn't work anymore after a crash, which would need a console output. Could you please try reproducing the crash and start Amarok in a terminal twice with the following options: -d --nofork You need to run it twice to have the debugging output enabled, so maybe do this first, then, try reproducing the crash Ok, thank you for the clarification! I will provide you with the log as soon as one little obstacle is out of the way. Konsole seems to display only a limited amount of lines, so the beginning of the output is cut off, if I am not mistaken. This happened even the second time I tried despite my checking of the third option (unlimited something) in the fourth tab from the left in the konsole profile settings (which I thought would fix it). So I guess it would help if somebody knew how to turn off this limitation. Well, why don't you redirect the output to a text file instead of copying it from konsole? I'm sorry, I tried to not be a noob about it and just find out how to do it by myself. The command string seems to be "amarok -d --nofork > amarok.txt" (for an output into the textfile "amarok.txt"), but the file stays empty. I'm gonna need some assistance with this... Sorry for the hassle. To redirect the output, try this: amarok -d --nofork 2> amarok_output.txt See also http://www.codecoffee.com/tipsforlinux/articles2/042.html Any news on this? Amarok 2.3.2 has been released in the mean time and you could also test Amarok 2.4 beta Sorry, I had gotten sidetracked from this. Basically, the bug wasn't around anymore after the 2.3.2 upgrade. Thanks anyway! :-) Thank you for the feedback. |