| Summary: | Crashes and stalls ... | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Roger March <roger> |
| Component: | general | Assignee: | Amarok Bugs <amarok-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | roger |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 2.8.0 | ||
| Target Milestone: | 2.9 | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Roger March
2015-04-15 22:04:01 UTC
Sadly your backtrace has no debugging symbols. Could you please install the package amarok-debuginfo an provide a better backtrace? See also https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#openSUSE Whoops, I will do so. It will probably crash soon so you will have a
nice fresh back trace.
Thanks.
On 04/15/2015 03:12 PM, Myriam Schweingruber wrote:
> https://bugs.kde.org/show_bug.cgi?id=346241
>
> Myriam Schweingruber <myriam@kde.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |NEEDSINFO
> Resolution|--- |BACKTRACE
>
> --- Comment #1 from Myriam Schweingruber <myriam@kde.org> ---
> Sadly your backtrace has no debugging symbols. Could you please install the
> package amarok-debuginfo an provide a better backtrace? See also
> https://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#openSUSE
>
Created attachment 92086 [details]
New crash information added by DrKonqi
amarok (2.8.0) on KDE Platform 4.14.6 using Qt 4.8.6
This just like the crash I reported earlier, this time I have included the back trace.
-- Backtrace (Reduced):
#6 0x00007fd1d50a1e88 in SqlRegistry::emptyCache() (o=..., this=0x7fffa1fec7d0) at /usr/include/ksharedptr.h:84
#7 0x00007fd1d50a1e88 in SqlRegistry::emptyCache() (this=0x1e48300) at /usr/src/debug/amarok-2.8.0/src/core-impl/collections/db/sql/SqlRegistry.cpp:933
[...]
#9 0x00007fd1f4e2d3b1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#10 0x00007fd1f535a76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#11 0x00007fd1f5360cad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
Created attachment 92087 [details]
New crash information added by DrKonqi
amarok (2.8.0) on KDE Platform 4.14.6 using Qt 4.8.6
This just like the crash I reported earlier, this time I have included the back trace.
-- Backtrace (Reduced):
#6 0x00007fd1d50a1e88 in SqlRegistry::emptyCache() (o=..., this=0x7fffa1fec7d0) at /usr/include/ksharedptr.h:84
#7 0x00007fd1d50a1e88 in SqlRegistry::emptyCache() (this=0x1e48300) at /usr/src/debug/amarok-2.8.0/src/core-impl/collections/db/sql/SqlRegistry.cpp:933
[...]
#9 0x00007fd1f4e2d3b1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#10 0x00007fd1f535a76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#11 0x00007fd1f5360cad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
Please always paste the full backtrace inline, or at least all of the relevant parts, else it is not searchable: Thread 1 (Thread 0x7fd1f7951800 (LWP 2651)): [KCrash Handler] #6 0x00007fd1d50a1e88 in SqlRegistry::emptyCache() (o=..., this=0x7fffa1fec7d0) at /usr/include/ksharedptr.h:84 #7 0x00007fd1d50a1e88 in SqlRegistry::emptyCache() (this=0x1e48300) at /usr/src/debug/amarok-2.8.0/src/core-impl/collections/db/sql/SqlRegistry.cpp:933 #8 0x00007fd1f4e291fa in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib64/libQtCore.so.4 #9 0x00007fd1f4e2d3b1 in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4 #10 0x00007fd1f535a76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #11 0x00007fd1f5360cad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4 #12 0x00007fd1f73bbcea in KApplication::notify(QObject*, QEvent*) (this=0x7fffa1fed0f0, receiver=0x19ac930, event=0x7fffa1fecd50) at /usr/src/debug/kdelibs-4.14.6/kdeui/kernel/kapplication.cpp:311 #13 0x00007fd1f4e152ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQtCore.so.4 #14 0x00007fd1f4e44cbc in () at /usr/lib64/libQtCore.so.4 #15 0x00007fd1f4e41f39 in () at /usr/lib64/libQtCore.so.4 #16 0x00007fd1eeb18a04 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #17 0x00007fd1eeb18c48 in () at /usr/lib64/libglib-2.0.so.0 #18 0x00007fd1eeb18cec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #19 0x00007fd1f4e420be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #20 0x00007fd1f53f7676 in () at /usr/lib64/libQtGui.so.4 #21 0x00007fd1f4e13e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #22 0x00007fd1f4e14165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #23 0x00007fd1f4e195b9 in QCoreApplication::exec() () at /usr/lib64/libQtCore.so.4 #24 0x0000000000407fb3 in () #25 0x00007fd1f4604b05 in __libc_start_main (main=0x401a40, argc=1, argv=0x7fffa1fed258, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffa1fed248) at libc-start.c:285 #26 0x00000000004080d2 in _start () Possible duplicates by query: bug 346241, bug 343167, bug 337714, bug 333574. Reported using DrKonqi this is already solved in the upcoming Amarok 2.9 *** This bug has been marked as a duplicate of bug 329011 *** |