Summary: | Crash when toggling unified view mode | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Myriam Schweingruber <myriam> |
Component: | Collection Browser | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | alpha_one_x86, aomegax, architect.adrian, benpro82, boldak.prasek, franklin, garystriplett, i-am-sergey, itrenor, jim, jreznik, maetryx, martin-schumann, maximilian.kossick, moritz-kdebugs, nagyesta, ophir.geffen, silentashes, Simon80, ulrik.mikaelsson |
Priority: | NOR | Keywords: | release_blocker |
Version: | 2.3-GIT | ||
Target Milestone: | 2.3.0 | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Myriam Schweingruber
2009-09-06 02:18:03 UTC
*** Bug 209217 has been marked as a duplicate of this bug. *** still valid with 2.2.0, more recent backtrace: Thread 1 (Thread 0x7fb682e05820 (LWP 13285)): [KCrash Handler] #5 size (this=<value optimized out>) at /usr/include/QtCore/qlist.h:87 #6 indexOf (this=<value optimized out>) at /usr/include/QtCore/qlist.h:633 #7 CollectionTreeItem::row (this=<value optimized out>) at /usr/src/debug/amarok-2.2.0/src/browsers/CollectionTreeItem.cpp:292 #8 0x00007fb681f321c6 in CollectionTreeItemModelBase::handleNormalQueryResult (this=0x4bd71c0, qm=0x4a15e60, dataList=...) at /usr/src/debug/amarok-2.2.0/src/browsers/CollectionTreeItemModelBase.cpp:798 #9 0x00007fb681f325dc in CollectionTreeItemModelBase::newResultReady (this=0x4bd71c0, collectionId=<value optimized out>, data=) at /usr/src/debug/amarok-2.2.0/src/browsers/CollectionTreeItemModelBase.cpp:677 #10 0x00007fb681f2e3f0 in CollectionTreeItemModelBase::qt_metacall (this=0x4bd71c0, _c=<value optimized out>, _id=3, _a=0x7fb624012c20) at /usr/src/debug/amarok-2.2.0/x86_64-redhat-linux-gnu/src/CollectionTreeItemModelBase.moc:87 #11 0x00007fb681643ec1 in QObject::event (this=0x4bd71c0, e=0x7fb6240132f0) at kernel/qobject.cpp:1110 #12 0x00007fb680abf6bc in QApplicationPrivate::notify_helper (this=0xed0ee0, receiver=0x4bd71c0, e=0x7fb6240132f0) at kernel/qapplication.cpp:4056 #13 0x00007fb680ac691e in QApplication::notify (this=<value optimized out>, receiver=0x4bd71c0, e=0x7fb6240132f0) at kernel/qapplication.cpp:4021 #14 0x00007fb682831b56 in KApplication::notify (this=0x7fff1efa4010, receiver=0x4bd71c0, event=0x7fb6240132f0) at /usr/src/debug/kdelibs-4.3.1/kdeui/kernel/kapplication.cpp:302 #15 0x00007fb68163490c in QCoreApplication::notifyInternal (this=0x7fff1efa4010, receiver=0x4bd71c0, event=0x7fb6240132f0) at kernel/qcoreapplication.cpp:610 #16 0x00007fb681635512 in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213 #17 QCoreApplicationPrivate::sendPostedEvents (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.cpp:1247 #18 0x00007fb68165d033 in sendPostedEvents () at kernel/qcoreapplication.h:218 #19 postEventSourceDispatch () at kernel/qeventdispatcher_glib.cpp:210 #20 0x00007fb67a4ff22e in g_main_dispatch (context=<value optimized out>) at gmain.c:1960 #21 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513 #22 0x00007fb67a502c18 in g_main_context_iterate (context=0xec2220, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 #23 0x00007fb67a502d3a in IA__g_main_context_iteration (context=0xec2220, may_block=1) at gmain.c:2654 #24 0x00007fb68165cca6 in QEventDispatcherGlib::processEvents (this=0xdb1bd0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #25 0x00007fb680b5208e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #26 0x00007fb681633242 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #27 0x00007fb681633614 in QEventLoop::exec (this=0x7fff1efa3fa0, flags=) at kernel/qeventloop.cpp:201 #28 0x00007fb6816357a9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #29 0x0000000000409d26 in main (argc=<value optimized out>, argv=0x7fff1efa5db8) at /usr/src/debug/amarok-2.2.0/src/main.cpp:225 *** Bug 209499 has been marked as a duplicate of this bug. *** *** Bug 210023 has been marked as a duplicate of this bug. *** *** Bug 210390 has been marked as a duplicate of this bug. *** Maximilian, any chance to get that fixed before 2.2.1? *** Bug 211523 has been marked as a duplicate of this bug. *** *** Bug 212559 has been marked as a duplicate of this bug. *** *** Bug 212677 has been marked as a duplicate of this bug. *** Fixed in upcoming 2.2.1. *** Bug 212819 has been marked as a duplicate of this bug. *** *** Bug 212899 has been marked as a duplicate of this bug. *** *** Bug 213686 has been marked as a duplicate of this bug. *** *** Bug 214916 has been marked as a duplicate of this bug. *** *** Bug 216064 has been marked as a duplicate of this bug. *** *** Bug 216663 has been marked as a duplicate of this bug. *** Why is this marked as fixed?? I just submitted a duplicate bug -- Amarok crashed for me, also. So what is the resolution? Any insight you could provide would be appreciate -- thanks!! - Joseph (In reply to comment #17) > Why is this marked as fixed?? > I just submitted a duplicate bug -- Amarok crashed for me, also. because it's fixed :) > > So what is the resolution? upgrade to amarok 2.2.1 ahhh okay, whoops somehow I missed that. Thanks! On Sun, Nov 29, 2009 at 05:59, Mikko C. <mikko.cal@gmail.com> wrote: > https://bugs.kde.org/show_bug.cgi?id=206445 > > > > > > --- Comment #18 from Mikko C. <mikko cal gmail com> 2009-11-29 14:59:43 > --- > (In reply to comment #17) > > Why is this marked as fixed?? > > I just submitted a duplicate bug -- Amarok crashed for me, also. > > because it's fixed :) > > > > > So what is the resolution? > > > upgrade to amarok 2.2.1 > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You are on the CC list for the bug. > *** Bug 217403 has been marked as a duplicate of this bug. *** *** Bug 218865 has been marked as a duplicate of this bug. *** Reopening based on a new report in Amarok 2.2.2 *** Bug 222966 has been marked as a duplicate of this bug. *** Backtrace from bug 222966: Thread 1 (Thread 0x7fb3cfabb770 (LWP 2934)): [KCrash Handler] #5 QListData::size (this=0x29ef2f0) at /usr/include/qt4/QtCore/qlist.h:87 #6 QList<CollectionTreeItem*>::indexOf (this=0x29ef2f0) at /usr/include/qt4/QtCore/qlist.h:633 #7 CollectionTreeItem::row (this=0x29ef2f0) at /build/buildd/amarok-2.2.2/src/browsers/CollectionTreeItem.cpp:295 #8 0x00007fb3ce966a24 in CollectionTreeItemModelBase::queryDone (this=0x2645090) at /build/buildd/amarok-2.2.2/src/browsers/CollectionTreeItemModelBase.cpp:679 #9 0x00007fb3ce96a985 in CollectionTreeItemModelBase::qt_metacall (this=0x2645090, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x2cf3580) at /build/buildd/amarok-2.2.2/obj-x86_64-linux-gnu/src/CollectionTreeItemModelBase.moc:86 #10 0x00007fb3ce9627a0 in CollectionTreeItemModel::qt_metacall (this=0x29ef2f0, _c=30515328, _id=7536640, _a=0x29ef2f0) at /build/buildd/amarok-2.2.2/obj-x86_64-linux-gnu/src/CollectionTreeItemModel.moc:67 #11 0x00007fb3cd4b10f9 in QObject::event (this=0x2645090, e=0x76ed460) at kernel/qobject.cpp:1111 #12 0x00007fb3cddc5efc in QApplicationPrivate::notify_helper (this=0x195fd10, receiver=0x2645090, e=0x76ed460) at kernel/qapplication.cpp:4056 #13 0x00007fb3cddcd1ce in QApplication::notify (this=0x7fffdf9b4260, receiver=0x2645090, e=0x76ed460) at kernel/qapplication.cpp:4021 #14 0x00007fb3ced498ea in App::notify (this=0x29ef2f0, receiver=0x1d1a080, event=0x6f006800730000) at /build/buildd/amarok-2.2.2/src/App.cpp:856 #15 0x00007fb3cd4a1c2c in QCoreApplication::notifyInternal (this=0x7fffdf9b4260, receiver=0x2645090, event=0x76ed460) at kernel/qcoreapplication.cpp:610 #16 0x00007fb3cd4a280a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x1837f60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213 #17 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x1837f60) at kernel/qcoreapplication.cpp:1247 #18 0x00007fb3cd4ca533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218 #19 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210 #20 0x00007fb3c6139bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #21 0x00007fb3c613d598 in ?? () from /lib/libglib-2.0.so.0 #22 0x00007fb3c613d6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #23 0x00007fb3cd4ca1a6 in QEventDispatcherGlib::processEvents (this=0x1837b90, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #24 0x00007fb3cde5a4be in QGuiEventDispatcherGlib::processEvents (this=0x29ef2f0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #25 0x00007fb3cd4a0532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #26 0x00007fb3cd4a0904 in QEventLoop::exec (this=0x7fffdf9b41f0, flags=) at kernel/qeventloop.cpp:201 #27 0x00007fb3cd4a2ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #28 0x000000000040a254 in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/amarok-2.2.2/src/main.cpp:235 The current source language is "auto; currently c". *** Bug 223785 has been marked as a duplicate of this bug. *** The backtrace above no longer matches the line numbers in the code from Git Master, so it's hard to tell if this is still valid (might be fixed), and what the actual crash is. A new backtrace from Git Master could help. I'm closing this for now, but we can reopen it if anyone could provide a good current backtrace, thanks. I can't reproduce this with current Amarok 2.2.3-git, build of today. *** Bug 225688 has been marked as a duplicate of this bug. *** *** Bug 227888 has been marked as a duplicate of this bug. *** *** Bug 232504 has been marked as a duplicate of this bug. *** It looks like I don't have privileges to reopen this bug, but there is clearly still a crasher lurking somewhere. If the line numbers in bug 232504 still don't line up, a fix can be made on the corresponding version that produced the backtrace, and then rebased onto the latest version of the source. |