Bug 251542 - KNetworkManager crashes plasma when selecting network [[invalid QDBusAbstractInterface], RemoteActivatable::activate, ActivatableItem::emitClicked]
Summary: KNetworkManager crashes plasma when selecting network [[invalid QDBusAbstract...
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: Network Management
Classification: Unmaintained
Component: Plasma Widget (other bugs)
Version First Reported In: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 253580 255177 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-09-17 10:13 UTC by Bruno
Modified: 2011-05-21 04:11 UTC (History)
7 users (show)

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


Attachments
New crash information added by DrKonqi (2.23 KB, text/plain)
2010-09-25 22:11 UTC, corpsman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno 2010-09-17 10:13:24 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.4 (KDE 4.4.4) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.4-0.1-default x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
KNetworkManager, on opensuse 11.3 - kde 4.4.4r2, crashes in the following circumstance:

- eth has network cable connected but there isn't dchp to automatically connect.
- knetworkmanager applet will say no network is connected, as expected.
- when selecting a network from the list to connect to, plasma crashes and network doesnt become connected.
- after plasma is restored network can be selected and from now on it will connect correctly.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0x00007ffb62a61e17 in RemoteActivatable::activate (this=0x20436b0) at /usr/src/debug/networkmanagement/libs/client/remoteactivatable.cpp:73
#6  0x00007ffb62c8d882 in ActivatableItem::emitClicked (this=0x204bb00) at /usr/src/debug/networkmanagement/applet/activatableitem.cpp:49
#7  0x00007ffb62c84a6c in ActivatableItem::qt_metacall (this=0x204bb00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4ac90510)
    at /usr/src/debug/networkmanagement/build/applet/moc_activatableitem.cpp:83
#8  0x00007ffb80ad1a1f in QMetaObject::activate (sender=0x204bb00, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3295
#9  0x00007ffb79225f50 in Plasma::IconWidget::qt_metacall (this=0x204bb00, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fff4ac90730) at /usr/src/debug/kdelibs-4.4.4/build/plasma/iconwidget.moc:115
#10 0x00007ffb62c84a10 in ActivatableItem::qt_metacall (this=0x204bb00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4ac90730)
    at /usr/src/debug/networkmanagement/build/applet/moc_activatableitem.cpp:76
#11 0x00007ffb80ad1a1f in QMetaObject::activate (sender=0x204c270, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3295
#12 0x00007ffb79224728 in Plasma::IconWidget::mouseReleaseEvent (this=0x204c270, event=<value optimized out>) at /usr/src/debug/kdelibs-4.4.4/plasma/widgets/iconwidget.cpp:1259
#13 0x00007ffb802422ba in QGraphicsItem::sceneEvent (this=0x204c280, event=0x7fff4ac91090) at graphicsview/qgraphicsitem.cpp:6545
#14 0x00007ffb802642d0 in QGraphicsScenePrivate::sendMouseEvent (this=0x760af0, mouseEvent=0x7fff4ac91090) at graphicsview/qgraphicsscene.cpp:1264
#15 0x00007ffb80264c95 in QGraphicsScene::mouseReleaseEvent (this=<value optimized out>, mouseEvent=0x7fff4ac91090) at graphicsview/qgraphicsscene.cpp:4072
#16 0x00007ffb802769ff in QGraphicsScene::event (this=0x6f3780, event=0x7fff4ac91090) at graphicsview/qgraphicsscene.cpp:3407
#17 0x00007ffb7fc924d4 in QApplicationPrivate::notify_helper (this=0x671dc0, receiver=0x6f3780, e=0x7fff4ac91090) at kernel/qapplication.cpp:4302
#18 0x00007ffb7fc9aaca in QApplication::notify (this=<value optimized out>, receiver=0x6f3780, e=0x7fff4ac91090) at kernel/qapplication.cpp:4185
#19 0x00007ffb80f49c06 in KApplication::notify (this=0x665a90, receiver=0x6f3780, event=0x7fff4ac91090) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#20 0x00007ffb80abde4c in QCoreApplication::notifyInternal (this=0x665a90, receiver=0x6f3780, event=0x7fff4ac91090) at kernel/qcoreapplication.cpp:726
#21 0x00007ffb8028d47b in QGraphicsView::mouseReleaseEvent (this=0xa466f0, event=0x7fff4ac91b10) at graphicsview/qgraphicsview.cpp:3259
#22 0x00007ffb7fce2dbc in QWidget::event (this=0xa466f0, event=0x7fff4ac91b10) at kernel/qwidget.cpp:8044
#23 0x00007ffb800757d6 in QFrame::event (this=0xa466f0, e=0x7fff4ac91b10) at widgets/qframe.cpp:557
#24 0x00007ffb802903bb in QGraphicsView::viewportEvent (this=0xa466f0, event=0x7fff4ac91b10) at graphicsview/qgraphicsview.cpp:2787
#25 0x00007ffb80abdfd7 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0x1280c50, event=0x7fff4ac91b10) at kernel/qcoreapplication.cpp:841
#26 0x00007ffb7fc924a1 in QApplicationPrivate::notify_helper (this=0x671dc0, receiver=0x1280c50, e=0x7fff4ac91b10) at kernel/qapplication.cpp:4298
#27 0x00007ffb7fc9b34a in QApplication::notify (this=<value optimized out>, receiver=0x1280c50, e=0x7fff4ac91b10) at kernel/qapplication.cpp:3867
#28 0x00007ffb80f49c06 in KApplication::notify (this=0x665a90, receiver=0x1280c50, event=0x7fff4ac91b10) at /usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#29 0x00007ffb80abde4c in QCoreApplication::notifyInternal (this=0x665a90, receiver=0x1280c50, event=0x7fff4ac91b10) at kernel/qcoreapplication.cpp:726
#30 0x00007ffb7fc941e5 in sendEvent (receiver=0x1280c50, event=0x7fff4ac91b10, alienWidget=0x1280c50, nativeWidget=0xa1e430, buttonDown=0x7ffb8073eb28, lastMouseReceiver=..., spontaneous=true)
    at ../../src/corelib/kernel/qcoreapplication.h:215
#31 QApplicationPrivate::sendMouseEvent (receiver=0x1280c50, event=0x7fff4ac91b10, alienWidget=0x1280c50, nativeWidget=0xa1e430, buttonDown=0x7ffb8073eb28, lastMouseReceiver=..., spontaneous=true)
    at kernel/qapplication.cpp:2967
#32 0x00007ffb7fd0e6c8 in QETWidget::translateMouseEvent (this=0xa1e430, event=<value optimized out>) at kernel/qapplication_x11.cpp:4380
#33 0x00007ffb7fd0ce19 in QApplication::x11ProcessEvent (this=0x665a90, event=0x7fff4ac92470) at kernel/qapplication_x11.cpp:3513
#34 0x00007ffb7fd33492 in x11EventSourceDispatch (s=0x6754f0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#35 0x00007ffb7bd36a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#36 0x00007ffb7bd37270 in ?? () from /usr/lib64/libglib-2.0.so.0
#37 0x00007ffb7bd37510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#38 0x00007ffb80ae667f in QEventDispatcherGlib::processEvents (this=0x666480, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#39 0x00007ffb7fd3314e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#40 0x00007ffb80abd292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#41 0x00007ffb80abd495 in QEventLoop::exec (this=0x7fff4ac92790, flags=...) at kernel/qeventloop.cpp:201
#42 0x00007ffb80ac188b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#43 0x00007ffb73ee327d in kdemain (argc=1, argv=0x661240) at /usr/src/debug/kdebase-workspace-4.4.4/plasma/desktop/shell/main.cpp:112
#44 0x0000000000407659 in _start ()

Reported using DrKonqi
Comment 1 corpsman 2010-09-25 22:11:50 UTC
Created attachment 51989 [details]
New crash information added by DrKonqi

Same error like described.

The network cable is connected, but without DHCP. By choosing the manual connection KNetworkmanager crashes ( most times).

If i wait, it switches by itself to the manual connection and work fine.

Switching the connection at later time is no problem.

The Bug comes only short after a restart / first boot.
Comment 2 Dario Andres 2010-11-18 16:42:01 UTC
[Comment from a bug triager]
From bug 255177:
- What I was doing when the application crashed: restarting the network interface Plasma crashed

- Another backtrace:
Thread 1 (Thread 0x7f09a70087a0 (LWP 2123)):
[KCrash Handler]
#6  d_func (this=0x9090909090909090, method=..., args=...) at
qdbusabstractinterface.h:156
#7  QDBusAbstractInterface::asyncCallWithArgumentList (this=0x9090909090909090,
method=..., args=...) at qdbusabstractinterface.cpp:469
#8  0x00007f0983000949 in activate (this=<value optimized out>) at
./activatableinterface.h:56
#9  RemoteActivatable::activate (this=<value optimized out>) at
../../../libs/client/remoteactivatable.cpp:74
#10 0x00007f09832568e2 in ActivatableItem::emitClicked (this=0x17de0b0) at
../../applet/activatableitem.cpp:81
#11 0x00007f0983242b24 in ActivatableItem::qt_metacall (this=0x17de0b0,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff235dc350)
at moc_activatableitem.cpp:95
#12 0x00007f0983242b88 in InterfaceConnectionItem::qt_metacall
(this=0x7fff235dc1e0, _c=2425393296, _id=593347056, _a=0x7fff235dc200) at
moc_interfaceconnectionitem.cpp:67
#13 0x00007f09a3fb0b27 in QMetaObject::activate (sender=0x17de0b0, m=<value
optimized out>, local_signal_index=<value optimized out>, argv=0x7fff235dc200)
at kernel/qobject.cpp:3280
#14 0x00007f09a6512e38 in Plasma::IconWidget::qt_metacall (this=0x17de0b0,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff235dc540)
at ./iconwidget.moc:122
#15 0x00007f0983242a30 in ActivatableItem::qt_metacall (this=0x7fff235dc1e0,
_c=2425393296, _id=593347056, _a=0x7fff235dc200) at moc_activatableitem.cpp:87
#16 0x00007f0983242b88 in InterfaceConnectionItem::qt_metacall
(this=0x7fff235dc1e0, _c=2425393296, _id=593347056, _a=0x7fff235dc200) at
moc_interfaceconnectionitem.cpp:67

- Other information from bug 253580:
just used this plasmoid 24 hours; noted day of installation & first use that
seems it used existing kd4 default opensuse 11.3 installs networkmanager's usb
cellphone tether connection configs..BUT seemed to offer duplicates upon first
run.
each time i clicked on either of the two cellphone icons they would both appear
to activate including showing the 'heart - connected now' status.
so this am upon beginning i chose to connect same as few times day of install,
and this crash report appeared.
please note i am connected without the plasmoid disappearing; the only change
seems to be that the described duplicate mobile broadband acct icon in the
right pane of plasmoid is gone! BUT the plasmoid  STILL CONNECTED me here now
and is working.
implication is the duplicate connection accounts somehow conflicted with each
other?
perhaps post next reboot of laptop that duplication of connection
configurations will appear again?
-
virtually same as initial bug filed. awoke this am to find same described
duplicate icons representing my Samsung Vibrant's Android OS 2.1 (Eclair)'s usb
tether access to phone seen as 'mobile broadband' by my system:
Linux 2.6.34.7-0.3-desktop running KDE Development Platform 4.4.4 (KDE 4.4.4)
"release 3", CPU: AMD Turion Dual-Core RM-70 at 2000 MHz (4000 bogomips), HD:
156/241GB, RAM: 2038/2763MB, 174 proc's, 7.9h up
running openSuSE 11.3 x86_64. Upon clicking on the uppermost duplicate, same as
yesterday, i got this crash notice and one of the icons disappears yet
plasmoid-networkmanagement remains and i can still connect with single
remaining icon.
Comment 3 Dario Andres 2010-11-18 16:42:14 UTC
*** Bug 255177 has been marked as a duplicate of this bug. ***
Comment 4 Dario Andres 2010-11-18 16:42:16 UTC
*** Bug 253580 has been marked as a duplicate of this bug. ***
Comment 5 Lamarque V. Souza 2011-04-09 00:57:52 UTC
Can you test with a more recent KDE SC and Plasma NM (called plasmoid-networkmanagement in OpenSuse)?