Version: 2.0 (using KDE 4.1.3) OS: Linux Installed from: Ubuntu Packages I installed amarok 2.0 to my computer (ubuntu 8.10). Previous version of amarok works okay. When I try to start amarok it crash. I can only seen a starting picture and then program fails. Bug report: Application: Amarok (amarok), signal SIGSEGV [Thread debugging using libthread_db enabled] [New Thread 0xb48406c0 (LWP 7011)] [New Thread 0xb1df6b90 (LWP 7031)] [New Thread 0xb25f8b90 (LWP 7020)] [New Thread 0xb2df9b90 (LWP 7017)] [KCrash handler] #6 0xb5e8a5f7 in ?? () from /usr/lib/libQtSvg.so.4 #7 0xb5e92097 in ?? () from /usr/lib/libQtSvg.so.4 #8 0xb5e9272d in ?? () from /usr/lib/libQtSvg.so.4 #9 0xb5ea2e53 in QSvgTinyDocument::load () from /usr/lib/libQtSvg.so.4 #10 0xb5ea4a6a in QSvgRenderer::load () from /usr/lib/libQtSvg.so.4 #11 0xb5ea747e in QGraphicsSvgItem::QGraphicsSvgItem () from /usr/lib/libQtSvg.so.4 #12 0xb7e8f6f2 in MainControlsWidget (this=0x954ea38, parent=0x910a180) at /build/buildd/amarok-kde4-2.0/src/widgets/MainControlsWidget.cpp:55 #13 0xb7e90549 in MainToolbar (this=0x9566630, parent=0x0) at /build/buildd/amarok-kde4-2.0/src/widgets/MainToolbar.cpp:62 #14 0xb7dd856c in MainWindow::init (this=0x9140688) at /build/buildd/amarok-kde4-2.0/src/MainWindow.cpp:195 #15 0xb7dc2832 in App::continueInit (this=0xbf8445e4) at /build/buildd/amarok-kde4-2.0/src/App.cpp:553 #16 0xb7dc572c in App (this=0xbf8445e4) at /build/buildd/amarok-kde4-2.0/src/App.cpp:193 #17 0x0804c033 in main (argc=1, argv=0xbf844ae4) at /build/buildd/amarok-kde4-2.0/src/main.cpp:129 #0 0xb7f43430 in __kernel_vsyscall ()
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Also, what QT version do you have? Thanks :)
Yeah, sorry. From a developer perspective, the backtrace indicates that the problem is not within Amarok. Instead, something could be wrong with your KDE installation, or some other component. I'm closing the report since we developers are confident that it's not an Amarok bug.