[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Amarok 1.3.8-1 crashes on startup



I am having trouble getting the amarok 1.3.8-1 package running on my system. It crashes on startup every time I run it. I've tried wiping out the config files from .kde, but after I get through the first run wizard it crashes in the same manner, with the following:

libolt@tbird ~ $ amarok
amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp. QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
terminate called after throwing an instance of 'std::bad_alloc'
 what():  St9bad_alloc
KCrash: Application 'amarok' crashing...

I've run gdb on amarokapp and get the following backtrace:

libolt@tbird ~ $ gdb /usr/lib/amarok/amarokapp
GNU gdb 6.4-debian
Copyright 2005 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/lib/amarok/amarokapp
[Thread debugging using libthread_db enabled]
[New Thread 46912618815024 (LWP 26253)]
Qt: gdb: -nograb added to command-line options.
        Use the -dograb option to enforce grabbing.
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
terminate called after throwing an instance of 'std::bad_alloc'
 what():  St9bad_alloc

Program received signal SIGABRT, Aborted.
[Switching to Thread 46912618815024 (LWP 26253)]
0x00002aaaad207de0 in raise () from /lib/libc.so.6
(gdb) bt
#0  0x00002aaaad207de0 in raise () from /lib/libc.so.6
#1  0x00002aaaad209290 in abort () from /lib/libc.so.6
#2 0x00002aaaace02bf0 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #3 0x00002aaaace00c36 in __gxx_personality_v0 () from /usr/lib/libstdc++.so.6
#4  0x00002aaaace00c63 in std::terminate () from /usr/lib/libstdc++.so.6
#5  0x00002aaaace00d4a in __cxa_throw () from /usr/lib/libstdc++.so.6
#6  0x00002aaaace0103f in operator new () from /usr/lib/libstdc++.so.6
#7  0x00002aaaace010d9 in operator new[] () from /usr/lib/libstdc++.so.6
#8 0x00002aaaadd2f0e1 in QPNGImageWriter::writeImage () from /usr/lib/libqt-mt.so.3 #9 0x00002aaaadd2fb2a in QPNGImageWriter::writeImage () from /usr/lib/libqt-mt.so.3 #10 0x00002aaaadd2f272 in QPNGImageWriter::writeImage () from /usr/lib/libqt-mt.so.3
#11 0x00002aaaada58d97 in QImageIO::write () from /usr/lib/libqt-mt.so.3
#12 0x00002aaaada5c43f in QImage::doImageIO () from /usr/lib/libqt-mt.so.3
#13 0x00002aaaada5d6c6 in QImage::save () from /usr/lib/libqt-mt.so.3
#14 0x00000000004b0ce6 in QMap<QString, QString>::operator[] ()
#15 0x00000000004b2653 in QMap<QString, QString>::operator[] ()
#16 0x00002aaaadabf3a6 in QWidget::unsetFont () from /usr/lib/libqt-mt.so.3
#17 0x00002aaaadac0cd3 in QWidget::reparent () from /usr/lib/libqt-mt.so.3
#18 0x00002aaaadac0da0 in QWidget::reparent () from /usr/lib/libqt-mt.so.3
#19 0x00000000004604a3 in QValueListPrivate<QString>::~QValueListPrivate ()
#20 0x00000000005663f5 in QMapPrivate<QString, QPixmap>::QMapPrivate ()
#21 0x000000000045d93c in KToggleAction::metaObject ()
#22 0x00000000005ba091 in QWizard::setFinish ()
#23 0x00002aaaad1f44ca in __libc_start_main () from /lib/libc.so.6
#24 0x0000000000452cca in ?? ()
#25 0x00007fffffb779b8 in ?? ()
#26 0x00002aaaaabc29c0 in ?? () from /lib64/ld-linux-x86-64.so.2
#27 0x0000000000000001 in ?? ()
#28 0x00000000007f20f0 in ?? ()
#29 0x0000000000000000 in ?? ()


I'm running a custom compiled kernel 2.6.15 on a socket 754 Athlon 64 3200 on an asus k8v se deluxe motherboard. I am using the unstable tree. I submitted a bugreport a few weeks ago but never got a response. Any help is greatly appreciated. If there is anything more I can provide to help solve this problem let me know.

Mike McLean

!DSPAM:43fe653b243341750711582!



Reply to: