Bug 108740 - amarok crashes on startup
Summary: amarok crashes on startup
Status: RESOLVED FIXED
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 1.2.4
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-08 09:40 UTC by Joosep Pata
Modified: 2008-12-16 20:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joosep Pata 2005-07-08 09:40:47 UTC
Version:           1.2.4 (using KDE KDE 3.3.2)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc (GCC) 4.0.1 20050701 (prerelease) (Debian 4.0.0-12) 
OS:                Linux

amaroK crashes on startup. It shows me the splash screen then loads the UI and immediately crashes. The splash screen stays up until I click on it. It didn't happen before, but my PC just crashed and I had to do a reboot. Now after that it crashes. amaroK was running while the PC crashed, but no music was playing. When I run amaroK from Konsole I get this output:

amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& )
QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
KCrash: Application 'amarok' crashing...

I don't have amaroK compiled with debug symbols so a backtrace wouldn't probably mean a thing.
Comment 1 Alexandre Oliveira 2005-07-10 01:19:43 UTC
Ok, but without a backtrace there's nothing we can do about it, we can just gess what's happening, sorry.
Please consider reading http://amarok.kde.org/wiki/index.php/FAQ#How_can_I_obtain_a_decent_backtrace.3F and getting us a backtrace if possible.
Comment 2 Raphaël Pinson 2005-07-10 21:25:39 UTC
Just happened to me today. Amarok was playing. I restarted KDE and now amarok crashes at startup with *exactly* the same effects as described. I get the same output when launching from konsole. 

As for the backtrace, my version of amarok is from a debian unstable package, so I  guess the backtrace can't be used.
Comment 3 Raphaël Pinson 2005-07-10 21:48:06 UTC
Problem fixed by removing ~/.kde/share/config/amarokrc if that might help. Renaming ~/.kde/share/apps/amarok/ didn't help, so it might be a pb with amarokrc itself I guess.
Comment 4 Michael Fitzgerald 2005-07-16 10:40:43 UTC
I have also encountered this problem with the debian/unstable package, with a minor difference in the output ('cannot paint null pixmap'):

amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& )
QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QPainter::begin: Cannot paint null pixmap
KCrash: Application 'amarok' crashing...


If I rename amarokrc, the splash screen pops up, then the application crashes as in the original bug report (no null pixmap error).

I've attempted to rebuild with full-debug enabled in the debian source package, but am encoutering build errors and cannot yet obtain a backtrace.  -Mike
Comment 5 Joosep Pata 2005-07-18 14:12:12 UTC
Well I have  temporarily got rid of the bug by removing amarokrc, but accidentally I didn't keep the original amarokrc. I will try to reproduce the bug but I doubt I will succeed. Also I have the same problem with Juk(crashes on startup).
Comment 6 Keith Penrod 2005-09-01 17:24:03 UTC
I am actually using SuSE Linux, so I don't know if I need to start a new thread or what, but I have the same problem.  I tried deleting the amarokrc file and it still crashed.  I'm new to Linux and I don't even know how to compile anything with debug symbols, so for what it's worth I'm giving the backtrace.

[KCrash handler]
#7  0x080df1c6 in ContextBrowser::staticMetaObject ()
#8  0x0819d439 in amaroK::DcopPlayerHandler::staticMetaObject ()
#9  0x081a1ff0 in amaroK::Crash::crashHandler ()
#10 0x40e4f1f2 in DCOPClient::receive () from /opt/kde3/lib/libDCOP.so.4
#11 0x40e53e26 in DCOPClient::callAsync () from /opt/kde3/lib/libDCOP.so.4
#12 0x40e5447e in DCOPClient::processPostedMessagesInternal ()
   from /opt/kde3/lib/libDCOP.so.4
#13 0x40e552aa in DCOPClient::qt_invoke () from /opt/kde3/lib/libDCOP.so.4
#14 0x41174e7e in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x41175626 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x414ca619 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x4119a02f in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#18 0x41111d5f in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x41113a83 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40d9d6b1 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#21 0x4110650c in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x410bf286 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x41129e51 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x411138bf in QApplication::enter_loop ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x4130bb32 in QDialog::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x0808b9de in App::staticMetaObject ()
#27 0x08090f90 in App::staticMetaObject ()
#28 0x0819c788 in TrackPickerDialogBase::staticMetaObject ()
#29 0x41b80e80 in __libc_start_main () from /lib/tls/libc.so.6
#30 0x08086401 in ?? ()
Comment 7 Fatih Alabas 2005-09-09 20:07:48 UTC
One of the incompatible amarok plugins might cause the crash. Try removing the amarok-plugin rpms by YaST and install them again, but one by one and after each plugin installation try starting amarok...You may find it out... Good Luck...
Comment 8 kuede 2005-09-21 22:24:23 UTC
Removing the amarok-plugins did not solve the problem. Deleting the amarokrc made it only worse. My way was a bit longer (more than 3 days to be exactly):

I removed amarok and all plugins. Additionally I removed libvisual (probably not necessary). Then I searched for all amarok files rested in the filesystem. I removed all scripts, all setting files, all database files. What I left on my drive were the album covers.

After reinstallation amarok did not crash anymore.

BTW: My backtrace looked like the one in comment #7.
Comment 9 Mark Kretschmann 2005-09-22 10:03:11 UTC
Ok, thanks for testing. Closing.
Comment 10 Lore 2008-12-16 20:19:11 UTC
Application: Amarok (amarok), signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f9af0ddf740 (LWP 3757)]
[New Thread 0x42994950 (LWP 3763)]
[New Thread 0x42193950 (LWP 3762)]
[New Thread 0x410ec950 (LWP 3761)]
[New Thread 0x41992950 (LWP 3758)]
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f9aeccf49fd in QString::fromAscii_helper ()
   from /usr/lib64/libQtCore.so.4
#6  0x00007f9aeccf4a9e in QString::fromAscii () from /usr/lib64/libQtCore.so.4
#7  0x00007f9ad93f27df in ?? ()
   from /usr/lib64/kde4/libamarok_collection-sqlcollection.so
#8  0x00007f9ad93f3eb3 in ?? ()
   from /usr/lib64/kde4/libamarok_collection-sqlcollection.so
#9  0x00007f9ad93ce700 in ?? ()
   from /usr/lib64/kde4/libamarok_collection-sqlcollection.so
#10 0x00007f9af0905704 in CollectionManager::init ()
   from /usr/lib64/libamaroklib.so.1
#11 0x00007f9af0905c3d in CollectionManager::instance ()
   from /usr/lib64/libamaroklib.so.1
#12 0x00007f9af089f41d in ServiceFactory::ServiceFactory ()
   from /usr/lib64/libamaroklib.so.1
#13 0x00007f9ada1d7fd6 in create_plugin ()
   from /usr/lib64/kde4/amarok_service_shoutcast.so
#14 0x00007f9af09a185f in ?? () from /usr/lib64/libamaroklib.so.1
#15 0x00007f9af08b3c8f in ?? () from /usr/lib64/libamaroklib.so.1
#16 0x00007f9af08b46cd in ?? () from /usr/lib64/libamaroklib.so.1
#17 0x00007f9af086b156 in Playlist::Model::Model ()
   from /usr/lib64/libamaroklib.so.1
#18 0x00007f9af086bc3d in Playlist::Model::instance ()
   from /usr/lib64/libamaroklib.so.1
#19 0x00007f9af096680d in StatusBar::StatusBar ()
   from /usr/lib64/libamaroklib.so.1
#20 0x00007f9af0996edb in MainWindow::MainWindow ()
   from /usr/lib64/libamaroklib.so.1
#21 0x00007f9af097f78a in App::continueInit ()
   from /usr/lib64/libamaroklib.so.1
#22 0x00007f9af0980fb0 in App::App () from /usr/lib64/libamaroklib.so.1
#23 0x00000000004043f9 in _start ()
#0  0x00007f9ae62a3261 in nanosleep () from /lib64/libc.so.6