Bug 103746

Summary: on starting amarok crashes
Product: [Applications] amarok Reporter: Sérgio Esteves <sroe>
Component: generalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Slackware   
OS: Linux   
Latest Commit: Version Fixed In:

Description Sérgio Esteves 2005-04-12 20:10:09 UTC
Version:           lastest (using KDE KDE 3.4.0)
Installed from:    Slackware Packages
OS:                Linux

root@darkstar:~# amarok
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
amarokapp: dl-close.c:365: _dl_close: Assertion `imap->l_type == lt_loaded || imap->l_opencount > 0' failed.
KCrash: Application 'amarokapp' crashing...
amaroK: [Loader] amaroK is taking a long time to load! Perhaps something has gone wrong?


BackTrace:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 6810)]
[New Thread 32769 (LWP 6811)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x41a10ef1 in kill () from /lib/libc.so.6
#7  0x4197bbb1 in pthread_kill () from /lib/libpthread.so.0
#8  0x4197bf2b in raise () from /lib/libpthread.so.0
#9  0x41a10b24 in raise () from /lib/libc.so.6
#10 0x41a123fd in abort () from /lib/libc.so.6
#11 0x41a0a00f in __assert_fail () from /lib/libc.so.6
#12 0x41ad574c in _dl_close () from /lib/libc.so.6
#13 0x41af477b in __libc_ptyname2 () from /lib/libc.so.6
#14 0x0000016d in ?? ()
#15 0x41af47eb in __libc_ptyname2 () from /lib/libc.so.6
#16 0x00000000 in ?? ()
#17 0x00000001 in ?? ()
#18 0x0000004d in ?? ()
#19 0x00000052 in ?? ()
#20 0x00000003 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00000000 in ?? ()
#23 0x00000000 in ?? ()
#24 0x00000008 in ?? ()
#25 0x0000000c in ?? ()
#26 0x4197ce70 in __pthread_lock () from /lib/libpthread.so.0

Description: A splashscreen appears and then the application crashes. I'm using slackware 10.1
Comment 1 Mark Kretschmann 2005-04-12 20:15:40 UTC

*** This bug has been marked as a duplicate of 100049 ***
Comment 2 Ian Monroe 2005-04-13 01:46:04 UTC
Please see the comment I wrote in Bug #100409 about obtaining a good backtrace, we're still waiting for one.