Bug 171801

Summary:	ksystraycmd crash reported when hitting ctrl+C
Product:	[I don't know] kde	Reporter:	juanma <v0336es>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, v0336es
Priority:	NOR
Version First Reported In:	4.0
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description juanma 2008-09-28 17:06:50 UTC

Version:            (using KDE 4.0.5)
Compiler:          gcc 4.3.1  
OS:                Linux
Installed from:    SuSE RPMs

Using OpenSUSE 11, with all up-to-dates packages up to today.

While pressing Ctrl+C in a X console, a crash report window pops up informing about that the application ksystraycmd crashed and caused the signal 11 (SIGSEGV). After looking in several forums I could not find out someone having the same problem. Is this a bug or a failure in my system?

It happens not only in Console, but at any time and location!! (does not matter in which window the focus is) when the key combination is pressed.

Backtrace is:
[?1034h(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 0x7f126215d700 (LWP 4835)]
(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]
#5  0x0000000000000001 in ?? ()
#6  0x00007f1260ee7d38 in NETRootInfo::update () from /usr/lib64/libkdeui.so.5
#7  0x00007f1260ed803d in ?? () from /usr/lib64/libkdeui.so.5
#8  0x00007f1260edb86b in KWindowSystem::connectNotify ()
   from /usr/lib64/libkdeui.so.5
#9  0x00007f125f69bf88 in QObject::connect () from /usr/lib64/libQtCore.so.4
#10 0x00000000004037c0 in _start ()
#0  0x00007f125b371230 in nanosleep () from /lib64/libc.so.6


Any idea?

Cheers,

Juanma

Comment 1 juanma 2008-09-28 17:08:49 UTC

Running on a Dell 820 Core2 duo, with kernel 
Linux version 2.6.25.16-0.1-default (geeko@buildhost) (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1 SMP 2008-08-21 00:34:25 +0200

Comment 2 Dario Andres 2008-12-05 16:17:28 UTC

Can you still reproduce this bug with a recent KDE version? (4.1.3 / 4.2beta1 / 4.2 svn) ? Thanks :)
This may be related to bug 170519

Comment 3 Dario Andres 2008-12-25 17:32:36 UTC


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