Bug 176421 - crash by startup of system
Summary: crash by startup of system
Status: RESOLVED DUPLICATE of bug 170519
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Unspecified
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: needs_verification
Depends on:
Blocks:
 
Reported: 2008-11-29 11:21 UTC by Dieter Pfeiffer
Modified: 2008-12-05 16:17 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dieter Pfeiffer 2008-11-29 11:21:08 UTC
Version:            (using KDE 4.1.3)
Installed from:    Ubuntu Packages

Anwendung: KSysTrayCmd (ksystraycmd), 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)
(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 0xb5d316c0 (LWP 6314)]
(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)
[KCrash handler]
#6  0xb7f6903e in NETRootInfo::update () from /usr/lib/libkdeui.so.5
#7  0xb7f696c3 in NETRootInfo::activate () from /usr/lib/libkdeui.so.5
#8  0xb7f58a25 in ?? () from /usr/lib/libkdeui.so.5
#9  0xb7f5c626 in KWindowSystem::connectNotify () from /usr/lib/libkdeui.so.5
#10 0xb787a5bf in QObject::connect () from /usr/lib/libQtCore.so.4
#11 0x0804ab74 in _start ()
#0  0xb7ff4430 in __kernel_vsyscall ()
Comment 1 Jordi Polo 2008-11-29 13:19:17 UTC
Can you try with debugging packages as stated here:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

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

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