Bug 177078 - at startup the bug comes up every time
Summary: at startup the bug comes up every time
Status: RESOLVED DUPLICATE of bug 170519
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-06 18:49 UTC by Paul
Modified: 2008-12-06 22:18 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul 2008-12-06 18:49:53 UTC
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Ubuntu Packages

Application: KSysTrayCmd (ksystraycmd), signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0xb5cd36c0 (LWP 7848)]
[KCrash handler]
#6  0xb7f0b03e in NETRootInfo::update (this=0x8bc96bc, dirty_props=0x8be3500)
    at /build/buildd/kde4libs-4.1.3/kdeui/windowmanagement/netwm.cpp:2140
#7  0xb7f0b6c3 in NETRootInfo::activate (this=0x8bc96bc)
    at /build/buildd/kde4libs-4.1.3/kdeui/windowmanagement/netwm.cpp:818
#8  0xb7efaa25 in KWindowSystemPrivate::activate (this=0x8bc96a8)
    at /build/buildd/kde4libs-4.1.3/kdeui/windowmanagement/kwindowsystem_x11.cpp:122
#9  0xb7efe626 in KWindowSystem::connectNotify (this=0x8be2d48, 
    signal=0x804d1e3 "2windowAdded(WId)")
    at /build/buildd/kde4libs-4.1.3/kdeui/windowmanagement/kwindowsystem_x11.cpp:348
#10 0xb781c5bf in QObject::connect () from /usr/lib/libQtCore.so.4
#11 0x0804ab74 in KSysTrayCmd::startClient (this=0xbf8a74e0)
    at /usr/include/qt4/QtCore/qobject.h:303
#12 0x0804b638 in KSysTrayCmd::start (this=0xbf8a74e0)
    at /build/buildd/kdebase-workspace-4.1.3/ksystraycmd/ksystraycmd.cpp:69
#13 0x0804cd53 in main (argc=2, argv=0xbf8a76f4)
    at /build/buildd/kdebase-workspace-4.1.3/ksystraycmd/main.cpp:132
#0  0xb7fa6430 in __kernel_vsyscall ()
Comment 1 Dario Andres 2008-12-06 22:18:55 UTC

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