Bug 201355

Summary:	Eine korrekte Rückverfolgung ist nicht möglich. Wahrscheinlich sind die Dateien Ihres Systems in einer Weise erstellt worden, die eine solche Rückverfolgung (Backtrace) nicht erlaubt. Oder der so genannte „Stack Frame“ für das Programm wurde durch den Abs
Product:	[I don't know] kde	Reporter:	Stuart James Tetlow <torjt56>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	andresbajotierra
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Stuart James Tetlow 2009-07-24 15:41:32 UTC

Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

Eine korrekte Rückverfolgung ist nicht möglich.
Wahrscheinlich sind die Dateien Ihres Systems in einer Weise erstellt worden, die eine solche Rückverfolgung (Backtrace) nicht erlaubt. Oder der so genannte „Stack Frame“ für das Programm wurde durch den Absturz unbrauchbar gemacht.

[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(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)
(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)
0x00007fe2fb373cb0 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fe302559750 (LWP 4899))]

Thread 1 (Thread 0x7fe302559750 (LWP 4899)):
#0  0x00007fe2fb373cb0 in nanosleep () from /lib64/libc.so.6
#1  0x00007fe2fb373adc in sleep () from /lib64/libc.so.6
#2  0x00007fe30159d54f in ?? () from /usr/lib64/libkdeui.so.5
#3  0x00007fe30159deaa in KCrash::defaultCrashHandler(int) () from /usr/lib64/libkdeui.so.5
#4  <signal handler called>
#5  0x00007fe2ff97b838 in XGetWindowProperty () from /usr/lib64/libX11.so.6
#6  0x00007fe30165a5d6 in NETRootInfo::update(unsigned long const*) () from /usr/lib64/libkdeui.so.5
#7  0x00007fe30164bafd in ?? () from /usr/lib64/libkdeui.so.5
#8  0x00007fe30164f2bb in KWindowSystem::connectNotify(char const*) () from /usr/lib64/libkdeui.so.5
#9  0x00007fe3020a1087 in QObject::connect(QObject const*, char const*, QObject const*, char const*, Qt::ConnectionType) () from /usr/lib64/libQtCore.so.4
#10 0x0000000000403980 in _start ()

Comment 1 Dario Andres 2009-07-24 20:10:39 UTC

This is reported as bug 170519. 
For next crash reports mention which application crashed. Thanks

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