Summary: | Amarok crashed while using Automated Playlist Generator [@ ConstraintGroup::deleteTrack] | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Leonardo La Malfa <leonardo.la.malfa> |
Component: | Playlists/Automated Playlist Generator | Assignee: | Amarok Bugs <amarok-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | cfeck, daniel.falsetti, hugo.pereira.da.costa, optiluca, stharward |
Priority: | NOR | ||
Version First Reported In: | 2.3.1.90 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Leonardo La Malfa
2010-08-22 00:20:23 UTC
Which versions of Qt and kdelibs were you running? Can you run Amarok with debugging output (run "amarok --nofork --debug &> debug.log") and post the debugging log as an attachment here? > Which versions of Qt and kdelibs were you running? Qt Version: 4.7.0 kdelibs: while I took the former from this bug report, I'm not sure how to check this one. Can you please show me how to find that out? > Can you run Amarok with debugging output (run "amarok --nofork --debug &> > debug.log") and post the debugging log as an attachment here? Sure. Do you mean I should wait for another crash, then report back, or just report it in any case? Because I've tried a couple of times, already, and it doesn't seem to be reproducible. (In reply to comment #2) > > Which versions of Qt and kdelibs were you running? > Qt Version: 4.7.0 > kdelibs: while I took the former from this bug report, I'm not sure how to > check this one. Can you please show me how to find that out? The version of kdelibs is synonymous with the version of KDE. So just run any KDE application, and then select "Help > About KDE" and give me the version there. > > Can you run Amarok with debugging output (run "amarok --nofork --debug &> > > debug.log") and post the debugging log as an attachment here? > Sure. Do you mean I should wait for another crash, then report back, or just > report it in any case? Because I've tried a couple of times, already, and it > doesn't seem to be reproducible. Yeah, I need the debugging log from when it crashes. I can't reproduce it either, and even though I'm pretty sure I know what happened, the likely cause was something that shouldn't happen because I have measures in place in the code to prevent it from happening. Further question: did you change the constraint at all between when you ran it the first time and it didn't appear to work, and when you ran it again and it crashed? Did you even open the constraint editor dialog? > The version of kdelibs is synonymous with the version of KDE. So just run > any KDE application, and then select "Help > About KDE" and give me the > version there. OK, sorry, I'm still sort of a noob. Then it would be the same as in the bug report: 4.5 :) > Yeah, I need the debugging log from when it crashes. I can't reproduce it > either, and even though I'm pretty sure I know what happened, the likely > cause was something that shouldn't happen because I have measures in place > in the code to prevent it from happening. I've kept testing, and still nothing happened. I will keep doing so until it does. > Further question: did you change the constraint at all between when you ran > it the first time and it didn't appear to work, and when you ran it again > and it crashed? Did you even open the constraint editor dialog? It was the first time I tried that feature, I didn't even know what "constraint" exactly meant, go figure! And I haven't changed them afterwards, either. (In reply to comment #4) > > Yeah, I need the debugging log from when it crashes. I can't reproduce it > > either, and even though I'm pretty sure I know what happened, the likely > > cause was something that shouldn't happen because I have measures in place > > in the code to prevent it from happening. > I've kept testing, and still nothing happened. I will keep doing so until it > does. Okay. Right now, the existing safety checks make crashes "very unlikely", which isn't the same as "never". I've got some ideas for how to bolster them, but they're a few steps down the priority list. *** Bug 255927 has been marked as a duplicate of this bug. *** Confirmed by duplicate *** Bug 249175 has been marked as a duplicate of this bug. *** Not an oxygen bug I'd say. Crash occurs deep inside Qt via KIconLoader, triggered by a QCommonStyle call. Re-assigning to kdelibs, though it might also be Qt upstream. Who reads the backtrace? The crash is in Thread 12, in "ConstraintGroup::deleteTrack", which is from Amarok source, and neither in kdelibs, nor in Qt, nor in Oxygen. Reassigning back. @Christoph: please see comment #8, Aaron reassigned that to Oxygen on May 6th. I set it to the APG in Amarok earlier though, no idea why this was reassigned. Leonardo or Soren, is this still valid? (In reply to comment #11) > @Christoph: please see comment #8, Aaron reassigned that to Oxygen on May 6th. > I set it to the APG in Amarok earlier though, no idea why this was reassigned. > Leonardo or Soren, is this still valid? It was a one time crash, I didn't experience it anymore. Thank you for the feedback. |