Summary: | Amarok crashed while selecting music to be played | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Khris Roberts <robertsk3265> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bob, matej |
Priority: | NOR | ||
Version: | 2.4.3 | ||
Target Milestone: | 2.6 | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Khris Roberts
2012-04-26 04:06:42 UTC
Is this reproducible? Was this other track already loaded in the playlist? Else could you please tell the exact steps you did so we can try to reproduce this? FWIW: you should upgrade to Amarok 2.5, available in the Kubuntu-backports-PPA Created attachment 71736 [details]
New crash information added by DrKonqi
amarok (2.5.0) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1
- What I was doing when the application crashed:
Doubled clicked on a playlist file in the app and it crashed.
-- Backtrace (Reduced):
#7 0x00007fd33bcc2296 in operator= (p=0x0, this=0x25b1f70) at ../../include/QtCore/../../src/corelib/kernel/qpointer.h:68
#8 QMenuPrivate::activateAction (this=0x25b1cb0, action=0x25b21a0, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1133
#9 0x00007fd33b8c1144 in QWidget::event (this=0x25effd0, event=0x7ffff622e470) at kernel/qwidget.cpp:8362
#10 0x00007fd33bcc380b in QMenu::event (this=0x25effd0, e=0x7ffff622e470) at widgets/qmenu.cpp:2469
#11 0x00007fd33b870894 in notify_helper (e=0x7ffff622e470, receiver=0x25effd0, this=0x101b010) at kernel/qapplication.cpp:4559
(In reply to comment #2) > Created attachment 71736 [details] > New crash information added by DrKonqi > > amarok (2.5.0) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.1 > > - What I was doing when the application crashed: > > Doubled clicked on a playlist file in the app and it crashed. > > -- Backtrace (Reduced): .. Bob, please install the amarok debugging symbols and file a separate report, it is apparently not related to this one anyway, most likely not even related to Amarok as nothing in your backtrace indicates it. Also please do not add bug reports as duplicates if you are not 100% sure. Closing for lack of feedback. Please feel free to reopen this report if you can reproduce it with Amarok 2.6.0 or later and provide the requested information. *** This bug has been marked as a duplicate of bug 265626 *** |