Bug 191641

Summary: Fatal error:The application KRDC (krdc) crashed and caused the signal 11 (SIGSEGV).
Product: [Applications] krdc Reporter: dasvaik
Component: generalAssignee: Urs Wolfer <uwolfer>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Debian stable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description dasvaik 2009-05-05 03:52:59 UTC 
Version:           Version 4.1.4 (KDE 4.1.4) Using KDE 4.1.4 (KDE 4.1.4) (using KDE 4.1.4)
Compiler:          pplication: KRDC (krdc), signal SIGSEGV [Current thread is 0 (LWP 7060)]  Thread 2 (Thread 0xb47ffb90 (LWP 7061)): #0  0xb809d430 in __kernel_vsyscall () #1  0xb6abbdf1 in select () from /lib/tls/i686/cmov/libc.so.6 #2  0xb76bf150 in ?? () from /usr/lib/libQtCore.so.4 #3  0xb75ef6ae in ?? () from /usr/lib/libQtCore.so.4 #4  0xb658550f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5  0xb6ac3a0e in clone () from /lib/tls/i686/cmov/libc.so.6  Thread 1 (Thread 0xb61126c0 (LWP 7060)): [KCrash Handler] #6  0xb6d627ed in QAction::icon () from /usr/lib/libQtGui.so.4 #7  0x0807998f in _start () 
OS:                Linux
Installed from:    Debian stable Packages

The application KRDC (krdc) crashed and caused the signal 11 (SIGSEGV).

Application: KRDC (krdc), signal SIGSEGV
[Current thread is 0 (LWP 7060)]

Thread 2 (Thread 0xb47ffb90 (LWP 7061)):
#0  0xb809d430 in __kernel_vsyscall ()
#1  0xb6abbdf1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb76bf150 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb75ef6ae in ?? () from /usr/lib/libQtCore.so.4
#4  0xb658550f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb6ac3a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb61126c0 (LWP 7060)):
[KCrash Handler]
#6  0xb6d627ed in QAction::icon () from /usr/lib/libQtGui.so.4
#7  0x0807998f in _start ()
Comment 1 Dario Andres 2009-05-05 19:02:42 UTC 
This is fixed on KDE4.2.1+
Marking as duplicate of bug 179016
Thanks

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