Bug 253350 - Booting Up Crash
Summary: Booting Up Crash
Status: RESOLVED DUPLICATE of bug 170519
Alias: None
Product: ksystraycmd
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 267697 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-10-06 01:34 UTC by wdmlist
Modified: 2013-05-05 06:32 UTC (History)
4 users (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 wdmlist 2010-10-06 01:34:03 UTC
Application: ksystraycmd (KSysTrayCmd 0.1)
KDE Platform Version: 4.5.1 (KDE 4.5.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.32-25-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Booting up my computer, Applications running:
Dolphin, Evolution, GVSW, Kate, System Monitor, Synce KDE PDA Manager, HPLIP, Kopete, Network Manager, Klipper, Bluetooth, KDE Wallet Manager

-- Backtrace:
Application: KSysTrayCmd (ksystraycmd), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f30f99a073a in NETRootInfo::update (this=0x15145b8, dirty_props=<value optimized out>) at ../../kdeui/windowmanagement/netwm.cpp:2198
#7  0x00007f30f99a1433 in NETRootInfo::event (this=0x15145b8, event=<value optimized out>, properties=0x7fffc6f5ba70, properties_size=5) at ../../kdeui/windowmanagement/netwm.cpp:2070
#8  0x00007f30f99922ec in KWindowSystemPrivate::x11Event (this=0x1514590, ev=0x7fffc6f5c160) at ../../kdeui/windowmanagement/kwindowsystem_x11.cpp:136
#9  0x00007f30f9850dde in KAppX11HackWidget::publicx11Event (this=<value optimized out>, _event=0x7fffc6f5c160) at ../../kdeui/kernel/kapplication.cpp:915
#10 KApplication::x11EventFilter (this=<value optimized out>, _event=0x7fffc6f5c160) at ../../kdeui/kernel/kapplication.cpp:966
#11 0x00007f30f7ca2801 in qt_x11EventFilter (ev=0x7fffc6f5c160) at kernel/qapplication_x11.cpp:408
#12 0x00007f30f7cb2481 in QApplication::x11ProcessEvent (this=<value optimized out>, event=0x7fffc6f5c160) at kernel/qapplication_x11.cpp:3248
#13 0x00007f30f7cdee22 in x11EventSourceDispatch (s=0x1401b40, callback=<value optimized out>, user_data=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:146
#14 0x00007f30f3d298c2 in g_main_dispatch (context=0x1400920) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:1960
#15 IA__g_main_context_dispatch (context=0x1400920) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2513
#16 0x00007f30f3d2d748 in g_main_context_iterate (context=0x1400920, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2591
#17 0x00007f30f3d2d8fc in IA__g_main_context_iteration (context=0x1400920, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654
#18 0x00007f30f8b0a183 in QEventDispatcherGlib::processEvents (this=0x13e59e0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#19 0x00007f30f7cde78e in QGuiEventDispatcherGlib::processEvents (this=0x15145b8, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#20 0x00007f30f8adcdd2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#21 0x00007f30f8add1bc in QEventLoop::exec (this=0x7fffc6f5c490, flags=) at kernel/qeventloop.cpp:201
#22 0x00007f30f8ae126b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#23 0x00000000004061ff in main (argc=<value optimized out>, argv=<value optimized out>) at ../../ksystraycmd/main.cpp:139

Reported using DrKonqi
Comment 1 Dario Andres 2010-11-18 17:10:51 UTC
[Comment from a bug triager]
This looks like bug 170519 (which is marked as fixed).
Adding Christoph to the CC
Comment 2 Christoph Feck 2011-03-05 14:13:35 UTC
*** Bug 267697 has been marked as a duplicate of this bug. ***
Comment 3 Chao Feng 2013-05-05 06:32:40 UTC
Mark as duplication based on backtrace. 
Please reopen if it still exist.

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