Summary: | amarok 2.3.2 crashes on meta+b (next track) [@ Meta::Field::writeFields] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Serge Ratke <wuseldusel> |
Component: | Shortcuts | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 2.3.2 | ||
Target Milestone: | 2.4.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Serge Ratke
2010-11-07 17:43:58 UTC
Is this crash report what you got with the shortcut or is it the crash on startup? Also, can you reproduce this crash? this is the shortcut crash. i can't reproduce it reliably. but amarok crashes *very* often on me while switching to next track, either by shortcut or by itself. Thank you for the feedback. Switching rapidly by clicking is a known crash caused by Phonon, but yours doesn't indicate that. I looks more like a taglib issue as the crash is apparently in TagLibUtils.cpp it crashas no matter whether or not i'm swinging fast through the tracks or not. in fact -- as i said -- amarok crashes when playing one track after another, without me doing anything. and yes, i've seen the dump, and it looks like a problem with taglib. do you need some further information/data? I can't reproduce this here at all, using Amarok 2.4-git of today on KDE 4.5.3 on Kubuntu 10.10. Maybe it is caused by a specific taglib version, I have taglib 1.6.3-1 and taglib-extras 1.0.1 here. Make sure you don't have any older version still around. same lib versions here. could that be caused by me using two different programs to set the tags? i used to use picard, now i'm using puddletag. If the tagging software respects the standards this should not cause problems, but Picard is known to write strange entries in some obscure fields, this could indeed be related. Interesting, I didn't know puddletag but will have a look at it :) I just checked puddletag, have a look at the Stored Tags windo to see if there are some strange tags. This is indeed a taglib issue *** This bug has been marked as a duplicate of bug 216819 *** |