| Summary: | Amarok crash during the startup | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | giggi1999 |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | john, leonardo.la.malfa, willfe |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | 2.5 | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
giggi1999
2011-08-09 06:03:17 UTC
You don´t have debugging symbols installed for Amarok. Please install those first and try again. Also please do not forget to specify which exact version of Amarok you are using in the bug report wizard. Closing for lack of feedback. Feel free to reopen this report if you can still reproduce this with current Amarok 2.4.3 or later and provide a valid backtrace. Created attachment 64524 [details]
New crash information added by DrKonqi
amarok (2.4.3) on KDE Platform 4.7.1 (4.7.1) using Qt 4.7.4
- What I was doing when the application crashed:
Amarok crashed on startup. Has been happening for a couple of days now, appeared for no reason I can tell.
Appears to be the same as linked bug report, hopefully my BT will provide enough information.
-- Backtrace (Reduced):
#6 QAbstractAnimation::state (this=0x7fb600000000) at animation/qabstractanimation.cpp:510
#7 0x00007fb64640ef31 in Context::ContextView::addCollapseAnimation(QAbstractAnimation*) () from /usr/lib/libamaroklib.so.1
#8 0x00007fb64640a5b4 in Context::Applet::collapse(bool) () from /usr/lib/libamaroklib.so.1
[...]
#13 0x00007fb6412e6927 in Plasma::DataContainer::dataUpdated (this=<optimized out>, _t1=<optimized out>, _t2=<optimized out>) at ./datacontainer.moc:112
#14 0x00007fb6412e6dfe in Plasma::DataContainer::checkForUpdate (this=0x1899660) at ../../plasma/datacontainer.cpp:297
John, please install the debugging symbols for Amarok and provide a better backtrace. Created attachment 65741 [details]
New crash information added by DrKonqi
amarok (2.4.3) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4
- What I was doing when the application crashed:
I started Amarok this morning, and it crashed.
-- Backtrace (Reduced):
#6 0x00007f8143a29424 in QAbstractAnimation::state (this=0x7f81180c62c0) at animation/qabstractanimation.cpp:510
#7 0x00007f8145514f31 in Context::ContextView::addCollapseAnimation (this=0x7f81180c5ee0, anim=0x1277190) at ../../src/context/ContextView.cpp:240
#8 0x00007f81455105b4 in Context::Applet::collapse (this=0x1e3bc30, on=<optimized out>) at ../../src/context/Applet.cpp:320
#9 0x00007f810fa0e6d2 in Albums::dataUpdated (this=0x1e3bc30, data=<optimized out>, name=<optimized out>) at ../../../../../src/context/applets/albums/Albums.cpp:155
#10 0x00007f810fa0f939 in Albums::dataUpdated (this=0x1e3bc30, name=<optimized out>, data=...) at ../../../../../src/context/applets/albums/Albums.cpp:132
Created attachment 72475 [details]
New crash information added by DrKonqi
amarok (2.5.0) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.1
I'm also seeing this issue; full debugging symbols are installed and should be included with this backtrace (the Crash Reporting Assistant claims the backtrace it generated is "useful", so I'm crossing my fingers ;)).
The application crashes every time it's started. Attempting to clear the playback queue by passing "-l file:///dev/null" doesn't appear to help. On the command line, the following messages are printed:
wferrell@stewie:~$ amarok -m
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work
Fading to 1
Transitioning to state "ready"
QWidget::insertAction: Attempt to insert null action
**********************************************************************************************
** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
** amarok --debug **
**********************************************************************************************
(the --debug output is excessively lengthy and I figured I'd omit it unless you think it'd be useful; if so, I can regenerate it upon request)
-- Backtrace (Reduced):
#6 QAbstractAnimation::state (this=0x61663d6e00000064) at animation/qabstractanimation.cpp:662
#7 0x00007f8eb68a24aa in Context::ContextView::addCollapseAnimation (this=0x3025960, anim=0x3a713d0) at ../../src/context/ContextView.cpp:245
#8 0x00007f8eb689effe in Context::Applet::collapse (this=0x3185dd0, on=<optimized out>) at ../../src/context/Applet.cpp:321
#9 0x00007f8e845ee180 in WikipediaApplet::dataUpdated (this=0x3185dd0, source=..., data=...) at ../../../../../src/context/applets/wikipedia/WikipediaApplet.cpp:742
#10 0x00007f8e845f1e5d in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at ./WikipediaApplet.moc:91
Folks, please stop adding debug outputs to a closed bug, All these are the same and are duplicates of a bug already solved in Amarok 2.6 Please everybody, read the backtrace, especially the bottom of it where there are links pointing in the right direction, but adding backtraces to closed bugs is pointless. *** This bug has been marked as a duplicate of bug 258741 *** Please accept my apologies; I didn't notice the [closed] attribute for this bug in the crash handler when it listed the potentially related bug reports. (In reply to comment #8) > Please accept my apologies; I didn't notice the [closed] attribute for this > bug in the crash handler when it listed the potentially related bug reports. Apologies accepted :) The status was set to RESOLVED which means the bug is closed |