Bug 242891

*** Bug 243162 has been marked as a duplicate of this bug. ***

*** Bug 243353 has been marked as a duplicate of this bug. ***

*** Bug 243824 has been marked as a duplicate of this bug. ***

*** Bug 246739 has been marked as a duplicate of this bug. ***

*** Bug 247419 has been marked as a duplicate of this bug. ***

Bug 243824 contains a description how to reproduce this crash easily. Perhaps you should keep the bug containing the most/best information and close the others as duplicates, instead of just picking one randomly and hide useful informations from the others.

Anyways, thanks for that gorgeous Networkmanagement Plasmoid!

[Comment from a bug triager]
Note: the backtrace seems related to the one in bug 210785. Most of the backtraces here are from KDE SC 4.4.4, but NM-KDE 0.9, and I don't know if that is the latest version, or if it includes the fix for bug 210785.

[Comment from a bug triager]
From bug 243353:
What I was doing when the application crashed:
i was connected via wifi (WPA2) when the connection failed and if i tried to
reconnect it would ask me the wifi password over and over again until it
crashed and the icon in the system try disappeared.
laptop: HP pavillion tx2130el

From bug 246739:
Netmanager crashes when trying to connect with Wireless Tether
Don't know much about Tether but I connected to Internet in < 30 seconds  
under WinXP
(Note from Dario: the report contains other information about the connection)

From bug 243824 (kded4 crash):
- What I was doing when the application crashed:
* Click on a wireless LAN in the networkmanagement plasmoid, so that it asks
for a password. Don't close the password dialog.
* unload the networkmanagement module and load it again
* now click OK on the password dialog

This isn't actually a common use-case. However, having troubles connecting to
Wireless LANs I sometimes reload the module manually. Perhaps the password
dialog should be closed upon unloading the kded module.
The crash can be reproduced every time.

From bug 260877:
-- Information about the crash:
Tried to connect to a non-broadcasting Cisco AP at work that uses WEP. The
NetworkManager crashed after I've altered the name of the access point that the
computer should connect to. it did ask me to enter the KDE Wallet password,
then crashed.

-- Full backtrace from bug 247419:
[KCrash Handler]
#6  0x2e65646b in ?? ()
#7  0xb5c5707b in WirelessSecuritySettingWidget::writeConfig (this=0x81dc468)
at
/usr/src/debug/networkmanagement/libs/ui/security/wirelesssecuritysettingwidget.cpp:290
#8  0xb5c6a346 in ConnectionSecretsJob::dialogAccepted (this=0x82524c8) at
/usr/src/debug/networkmanagement/libs/ui/connectionsecretsjob.cpp:185
#9  0xb5c3de2c in ConnectionSecretsJob::qt_metacall (this=0x82524c8,
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfa7445c)
    at
/usr/src/debug/networkmanagement/build/libs/ui/moc_connectionsecretsjob.cpp:78
#10 0xb6e1cefd in QMetaObject::metacall (object=0x82524c8,
cl=QMetaObject::InvokeMetaMethod, idx=27, argv=0xbfa7445c) at
kernel/qmetaobject.cpp:237
#11 0xb6e2bfe8 in QMetaObject::activate (sender=0x8325258, m=0x8070930,
local_signal_index=9, argv=0x0) at kernel/qobject.cpp:3295
#12 0xb72c0fa5 in KDialog::okClicked (this=0x8325258) at
/usr/src/debug/kdelibs-4.4.4/build/kdeui/kdialog.moc:258
#13 0xb744faa8 in KDialog::slotButtonClicked (this=0x8325258, button=4) at
/usr/src/debug/kdelibs-4.4.4/kdeui/dialogs/kdialog.cpp:862
#14 0xb74513b3 in KDialog::qt_metacall (this=0x8325258,
_c=QMetaObject::InvokeMetaMethod, _id=33, _a=0xbfa745e8) at
/usr/src/debug/kdelibs-4.4.4/build/kdeui/kdialog.moc:190
#15 0xb6e1cefd in QMetaObject::metacall (object=0x8325258,
cl=QMetaObject::InvokeMetaMethod, idx=69, argv=0xbfa745e8) at
kernel/qmetaobject.cpp:237
#16 0xb6e2bfe8 in QMetaObject::activate (sender=0x83bd1f0, m=0xb6f32104,
local_signal_index=0, argv=0xbfa745e8) at kernel/qobject.cpp:3295
#17 0xb6e2f595 in QSignalMapper::mapped (this=0x83bd1f0, _t1=4) at
.moc/release-shared/moc_qsignalmapper.cpp:101
#18 0xb6e2f809 in QSignalMapper::map (this=0x83bd1f0, sender=0x83be6a0) at
kernel/qsignalmapper.cpp:266
#19 0xb6e2f91e in QSignalMapper::map (this=0x83bd1f0) at
kernel/qsignalmapper.cpp:257
#20 0xb6e2fec0 in QSignalMapper::qt_metacall (this=0x83bd1f0,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfa74778) at
.moc/release-shared/moc_qsignalmapper.cpp:87
#21 0xb6e1cefd in QMetaObject::metacall (object=0x83bd1f0,
cl=QMetaObject::InvokeMetaMethod, idx=8, argv=0xbfa74778) at
kernel/qmetaobject.cpp:237
#22 0xb6e2bfe8 in QMetaObject::activate (sender=0x83be6a0, m=0x8070940,
local_signal_index=2, argv=0xbfa74778) at kernel/qobject.cpp:3295
#23 0xb6a7321d in QAbstractButton::clicked (this=0x83be6a0, _t1=false) at
.moc/release-shared/moc_qabstractbutton.cpp:206
#24 0xb6772c1d in QAbstractButtonPrivate::emitClicked (this=0x83be940) at
widgets/qabstractbutton.cpp:546
#25 0xb67742db in QAbstractButtonPrivate::click (this=0x83be940) at
widgets/qabstractbutton.cpp:539
#26 0xb6774596 in QAbstractButton::mouseReleaseEvent (this=0x83be6a0,
e=0xbfa74e84) at widgets/qabstractbutton.cpp:1121
#27 0xb63c4f00 in QWidget::event (this=0x83be6a0, event=0xbfa74e84) at
kernel/qwidget.cpp:8044
#28 0xb67737d0 in QAbstractButton::event (this=0x83be6a0, e=0xbfa74e84) at
widgets/qabstractbutton.cpp:1080
#29 0xb68132d8 in QPushButton::event (this=0x83be6a0, e=0xbfa74e84) at
widgets/qpushbutton.cpp:679
#30 0xb636bc64 in QApplicationPrivate::notify_helper (this=0x8095500,
receiver=0x83be6a0, e=0xbfa74e84) at kernel/qapplication.cpp:4302
#31 0xb6374750 in QApplication::notify (this=0xbfa74b9c, receiver=0x83be6a0,
e=0xbfa74e84) at kernel/qapplication.cpp:3867
#32 0xb72e09d1 in KApplication::notify (this=0xbfa756f0, receiver=0x83be6a0,
event=0xbfa74e84) at
/usr/src/debug/kdelibs-4.4.4/kdeui/kernel/kapplication.cpp:302
#33 0xb6e16e0e in QCoreApplication::notifyInternal (this=0xbfa756f0,
receiver=0x83be6a0, event=0xbfa74e84) at kernel/qcoreapplication.cpp:726
#34 0xb636cc4c in sendSpontaneousEvent (receiver=0x83be6a0, event=0xbfa74e84,
alienWidget=0x83be6a0, nativeWidget=0x8325258, buttonDown=0xb6cb6078,
lastMouseReceiver=..., spontaneous=true)
    at ../../src/corelib/kernel/qcoreapplication.h:218
#35 QApplicationPrivate::sendMouseEvent (receiver=0x83be6a0, event=0xbfa74e84,
alienWidget=0x83be6a0, nativeWidget=0x8325258, buttonDown=0xb6cb6078,
lastMouseReceiver=..., spontaneous=true)
    at kernel/qapplication.cpp:2965
#36 0xb63f458c in QETWidget::translateMouseEvent (this=0x8325258,
event=0xbfa7539c) at kernel/qapplication_x11.cpp:4380
#37 0xb63f373e in QApplication::x11ProcessEvent (this=0xbfa756f0,
event=0xbfa7539c) at kernel/qapplication_x11.cpp:3391
#38 0xb641c570 in x11EventSourceDispatch (s=0x80981f8, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#39 0xb5b0ab49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#40 0xb5b0b350 in ?? () from /usr/lib/libglib-2.0.so.0
#41 0xb5b0b60e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#42 0xb6e42d4b in QEventDispatcherGlib::processEvents (this=0x8078610,
flags=...) at kernel/qeventdispatcher_glib.cpp:412
#43 0xb641c19a in QGuiEventDispatcherGlib::processEvents (this=0x8078610,
flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#44 0xb6e1611d in QEventLoop::processEvents (this=0xbfa75654, flags=...) at
kernel/qeventloop.cpp:149
#45 0xb6e16319 in QEventLoop::exec (this=0xbfa75654, flags=...) at
kernel/qeventloop.cpp:201
#46 0xb6e1ac70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#47 0xb6369164 in QApplication::exec () at kernel/qapplication.cpp:3581
#48 0x08053e59 in _start ()

*** Bug 260877 has been marked as a duplicate of this bug. ***

Is this bug still happening in the latest Plasma NM snapshot? I cannot reproduce it and there have been several bug fixes in the last two months.

Lamarque,

Thanks for following up.  To be honest, I've switched over to the NM 
plasmoid and then, like you said, accepted a bunch of pending updates. 
Haven't had the problem reoccurring since that was done...

Thanks!

Alex


On 05/16/2011 07:47 PM, Lamarque V. Souza wrote:
> https://bugs.kde.org/show_bug.cgi?id=242891
>
>
> Lamarque V. Souza<lamarque@gmail.com>  changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |lamarque@gmail.com
>
>
>
>
> --- Comment #10 from Lamarque V. Souza<lamarque gmail com>   2011-05-17 01:47:43 ---
> Is this bug still happening in the latest Plasma NM snapshot? I cannot
> reproduce it and there have been several bug fixes in the last two months.
>

Ok, closing this bug as umaintained since monolithic knetworkmanager is unmaintained and the problem does not happen in the plasmoid version. Please use the plasmoid version.

*** Bug 285564 has been marked as a duplicate of this bug. ***

*** Bug 285659 has been marked as a duplicate of this bug. ***