Bug 457523

Summary: Amarok crashes on attempting to open main window
Product: [Applications] amarok Reporter: James Carlson <carlsonj>
Component: generalAssignee: Amarok Bugs <amarok-bugs-null>
Status: RESOLVED WAITINGFORINFO    
Severity: crash CC: tuomas
Priority: NOR Keywords: drkonqi
Version First Reported In: 2.9.71   
Target Milestone: kf5   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description James Carlson 2022-08-05 13:15:32 UTC 
Application: amarok (2.9.71)

Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.14.21-150400.24.11-default x86_64
Windowing System: X11
Distribution: "openSUSE Leap 15.4"
DrKonqi: 5.24.4 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:

I launched Amarok via KDE menus. Instead of showing the main window (as expected), it showed an icon on the toolbar. When I clicked on the icon, it crashed. Relaunched multiple times, and it crashes every time. I was able to get it to play music exactly once by right-clicking and selecting "next track." But clicking on the icon again causes it to crash.

Thinking the problem was with my settings and/or saved data, I removed these:

rm -rf .kde4/share/apps/amarok .local/share/amarok .cache/amarok

Now, I can't play music with "next track," but the behavior is otherwise exactly the same. On launch, it starts in iconified state. Clicking the icon causes it to crash.

- Unusual behavior I noticed:

Apparently a failed assertion in session creation.

The crash can be reproduced every time.

-- Backtrace:
Application: Amarok (amarok), signal: Aborted

[KCrash Handler]
#4  0x00007f34df2bccdb in raise () from /lib64/libc.so.6
#5  0x00007f34df2be375 in abort () from /lib64/libc.so.6
#6  0x00007f34dfb3356b in qt_message_fatal (context=..., message=<synthetic pointer>...) at global/qlogging.cpp:1914
#7  QMessageLogger::fatal (this=this@entry=0x7fff10f8e4b0, msg=msg@entry=0x7f34dde11e85 "%s") at global/qlogging.cpp:893
#8  0x00007f34dde0dedd in QQuickWidgetPrivate::handleContextCreationFailure (this=this@entry=0x55b1def06eb0, format=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:885
#9  0x00007f34dde0e22d in QQuickWidgetPrivate::createContext (this=this@entry=0x55b1def06eb0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:917
#10 0x00007f34dde103be in QQuickWidget::resizeEvent (this=0x55b1dec4b120, e=<optimized out>) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:1263
#11 0x00007f34e0d3ddee in QWidget::event (this=this@entry=0x55b1dec4b120, event=event@entry=0x7fff10f8e9c0) at kernel/qwidget.cpp:8810
#12 0x00007f34dde1116b in QQuickWidget::event (this=0x55b1dec4b120, e=0x7fff10f8e9c0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2+kde43-150400.2.5.x86_64/src/quickwidgets/qquickwidget.cpp:1573
#13 0x00007f34e0cfd3ac in QApplicationPrivate::notify_helper (this=this@entry=0x55b1ddd1dca0, receiver=receiver@entry=0x55b1dec4b120, e=e@entry=0x7fff10f8e9c0) at kernel/qapplication.cpp:3632
#14 0x00007f34e0d041a0 in QApplication::notify (this=0x7fff10f8f8a0, receiver=0x55b1dec4b120, e=0x7fff10f8e9c0) at kernel/qapplication.cpp:3156
#15 0x00007f34dfd51ac3 in QCoreApplication::notifyInternal2 (receiver=0x55b1dec4b120, event=0x7fff10f8e9c0) at kernel/qcoreapplication.cpp:1064
#16 0x00007f34dfd51c9e in QCoreApplication::sendEvent (receiver=receiver@entry=0x55b1dec4b120, event=event@entry=0x7fff10f8e9c0) at kernel/qcoreapplication.cpp:1462
#17 0x00007f34e0d35f46 in QWidgetPrivate::sendPendingMoveAndResizeEvents (this=this@entry=0x55b1def06eb0, recursive=recursive@entry=false, disableUpdates=<optimized out>, disableUpdates@entry=false) at kernel/qwidget.cpp:7712
#18 0x00007f34e0d3a503 in QWidgetPrivate::show_helper (this=0x55b1def06eb0) at kernel/qwidget.cpp:7763
#19 0x00007f34e0d3a32b in QWidgetPrivate::show_recursive (this=<optimized out>) at kernel/qwidget.cpp:7693
#20 0x00007f34e0d3a440 in QWidgetPrivate::showChildren (this=this@entry=0x55b1deecda80, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8182
#21 0x00007f34e0d3a51f in QWidgetPrivate::show_helper (this=0x55b1deecda80) at kernel/qwidget.cpp:7769
#22 0x00007f34e0d3a32b in QWidgetPrivate::show_recursive (this=<optimized out>) at kernel/qwidget.cpp:7693
#23 0x00007f34e0d3a440 in QWidgetPrivate::showChildren (this=this@entry=0x55b1de1ac220, spontaneous=spontaneous@entry=false) at kernel/qwidget.cpp:8182
#24 0x00007f34e0d3a51f in QWidgetPrivate::show_helper (this=this@entry=0x55b1de1ac220) at kernel/qwidget.cpp:7769
#25 0x00007f34e0d3d653 in QWidgetPrivate::setVisible (this=0x55b1de1ac220, visible=<optimized out>) at kernel/qwidget.cpp:8112
#26 0x00007f34de5f856d in ?? () from /usr/lib64/libKF5Notifications.so.5
#27 0x00007f34de5f8960 in ?? () from /usr/lib64/libKF5Notifications.so.5
#28 0x00007f34de5f8c57 in KStatusNotifierItem::activate(QPoint const&) () from /usr/lib64/libKF5Notifications.so.5
#29 0x00007f34de5ff66b in ?? () from /usr/lib64/libKF5Notifications.so.5
#30 0x00007f34de6124d9 in ?? () from /usr/lib64/libKF5Notifications.so.5
#31 0x00007f34de612ab5 in ?? () from /usr/lib64/libKF5Notifications.so.5
#32 0x00007f34d7a813a8 in ?? () from /usr/lib64/libQt5DBus.so.5
#33 0x00007f34d7a84830 in ?? () from /usr/lib64/libQt5DBus.so.5
#34 0x00007f34d7a851ac in ?? () from /usr/lib64/libQt5DBus.so.5
#35 0x00007f34d7a87368 in ?? () from /usr/lib64/libQt5DBus.so.5
#36 0x00007f34dfd85cfb in QObject::event (this=0x55b1df278470, e=0x7f34a0004780) at kernel/qobject.cpp:1314
#37 0x00007f34e0cfd3ac in QApplicationPrivate::notify_helper (this=this@entry=0x55b1ddd1dca0, receiver=receiver@entry=0x55b1df278470, e=e@entry=0x7f34a0004780) at kernel/qapplication.cpp:3632
#38 0x00007f34e0d041a0 in QApplication::notify (this=0x7fff10f8f8a0, receiver=0x55b1df278470, e=0x7f34a0004780) at kernel/qapplication.cpp:3156
#39 0x00007f34dfd51ac3 in QCoreApplication::notifyInternal2 (receiver=0x55b1df278470, event=0x7f34a0004780) at kernel/qcoreapplication.cpp:1064
#40 0x00007f34dfd51c9e in QCoreApplication::sendEvent (receiver=receiver@entry=0x55b1df278470, event=event@entry=0x7f34a0004780) at kernel/qcoreapplication.cpp:1462
#41 0x00007f34dfd544e1 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55b1ddca8480) at kernel/qcoreapplication.cpp:1821
#42 0x00007f34dfd54a68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680
#43 0x00007f34dfdb4a33 in postEventSourceDispatch (s=0x55b1ddddbe40) at kernel/qeventdispatcher_glib.cpp:277
#44 0x00007f34cb7c17fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#45 0x00007f34cb7c1ba0 in ?? () from /usr/lib64/libglib-2.0.so.0
#46 0x00007f34cb7c1c2c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#47 0x00007f34dfdb40dc in QEventDispatcherGlib::processEvents (this=0x55b1dddd9cf0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#48 0x00007f34dfd5033a in QEventLoop::exec (this=this@entry=0x7fff10f8f720, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232
#49 0x00007f34dfd59b37 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375
#50 0x000055b1dbe08075 in main ()
[Inferior 1 (process 776) detached]

Possible duplicates by query: bug 419428, bug 410870.

Reported using DrKonqi
Comment 1 James Carlson 2022-08-05 13:20:51 UTC 
A broader web search suggests that maybe this is a Qt problem with Nvidia.

I used to run OpenSUSE Tumbleweed on this system, but after a hardware disaster, I rebuilt using the somewhat more stable OpenSUSE Leap.  On Tumbleweed, Amarok worked perfectly.

So, it's at least possible that this is a fixed bug in those libraries that just hasn't gotten back to the stable releases, but I don't know for sure.
Comment 2 Tuomas Nurmi 2024-03-24 07:54:59 UTC 
Superficially reading the backtrace, there doesn't seem to be necessarily anything directly Amarok specific code triggering this (although there could be some indirect cause)

However, seeing that Leap 15.4 is now EOL and succeeded by openSUSE Leap 15.5, do you still encounter this crash with a more recent system version?
Comment 3 Tuomas Nurmi 2024-03-30 08:12:01 UTC 
Closing as likely fixed by system updates. Please do not hesitate to reopen if you still encounter this with current versions.