Summary: | Crash on double-clicking playlist item | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Eike Hein <hein> |
Component: | Playlist | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | langstr, nhn, peter.llorens, teo |
Priority: | NOR | ||
Version: | 2.3-GIT | ||
Target Milestone: | 2.3.1 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Eike Hein
2010-03-17 19:15:23 UTC
The backtrace seems similar to the one in bug 229240 with some line changes due to different QT version. So I guess this isn't fixed? It's possible that it has the same underlying cause, because reading the Qt source code it seems to involve a QPersistentModelIndex yet again. But the path is completely different. Hint to people trying to reproduce this: the lines in the crash dump indicate that an item edit was being started. You may need to move the mouse while you're double-clicking, to make it an item edit instead of an item select. I can not reproduce this (Qt 4.6). Interesting observations: - The crash dump does not contain any Amarok class names; it's all underlying generic Qt classes. - The crash dump is extremely similar to the one of Leo Franchi in comment #3 of BUG 228214. That went away when he upgraded Qt. - It runs aground at the very first QSortFilterProxyModel. That must be GroupingProxy, which is a dumb 1:1 passthrough of rows. I don't know the PrettyListView code well; it might be doing something nasty somewhere. But given the observations, I think that there's a significant chance of a bug in Qt. Ah! Qt 4.7 is not yet an official release of Qt, if I understand correctly? That would strengthen the suspicion. *** Bug 234591 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 229240 *** |