| Summary: | Amarok crashes on first launch, scanner afterwards not working | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | t.schmittlauch |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | simonandric5 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | kf5 | ||
| Target Milestone: | 2.9 | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | stacktrace with debugsymbols | ||
|
Description
t.schmittlauch
2017-12-14 10:14:42 UTC
Created attachment 109374 [details]
stacktrace with debugsymbols
I rebuilt some libraries with debug symbols to get a more meaningful output
Since there are currently no release for the kf5 based version, not even alpha, it is far too early to file bug reports. Relevant part of the attachment (please always file crash reports in comments, lese those are not searchable): Thread 1 (Thread 0x7f6ee34ab840 (LWP 25772)): [KCrash Handler] #6 QAbstractScrollArea::verticalScrollBar (this=0x4ff6c00000000) at widgets/qabstractscrollarea.cpp:692 #7 0x00007f6ef8d0ce7d in ScriptSelector::verticalPosition (this=<optimized out>) at /tmp/portage/media-sound/amarok-9999/work/amarok-9999/src/configdialog/dialogs/ScriptSelector.cpp:55 #8 0x00007f6ef8d08922 in ScriptsConfig::restoreScrollBar (this=0x5613d14b5990) at /tmp/portage/media-sound/amarok-9999/work/amarok-9999/src/configdialog/dialogs/ScriptsConfig.cpp:235 #9 0x00007f6ef73c66f6 in QtPrivate::QSlotObjectBase::call (a=0x7fff37d3fac0, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:101 #10 QSingleShotTimer::timerEvent (this=0x5613d15ad890) at kernel/qtimer.cpp:318 #11 0x00007f6ef73b9afb in QObject::event (this=0x5613d15ad890, e=<optimized out>) at kernel/qobject.cpp:1268 #12 0x00007f6ef7c099ec in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x5613d15ad890, e=0x7fff37d3fd80) at kernel/qapplication.cpp:3722 #13 0x00007f6ef7c113bd in QApplication::notify (this=0x7fff37d40120, receiver=0x5613d15ad890, e=0x7fff37d3fd80) at kernel/qapplication.cpp:3481 #14 0x00007f6ef738ab4a in QCoreApplication::notifyInternal2 (receiver=0x5613d15ad890, event=event@entry=0x7fff37d3fd80) at kernel/qcoreapplication.cpp:1018 #15 0x00007f6ef73e37bb in QCoreApplication::sendEvent (event=0x7fff37d3fd80, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:233 #16 QTimerInfoList::activateTimers (this=0x5613d08b5060) at kernel/qtimerinfo_unix.cpp:643 #17 0x00007f6ef73e40e4 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:182 #18 0x00007f6eef13d3c7 in g_main_dispatch (context=0x7f6edc0016f0) at /tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3203 #19 g_main_context_dispatch (context=context@entry=0x7f6edc0016f0) at /tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3856 #20 0x00007f6eef13d630 in g_main_context_iterate (context=context@entry=0x7f6edc0016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3929 #21 0x00007f6eef13d6dc in g_main_context_iteration (context=0x7f6edc0016f0, may_block=may_block@entry=1) at /tmp/portage/dev-libs/glib-2.50.3-r1/work/glib-2.50.3/glib/gmain.c:3990 #22 0x00007f6ef73e43af in QEventDispatcherGlib::processEvents (this=0x5613d08dc560, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23 0x00007f6ef7389252 in QEventLoop::exec (this=this@entry=0x7fff37d3ffd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #24 0x00007f6ef7392824 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1291 #25 0x00005613cef7877a in main (argc=<optimized out>, argv=<optimized out>) at /tmp/portage/media-sound/amarok-9999/work/amarok-9999/src/main.cpp:347 Thank you for the crash report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! FWIW: I can't reproduce this here at all with the latest git build, likely solved a while ago already. |