Summary: | Amarok crashes when double-clicking on a track | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Xosé <xosecalvo> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | list, untitled.no4 |
Priority: | NOR | ||
Version: | 2.3.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Xosé
2010-06-28 19:44:45 UTC
Created attachment 48432 [details]
New crash information added by DrKonqi
amarok (2.3.0) on KDE Platform 4.4.90 (KDE 4.4.90 (KDE 4.5 RC1)) using Qt 4.7.0
- What I was doing when the application crashed:
Amarok switched to the second track. Can be reproduced manually by clicking on any track in the playlist.
-- Backtrace (Reduced):
#6 0x00007f82b21ff73c in QSortFilterProxyModelPrivate::proxy_to_source (this=0x2b46ff0, proxy_index=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:369
#7 0x00007f82b21ff85d in QSortFilterProxyModel::mapToSource (this=<value optimized out>, proxyIndex=...) at itemviews/qsortfilterproxymodel.cpp:2491
#8 0x00007f82b21f62e5 in QSortFilterProxyModel::buddy (this=0x2b464e0, index=...) at itemviews/qsortfilterproxymodel.cpp:1994
#9 0x00007f82b2170bb3 in QAbstractItemViewPrivate::sendDelegateEvent (this=0x2cf1190, index=..., event=<value optimized out>) at itemviews/qabstractitemview.cpp:4068
#10 0x00007f82b2171036 in QAbstractItemView::edit (this=0x2cf10e0, index=..., trigger=QAbstractItemView::DoubleClicked, event=0x7fffeff84db0) at itemviews/qabstractitemview.cpp:2533
Created attachment 48472 [details]
New crash information added by DrKonqi
amarok (2.3.0) on KDE Platform 4.4.90 (KDE 4.4.90 (KDE 4.5 RC1)) using Qt 4.7.0
- What I was doing when the application crashed:
Double clicking on a song from the playlist causes Amarok to crash. Happens every time.
-- Backtrace (Reduced):
#6 QSortFilterProxyModelPrivate::proxy_to_source (this=0x14db4b0, proxy_index=...) at itemviews/qsortfilterproxymodel.cpp:369
#7 0x00007fead468885d in QSortFilterProxyModel::mapToSource (this=<value optimized out>, proxyIndex=...) at itemviews/qsortfilterproxymodel.cpp:2491
#8 0x00007fead467f2e5 in QSortFilterProxyModel::buddy (this=0x14d3010, index=...) at itemviews/qsortfilterproxymodel.cpp:1994
#9 0x00007fead45f9bb3 in QAbstractItemViewPrivate::sendDelegateEvent (this=0x16768c0, index=..., event=<value optimized out>) at itemviews/qabstractitemview.cpp:4068
#10 0x00007fead45fa036 in QAbstractItemView::edit (this=0x1676810, index=..., trigger=QAbstractItemView::DoubleClicked, event=0x7fffd5b56580) at itemviews/qabstractitemview.cpp:2533
Please report this upstream at http://bugreports.qt.nokia.com, this is a bug in Qt 4.7. and give the bug link back here. Thank you. Thank you for the feedback. QT won't fix since crash is not in QT but in Amarok and because user (i.e. me) cannot provide useful information (i.e. backtrace is not enough). Maybe it would be best if an Amarok developer dealt with the QT people to begin with? Qt, not QT. Sorry, but this is out of our scope. Indicating Amarok as the test case should be enough. You should maybe stick to stable Qt versions instead of using beta software, aimed at testers. Oh, sorry, I didn't realise us mere mortals who are not developers are not allowed to be testers, I actually thought that the more people who test and report bugs the better it is, but it seems like it's not the case with Amarok. Oh well, it still seems to be appreciated with other KDE apps, so I'll stick to those and leave Amarok to the pros in the future. You misunderstood what I said: if you are using unstable software you should be aware that you are testing, so filing reports should be within your scope. And as I said, filing a bug upstream, indicating Amarok as a testcase should be enough. But if you are not willing to file reports upstream with the necessary information, then you should maybe not use Qt 4.7 beta. This does not depend on Amarok, you have a Qt bug here, out of our scope. *** This bug has been marked as a duplicate of bug 233726 *** |