Bug 189691 - crash due to dangling item pointer
Summary: crash due to dangling item pointer
Status: RESOLVED DUPLICATE of bug 192117
Alias: None
Product: Network Management
Classification: Miscellaneous
Component: Plasma Widget (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-15 09:12 UTC by marcela maslanova
Modified: 2009-07-31 19:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
network management crash (8.86 KB, text/plain)
2009-04-26 10:25 UTC, Valter Mura
Details
full backtrace (10.34 KB, text/plain)
2009-05-06 08:19 UTC, marcela maslanova
Details

Note You need to log in before you can comment on or make changes to this bug.
Description marcela maslanova 2009-04-15 09:12:01 UTC
Version:            (using KDE 4.2.2)
Compiler:          gcc-4.4.0-0.32.x86_64 
OS:                Linux
Installed from:    Fedora RPMs

After log in using kdm plasma crash. I have installed debuginfo so I hope the backtrace would be helpful.

[Thread debugging using libthread_db enabled]
[New Thread 0x7fec2ddc9910 (LWP 8386)]
0x00007fec4744f531 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7fec4a152820 (LWP 8377))]

Thread 2 (Thread 0x7fec2ddc9910 (LWP 8386)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x0000003c7985b19b in QWaitConditionPrivate::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (time=<value optimized out>, this=<value optimized out>) at thread/qwaitcondition_unix.cpp:159
#3  0x0000003743282e0c in QHostInfoAgent::run (this=0x2099970) at kernel/qhostinfo.cpp:260
#4  0x0000003c7985a0e1 in QThreadPrivate::start (arg=0x2099970) at thread/qthread_unix.cpp:189
#5  0x00007fec47ec887a in start_thread (arg=<value optimized out>) at pthread_create.c:297
#6  0x00007fec4748a79d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fec4a152820 (LWP 8377)):
#0  0x00007fec4744f531 in nanosleep () from /lib64/libc.so.6
#1  0x00007fec4744f380 in __sleep (seconds=<value optimized out>) at ../sysdeps/unix/sysv/linux/sleep.c:138
#2  0x00007fec489d44bc in KCrash::startDrKonqi (argv=<value optimized out>, argc=17) at /usr/src/debug/kdelibs-4.2.2/kdeui/util/kcrash.cpp:412
#3  0x00007fec489d4f0c in KCrash::defaultCrashHandler (sig=1377371856) at /usr/src/debug/kdelibs-4.2.2/kdeui/util/kcrash.cpp:337
#4  <signal handler called>
#5  QGraphicsItem::setVisible (this=0x10, visible=true) at graphicsview/qgraphicsitem.cpp:1620
#6  0x00007fec2ee7db6e in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#7  0x00007fec2ee7b5ae in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#8  0x00007fec2ee7d67c in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#9  0x00007fec2ee8056e in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#10 0x00007fec2ee78299 in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#11 0x00007fec2ee78793 in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#12 0x00007fec2ee6ae0d in KDialog::setButtons(QFlags<KDialog::ButtonCode>) () at /usr/src/debug/kdelibs-4.2.2/kdeui/dialogs/kdialog.cpp:193
#13 0x00007fec2ee70fbd in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#14 0x00007fec2ee6e6ae in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#15 0x00007fec2ee7375f in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#16 0x00007fec2ee73c28 in ?? () from /usr/lib64/kde4/plasma_applet_networkmanagement.so
#17 0x00007fec499d208e in Plasma::Corona::loadLayout (this=0x1b81ca0, configName=<value optimized out>) at /usr/src/debug/kdelibs-4.2.2/plasma/corona.cpp:313
#18 0x00007fec499d29d2 in Plasma::Corona::initializeLayout (this=0x1b81ca0, configName=@0x7fff52191990) at /usr/src/debug/kdelibs-4.2.2/plasma/corona.cpp:260
#19 0x00007fec49d48711 in PlasmaApp::corona (this=0x19d5990) at /usr/src/debug/kdebase-workspace-4.2.2/plasma/shells/desktop/plasmaapp.cpp:514
#20 0x00007fec49d4ac5e in PlasmaApp::setupDesktop (this=0x19d5990) at /usr/src/debug/kdebase-workspace-4.2.2/plasma/shells/desktop/plasmaapp.cpp:255
#21 0x00007fec49d4bd44 in PlasmaApp::qt_metacall (this=0x19d5990, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff52191b20)
    at /usr/src/debug/kdebase-workspace-4.2.2/x86_64-redhat-linux-gnu/plasma/shells/desktop/plasmaapp.moc:95
#22 0x0000003c79957fa2 in QMetaObject::activate (sender=0x1b40ef0, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x7fec47713e58) at kernel/qobject.cpp:3069
#23 0x0000003c7995d02f in QSingleShotTimer::timerEvent (this=0x1b40ef0) at kernel/qtimer.cpp:298
#24 0x0000003c79951d13 in QObject::event (this=0x1b40ef0, e=0x1) at kernel/qobject.cpp:1082
#25 0x0000003c7b18deac in QApplicationPrivate::notify_helper (this=0x19efc70, receiver=0x1b40ef0, e=0x7fff52192130) at kernel/qapplication.cpp:4084
#26 0x0000003c7b1954de in QApplication::notify (this=0x19d5990, receiver=0x1b40ef0, e=0x7fff52192130) at kernel/qapplication.cpp:4049
#27 0x00007fec48972146 in KApplication::notify (this=0x19d5990, receiver=0x1b40ef0, event=0x7fff52192130) at /usr/src/debug/kdelibs-4.2.2/kdeui/kernel/kapplication.cpp:307
#28 0x0000003c799425ac in QCoreApplication::notifyInternal (this=0x19d5990, receiver=0x1b40ef0, event=0x7fff52192130) at kernel/qcoreapplication.cpp:602
#29 0x0000003c7996de32 in QCoreApplication::sendEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:213
#30 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:572
#31 0x0000003c7996b92d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:164
#32 0x00007fec463dd18e in g_main_dispatch (context=<value optimized out>) at gmain.c:1814
#33 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2367
#34 0x00007fec463e08e8 in g_main_context_iterate (context=0x19f2520, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2448
#35 0x00007fec463e0a5c in IA__g_main_context_iteration (context=0x19f2520, may_block=1) at gmain.c:2511
#36 0x0000003c7996b876 in QEventDispatcherGlib::processEvents (this=0x19b6db0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:323
#37 0x0000003c7b221fee in QGuiEventDispatcherGlib::processEvents (this=0x10, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#38 0x0000003c79940e82 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#39 0x0000003c79941254 in QEventLoop::exec (this=0x7fff521923d0, flags=) at kernel/qeventloop.cpp:200
#40 0x0000003c79943349 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#41 0x00007fec49d3a3cf in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.2.2/plasma/shells/desktop/main.cpp:54
#42 0x00007fec473c977d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, 
    rtld_fini=<value optimized out>, stack_end=0x7fff521926d8) at libc-start.c:220
#43 0x0000000000400769 in _start ()
Current language:  auto; currently asm
Current language:  auto; currently minimal
Comment 1 Valter Mura 2009-04-26 10:25:50 UTC
Created attachment 33111 [details]
network management crash

my backtrace for the crash
Comment 2 Valter Mura 2009-04-26 10:28:41 UTC
I have the same problem, if I try to use the config windows the application crashes together with the plasma system, and the plasma restarts automatically.

*I do not have problems with my connection* (it works), I only have problems with the application.
Comment 3 Will Stephenson 2009-04-30 17:14:58 UTC
The debug symbols are missing for Network Management in the first backtrace and completely missing in the second backtrace.

Please provide as described here: 
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 4 marcela maslanova 2009-05-06 08:19:33 UTC
Created attachment 33389 [details]
full backtrace

Hope here are all information.
Comment 5 Will Stephenson 2009-07-23 01:06:50 UTC
Should be fixed imminently in 0.8
Comment 6 Will Stephenson 2009-07-31 19:41:32 UTC

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