Bug 172455 - Initially executing amarok generates a kde.crash file.
Summary: Initially executing amarok generates a kde.crash file.
Status: RESOLVED DUPLICATE of bug 171870
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-09 14:05 UTC by Steven Giles
Modified: 2008-10-10 22:24 UTC (History)
1 user (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 Steven Giles 2008-10-09 14:05:08 UTC
Version:           Version 1.92.2 (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages



Application: KDE Daemon (kded4), signal SIGABRT
(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 0xb622da80 (LWP 6332)]
(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)
(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  0xb7f85410 in __kernel_vsyscall ()
#7  0xb7e36085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb7e37a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7502367 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7502458 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7502505 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb47a29d2 in ?? () from /usr/lib/kde4/lib/kde4/kded_globalaccel.so
#13 0xb47a7ce6 in ?? () from /usr/lib/kde4/lib/kde4/kded_globalaccel.so
#14 0xb47a2fef in ?? () from /usr/lib/kde4/lib/kde4/kded_globalaccel.so
#15 0xb737e880 in ?? () from /usr/lib/libQtDBus.so.4
#16 0xb737fad6 in ?? () from /usr/lib/libQtDBus.so.4
#17 0xb73800fc in ?? () from /usr/lib/libQtDBus.so.4
#18 0xb73804aa in ?? () from /usr/lib/libQtDBus.so.4
#19 0xb7605c31 in QObject::event () from /usr/lib/libQtCore.so.4
#20 0xb6b64f9c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#21 0xb6b69bf9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#22 0xb7a73483 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#23 0xb75f60b9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#24 0xb75f7469 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#25 0xb75f768d in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#26 0xb762162f in ?? () from /usr/lib/libQtCore.so.4
#27 0xb659cdd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0xb65a0193 in ?? () from /usr/lib/libglib-2.0.so.0
#29 0xb65a074e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0xb76219f8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#31 0xb6bf8a25 in ?? () from /usr/lib/libQtGui.so.4
#32 0xb75f533d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#33 0xb75f54cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#34 0xb75f774d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#35 0xb6b64897 in QApplication::exec () from /usr/lib/libQtGui.so.4
#36 0xb7f7bc12 in kdemain () from /usr/lib/kde4/lib/libkdeinit4_kded4.so
#37 0x08048572 in _start ()
#0  0xb7f85410 in __kernel_vsyscall ()


###########################################################

In addition after this crash, you can't do a "CTRL-ALT F2" to get the run command tool. Logging out doesn't fix it.  Now, just realize as I am writing this, I didn't just log out and restart X session.  I rebooted and was able to activate the Command execute tool, but when executed Amarok it repeats the problem.
Comment 1 Steven Giles 2008-10-09 15:26:44 UTC
Was able to log out and restart X server and log back in was able to fix problem, but soon as start amarok back up it generates the same report.  To fix I exit out of amarok session and log back in and was able to start the run command tool "Ctr-Alt F2"
Comment 2 David Faure 2008-10-10 22:24:52 UTC

*** This bug has been marked as a duplicate of bug 171870 ***