Bug 176518

Summary:	KDE Daemon crashed signal 11 (SIGSEGV)
Product:	[Frameworks and Libraries] kdelibs	Reporter:	George Dvorak <gldvorak>
Component:	kded	Assignee:	David Faure <faure>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	finex, frank78ac, Regnaron
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description George Dvorak 2008-11-30 03:51:04 UTC

Version:           kded4 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Application: KDE Daemon (kded4), signal SIGSEGV
(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 0xb62238d0 (LWP 13912)]
[KCrash handler]
#6  0xb7f55b56 in memcpy () from /lib/tls/i686/cmov/libc.so.6
#7  0xbff7c674 in ?? ()
#8  0xb75b732d in ?? () from /usr/lib/libkio.so.5
#9  0xb75b509f in ?? () from /usr/lib/libkio.so.5
#10 0xb75b6fb3 in ?? () from /usr/lib/libkio.so.5
#11 0xb75b715b in ?? () from /usr/lib/libkio.so.5
#12 0xb7e09a60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb7e0a7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb7e44633 in QSocketNotifier::activated () from /usr/lib/libQtCore.so.4
#15 0xb7e0f637 in QSocketNotifier::event () from /usr/lib/libQtCore.so.4
#16 0xb6b858ec in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#17 0xb6b8d72e in QApplication::notify () from /usr/lib/libQtGui.so.4
#18 0xb78f7b2d in KApplication::notify () from /usr/lib/libkdeui.so.5
#19 0xb7df4e61 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#20 0xb7e1f70a in ?? () from /usr/lib/libQtCore.so.4
#21 0xb68b86f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb68bbda3 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb68bbf61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb7e1f478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#25 0xb6c1fea5 in ?? () from /usr/lib/libQtGui.so.4
#26 0xb7df352a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb7df36ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#28 0xb7df5da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#29 0xb6b85767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#30 0xb80460a6 in kdemain () from /usr/lib/libkdeinit4_kded4.so
#31 0x080485a2 in _start ()
#0  0xb807c430 in __kernel_vsyscall ()

Comment 1 Oliver Putz 2008-11-30 12:47:53 UTC

Hi and thanks for the bugreport. As the backtrace regrettably isnt very useful (missing debugging symbols), could you say what you were doing when the crash ocurred?

Comment 2 George Dvorak 2008-11-30 21:33:48 UTC

I was running Update Manager when the crash occurred.  When I run Update Manager now I get a window with the following message:

Could not download all repository indexes

The repository may no longer be available or could not be contacted because of network problems. If available an older version of the failed index will be used. Otherwise the repository will be ignored. Check your network connection and ensure the repository address in the preferences is correct.

Failed to fetch cdrom:[Kubuntu 8.10 _Intrepid Ibex_ - Beta i386 (20081001)]/dists/intrepid/main/binary-i386/Packages.gz  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Failed to fetch cdrom:[Kubuntu 8.10 _Intrepid Ibex_ - Beta i386 (20081001)]/dists/intrepid/restricted/binary-i386/Packages.gz  Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs
Some index files failed to download, they have been ignored, or old ones used instead.

Comment 3 Frank Reininghaus 2008-12-05 22:28:38 UTC

Probably a duplicate of bug 165548.

Comment 4 FiNeX 2008-12-30 14:04:27 UTC


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