Bug 163022

Summary:	crash of program, menu list stuck in middle with nothing showing
Product:	[Applications] kontact	Reporter:	Bradley Pierson <bpierson>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	christophe
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Linux
Latest Commit:		Version Fixed In:

Description Bradley Pierson 2008-06-01 20:27:12 UTC

Version:           4.0.3 (using KDE 4.0.4)
Installed from:    Mandriva RPMs
OS:                Linux

Application: Kontact (kontact), signal SIGABRT
(no debugging symbols found)
Using host libthread_db library "/lib/i686/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)
[Thread debugging using libthread_db enabled]
[New Thread -1259513296 (LWP 18182)]
[New Thread -1313612912 (LWP 18183)]
(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)
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 18182)]

Thread 2 (Thread -1313612912 (LWP 18183)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb54d11f1 in select () from /lib/i686/libc.so.6
#2  0xb6ac0d2c in QObject::disconnectNotify () from /usr/lib/libQtCore.so.4
#3  0xb69eedf9 in QObject::disconnectNotify () from /usr/lib/libQtCore.so.4
#4  0xb6898315 in start_thread () from /lib/i686/libpthread.so.0
#5  0xb54d8ede in clone () from /lib/i686/libc.so.6

Thread 1 (Thread -1259513296 (LWP 18182)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb5496ad6 in nanosleep () from /lib/i686/libc.so.6
#2  0xb54968be in sleep () from /lib/i686/libc.so.6
#3  0xb729b794 in QObject::disconnectNotify () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()

Comment 1 Thomas McGuire 2008-06-01 22:40:55 UTC

Sorry, but this bug report does not contain enough information.
What version of Kontact are you using?
Please describe what you were doing when Kontact crashed, and provide us with a useable backtrace, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 2 Christophe Marin 2008-11-19 13:22:55 UTC

Closing due to lack of feedback. (comment #1)