| Summary: | Amarok crashed after unminimizing from taskbar | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Vasco <Druid> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | alex.busenius, dallumn, domlyons, Druid, gkhanceylan, janiktomanek, zawertun |
| Priority: | NOR | ||
| Version: | 2.4.0.90 | ||
| Target Milestone: | 2.4.1 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.5 | |
| Sentry Crash Report: | |||
| Attachments: | New crash information added by DrKonqi | ||
|
Description
Vasco
2011-03-23 13:40:29 UTC
The problem is with Qt, which Qt version is your Amarok compiled with? This bug is rather old and should have been fixed with Qt 4.6.1, see also bug 207382 Setting status correctly Hello Myriam, this chrash/comment is related to my former Dr. Konqui report shown on: [1] https://bugs.kde.org/show_bug.cgi?id=266746 In [1] you wrote: >> Feel free to reopen this report if you can >> reproduce this crash with Amarok 2.4.0.90 or later and provide a valid >> backtrace. Doing as suggested leads us to this bugreport. You asked: >> The problem is with Qt, which Qt version is your Amarok compiled with? Answer: 4.7.2 I think. # rpm -q -R amarok (output abridged to increase readability) ... qt4-qtscript taglib >= 1.6 libtag-extras1 >= 1.0 kdebase4-runtime >= 4.6.1 libqt4-x11 >= 4.7.2 /sbin/ldconfig ... libQtCore.so.4 libQtDBus.so.4 libQtGui.so.4 libQtNetwork.so.4 libQtScript.so.4 libQtSql.so.4 libQtSvg.so.4 libQtWebKit.so.4 libQtXml.so.4 libX11.so.6 Let me know if I can help by providing further information. Thanks for caring. Thank you for the information. This is a problem with Qt, I strongly suggest you report this upstream or at least to your distribution. *** Bug 270229 has been marked as a duplicate of this bug. *** *** Bug 268851 has been marked as a duplicate of this bug. *** I'm suffering from the same bug, I have reported the problem to Qt here: http://bugreports.qt.nokia.com/browse/QTBUG-18021 I think it would help if other people who can reproduce this would comment/vote there. Also, they are asking for a Qt-only example, so if somebody has the knowledge and time to make it, please do so. *** Bug 274446 has been marked as a duplicate of this bug. *** *** Bug 274856 has been marked as a duplicate of this bug. *** *** Bug 275980 has been marked as a duplicate of this bug. *** Created attachment 61810 [details]
New crash information added by DrKonqi
amarok (2.4.1) on KDE Platform 4.6.5 (4.6.5) "release 8" using Qt 4.7.3
- What I was doing when the application crashed:
OK, so where should I report this bug? (blah blah blah, stupid limit)
- Unusual behavior I noticed:
- Custom settings of the application:
-- Backtrace (Reduced):
#6 QGraphicsSceneFindItemBspTreeVisitor::visit (this=0x2828360, items=0x2e8fd60) at graphicsview/qgraphicsscene_bsp.cpp:79
#7 0x00007f33cabcf640 in QGraphicsSceneBspTree::climbTree (this=0x2828220, visitor=0x2828360, rect=..., index=<value optimized out>) at graphicsview/qgraphicsscene_bsp.cpp:252
#8 0x00007f33cabcf640 in QGraphicsSceneBspTree::climbTree (this=0x2828220, visitor=0x2828360, rect=..., index=<value optimized out>) at graphicsview/qgraphicsscene_bsp.cpp:252
#9 0x00007f33cabcf5a0 in QGraphicsSceneBspTree::climbTree (this=0x2828220, visitor=0x2828360, rect=..., index=<value optimized out>) at graphicsview/qgraphicsscene_bsp.cpp:261
#10 0x00007f33cabcf640 in QGraphicsSceneBspTree::climbTree (this=0x2828220, visitor=0x2828360, rect=..., index=<value optimized out>) at graphicsview/qgraphicsscene_bsp.cpp:252
*** Bug 278072 has been marked as a duplicate of this bug. *** *** Bug 279069 has been marked as a duplicate of this bug. *** Git commit 30f670f11a130e1bd9a7eb60865dc4f67431ecd9 by Daniel Faust. Committed on 08/08/2011 at 16:10. Pushed by dfaust into branch 'master'. Use QGraphicsScene::NoIndex instead of QGraphicsScene::BspTreeIndex (avoid Qt bug crashing amarok) BUG: 207382 BUG: 269227 FIXED-IN: 2.4.4 M +2 -1 src/context/ContextView.cpp M +1 -0 ChangeLog http://commits.kde.org/amarok/30f670f11a130e1bd9a7eb60865dc4f67431ecd9 The problem seems to be related to moodbar. I did not experience the crash anymore since I deactivated moodbar a few days ago. *** Bug 283158 has been marked as a duplicate of this bug. *** *** Bug 284762 has been marked as a duplicate of this bug. *** |