Bug 269396 - knetworkmanager crashes when using umts device (usb)
Summary: knetworkmanager crashes when using umts device (usb)
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 271412 271604 271938 274217 274219 275891 276062 280298 281266 282031 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-03-25 16:11 UTC by betatesta
Modified: 2012-03-03 21:52 UTC (History)
12 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (4.32 KB, text/plain)
2011-07-27 17:33 UTC, Burtea Radu-Alin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description betatesta 2011-03-25 16:11:40 UTC
Application: kded4 ($Id: kded.cpp 1204125 2010-12-06 11:17:10Z dfaure $)
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.1-1.2-default i686
Distribution: "openSUSE 11.4 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:

try to connect umts account
first it crashed when trying to setup a acount. problem solved by installing mobil account database.

-- Backtrace:
Application: KDE-Dienst (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb57f4710 (LWP 1575))]

Thread 3 (Thread 0xad237b70 (LWP 1638)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb5fe803e in poll () from /lib/libc.so.6
#2  0xb5a6e0bb in g_poll () from /lib/libglib-2.0.so.0
#3  0xb5a5dc46 in ?? () from /lib/libglib-2.0.so.0
#4  0xb5a5e3ef in g_main_loop_run () from /lib/libglib-2.0.so.0
#5  0xad32b001 in ?? () from /lib/libgio-2.0.so.0
#6  0xb5a86f44 in ?? () from /lib/libglib-2.0.so.0
#7  0xb6c35b05 in start_thread () from /lib/libpthread.so.0
#8  0xb5ff2d5e in clone () from /lib/libc.so.6

Thread 2 (Thread 0xaca29b70 (LWP 1647)):
#0  0xb6c39474 in __pthread_mutex_unlock_usercnt () from /lib/libpthread.so.0
#1  0xb5a5ca63 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#2  0xb5a5d8e2 in ?? () from /lib/libglib-2.0.so.0
#3  0xb5a5dfce in g_main_context_iteration () from /lib/libglib-2.0.so.0
#4  0xb6ddc7b7 in QEventDispatcherGlib::processEvents (this=0x817bec0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0xb6dad2bd in QEventLoop::processEvents (this=0xaca292b0, flags=...) at kernel/qeventloop.cpp:149
#6  0xb6dad4e9 in QEventLoop::exec (this=0xaca292b0, flags=...) at kernel/qeventloop.cpp:201
#7  0xb6cae7b9 in QThread::exec (this=0x81b2948) at thread/qthread.cpp:490
#8  0xb6d8d23d in QInotifyFileSystemWatcherEngine::run (this=0x81b2948) at io/qfilesystemwatcher_inotify.cpp:248
#9  0xb6cb13aa in QThreadPrivate::start (arg=0x81b2948) at thread/qthread_unix.cpp:285
#10 0xb6c35b05 in start_thread () from /lib/libpthread.so.0
#11 0xb5ff2d5e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb57f4710 (LWP 1575)):
[KCrash Handler]
#7  QMutex::lock (this=0x86c57520) at thread/qmutex.cpp:151
#8  0xb6db1306 in QCoreApplication::postEvent (receiver=0x819f224, event=0x819f1f0, priority=0) at kernel/qcoreapplication.cpp:1141
#9  0xb6db163b in QCoreApplication::postEvent (receiver=0x819f224, event=0x819f1f0) at kernel/qcoreapplication.cpp:1094
#10 0xb5c04376 in postEventToThread (this=0x816c5d8, hook=..., msg=...) at qdbusintegrator.cpp:2357
#11 QDBusConnectionPrivate::activateSignal (this=0x816c5d8, hook=..., msg=...) at qdbusintegrator.cpp:743
#12 0xb5c0567b in QDBusConnectionPrivate::handleSignal (this=0x816c5d8, key=..., msg=...) at qdbusintegrator.cpp:1542
#13 0xb5c058ef in QDBusConnectionPrivate::handleSignal (this=0x816c5d8, msg=...) at qdbusintegrator.cpp:1561
#14 0xb5c0879d in QDBusConnectionPrivate::handleMessage (this=0x816c5d8, amsg=...) at qdbusintegrator.cpp:546
#15 0xb5c0c01b in qDBusSignalFilter (connection=0x8170b50, message=0x86c57520, data=0x816c5d8) at qdbusintegrator.cpp:530
#16 0xb586c84b in dbus_connection_dispatch (connection=0x8170b50) at dbus-connection.c:4647
#17 0xb5bff4fb in q_dbus_connection_dispatch (this=0x816c5d8) at qdbus_symbols_p.h:115
#18 QDBusConnectionPrivate::doDispatch (this=0x816c5d8) at qdbusintegrator.cpp:1094
#19 0xb5c01d4d in QDBusConnectionPrivate::socketRead (this=0x816c5d8, fd=11) at qdbusintegrator.cpp:1114
#20 0xb5c48125 in QDBusConnectionPrivate::qt_metacall (this=0x816c5d8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfb10708) at .moc/release-shared/moc_qdbusconnection_p.cpp:99
#21 0xb6db48cd in QMetaObject::metacall (object=0x816c5d8, cl=QMetaObject::InvokeMetaMethod, idx=8, argv=0xbfb10708) at kernel/qmetaobject.cpp:237
#22 0xb6dc4a2c in QMetaObject::activate (sender=0x816f808, m=0xb6ee8550, local_signal_index=0, argv=0xbfb10708) at kernel/qobject.cpp:3272
#23 0xb6e13e55 in QSocketNotifier::activated (this=0x816f808, _t1=11) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#24 0xb6dcabbf in QSocketNotifier::event (this=0x816f808, e=0xbfb10b64) at kernel/qsocketnotifier.cpp:317
#25 0xb62ba414 in QApplicationPrivate::notify_helper (this=0x80bf4a0, receiver=0x816f808, e=0xbfb10b64) at kernel/qapplication.cpp:4445
#26 0xb62c30c7 in QApplication::notify (this=0xbfb10e60, receiver=0x816f808, e=0xbfb10b64) at kernel/qapplication.cpp:3845
#27 0xb74081f1 in KApplication::notify (this=0xbfb10e60, receiver=0x816f808, event=0xbfb10b64) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311
#28 0xb6dadfde in QCoreApplication::notifyInternal (this=0xbfb10e60, receiver=0x816f808, event=0xbfb10b64) at kernel/qcoreapplication.cpp:732
#29 0xb6ddc108 in sendEvent (source=0x80c1e10) at kernel/qcoreapplication.h:215
#30 socketNotifierSourceDispatch (source=0x80c1e10) at kernel/qeventdispatcher_glib.cpp:110
#31 0xb5a5d509 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0xb5a5dd10 in ?? () from /lib/libglib-2.0.so.0
#33 0xb5a5dfce in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0xb6ddc76b in QEventDispatcherGlib::processEvents (this=0x80a91b0, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#35 0xb637055a in QGuiEventDispatcherGlib::processEvents (this=0x80a91b0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0xb6dad2bd in QEventLoop::processEvents (this=0xbfb10dc4, flags=...) at kernel/qeventloop.cpp:149
#37 0xb6dad4e9 in QEventLoop::exec (this=0xbfb10dc4, flags=...) at kernel/qeventloop.cpp:201
#38 0xb6db1f90 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#39 0xb62b8104 in QApplication::exec () at kernel/qapplication.cpp:3719
#40 0xb541343d in kdemain (argc=1, argv=0x80a20b0) at /usr/src/debug/kdelibs-4.6.0/kded/kded.cpp:925
#41 0x0804e531 in launch (argc=1, _name=0x8052768 "kded4", args=<value optimized out>, cwd=0x0, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x80525e3 "0") at /usr/src/debug/kdelibs-4.6.0/kinit/kinit.cpp:730
#42 0x08050f44 in main (argc=-2033879816, argv=0xac1d440c, envp=0xac1d43f4) at /usr/src/debug/kdelibs-4.6.0/kinit/kinit.cpp:1845

Reported using DrKonqi
Comment 1 Lamarque V. Souza 2011-04-22 06:20:45 UTC
*** Bug 271412 has been marked as a duplicate of this bug. ***
Comment 2 Lamarque V. Souza 2011-04-24 16:01:47 UTC
*** Bug 271604 has been marked as a duplicate of this bug. ***
Comment 3 Tuukka Kivilahti, TKffTK 2011-05-07 11:12:03 UTC
Found probably same bug. Kde-version: 4.6.2, Distro: Kubuntu 11.04.

kded4 -process takes 100% of CPU time. Half of kde stops working (probably stuff related to that process).

-- Information about the crash:
- How to repeat (works every time for me):
1. Disable / disconnect every network-connection (wlan etc).
2. Connect huawei e1820 usb 3g modem and create connection with network-manager
3. Disconnect 3g connection with network-manager, or remove usb modem.

Bug does not appear if connected same time to wlan.


-- Log-information, end of: /var/log/syslog. usb-modem was removed just before first line

May  6 17:51:24 indi acpid: client 1054[0:0] has disconnected
May  6 17:51:24 indi acpid: client connected from 1054[0:0]
May  6 17:51:24 indi acpid: 1 client rule loaded
May  6 17:51:24 indi kernel: [  211.335656] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
May  6 17:51:28 indi ntpdate[2686]: adjust time server 91.189.94.4 offset -0.046265 sec
May  6 17:51:28 indi pppd[2619]: Modem hangup
May  6 17:51:28 indi pppd[2619]: Connect time 0.2 minutes.
May  6 17:51:28 indi pppd[2619]: Sent 586 bytes, received 874 bytes.
May  6 17:51:28 indi modem-manager[1025]: <info>  (ttyUSB0) closing serial port...
May  6 17:51:28 indi modem-manager[1025]: <info>  (ttyUSB0) serial port closed
May  6 17:51:28 indi modem-manager[1025]: <info>  (ttyUSB2) closing serial port...
May  6 17:51:28 indi modem-manager[1025]: <info>  (ttyUSB2) serial port closed
May  6 17:51:28 indi kernel: [  215.763250] usb 2-1.2: USB disconnect, address 4
May  6 17:51:28 indi kernel: [  215.763416] option: option_instat_callback: error -108
May  6 17:51:28 indi kernel: [  215.763592] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
May  6 17:51:28 indi kernel: [  215.763611] option 2-1.2:1.0: device disconnected
May  6 17:51:28 indi kernel: [  215.763961] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
May  6 17:51:28 indi kernel: [  215.763992] option 2-1.2:1.3: device disconnected
May  6 17:51:28 indi kernel: [  215.764201] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
May  6 17:51:28 indi kernel: [  215.764222] option 2-1.2:1.4: device disconnected
May  6 17:51:28 indi modem-manager[1025]: <info>  (tty/ttyUSB1): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2
May  6 17:51:28 indi modem-manager[1025]: <info>  (tty/ttyUSB2): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2
May  6 17:51:28 indi modem-manager[1025]: <info>  (tty/ttyUSB0): released by modem /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2
May  6 17:51:28 indi modem-manager[1025]: <info>  Modem /org/freedesktop/ModemManager/Modems/0: state changed (connected -> disabled)
May  6 17:51:28 indi NetworkManager[1018]: <info> (ttyUSB0): now unmanaged
May  6 17:51:28 indi NetworkManager[1018]: <info> (ttyUSB0): device state change: 8 -> 1 (reason 36)
May  6 17:51:28 indi NetworkManager[1018]: <info> (ttyUSB0): deactivating device (reason: 36).
May  6 17:51:28 indi pppd[2619]: Connection terminated.
May  6 17:51:28 indi avahi-daemon[1073]: Withdrawing workstation service for ppp0.
May  6 17:51:28 indi NetworkManager[1018]: <info> (ttyUSB0): cleaning up...
May  6 17:51:28 indi NetworkManager[1018]: <info> (ttyUSB0): taking down device.
May  6 17:51:28 indi NetworkManager[1018]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
May  6 17:51:28 indi NetworkManager[1018]:    SCPlugin-Ifupdown: devices removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
May  6 17:51:28 indi nm-dispatcher.action: Error in get_property: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist#012
May  6 17:51:29 indi pppd[2619]: Exit.
May  6 17:52:02 indi acpid: client 1054[0:0] has disconnected
Comment 4 ray-ven 2011-05-14 09:37:05 UTC
Installing mobile account database doesn't solve the Problem.
kded takes 100% CPU every time the 3g device is unplugged or disconnects.
This affects a lot of services, like kwallet because only
killall -9 kded4 && kded4 brings kded4 back.

This is killing my nerves!!!
Comment 5 Lamarque V. Souza 2011-05-26 23:13:56 UTC
*** Bug 274217 has been marked as a duplicate of this bug. ***
Comment 6 Lamarque V. Souza 2011-05-26 23:14:04 UTC
*** Bug 274219 has been marked as a duplicate of this bug. ***
Comment 7 Lamarque V. Souza 2011-05-27 07:26:22 UTC
The 100% CPU in kded is problably this bug http://bugs.kde.org/268038 . This is one is different. Can you try upgrading Plasma NM using these packages?

http://lists.opensuse.org/opensuse-kde/2011-05/msg00035.html
Comment 8 Lamarque V. Souza 2011-06-19 18:52:39 UTC
*** Bug 276062 has been marked as a duplicate of this bug. ***
Comment 9 Beat Wolf 2011-06-20 15:36:07 UTC
*** Bug 275891 has been marked as a duplicate of this bug. ***
Comment 10 Lamarque V. Souza 2011-06-23 22:12:27 UTC
*** Bug 271938 has been marked as a duplicate of this bug. ***
Comment 11 Burtea Radu-Alin 2011-07-27 17:33:40 UTC
Created attachment 62248 [details]
New crash information added by DrKonqi

kded4 ($Id$) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2

- What I was doing when the application crashed:
I was tryng to set up my internet connection using my USB flash,and i was tweaking my network conection when everything crushed

-- Backtrace (Reduced):
#6  QCoreApplication::postEvent (receiver=0x152ac10, event=0x1537640, priority=0) at kernel/qcoreapplication.cpp:1132
#7  0x00007f94a4dee361 in QDBusConnectionPrivate::handleSignal (this=0x13e0c50, key=..., msg=...) at qdbusintegrator.cpp:1573
#8  0x00007f94a4dee5b8 in QDBusConnectionPrivate::handleSignal (this=0x13e0c50, msg=...) at qdbusintegrator.cpp:1592
#9  0x00007f94a4deff95 in QDBusConnectionPrivate::handleMessage (this=0x13e0c50, amsg=...) at qdbusintegrator.cpp:560
#10 0x00007f94a4df4387 in qDBusSignalFilter (connection=<value optimized out>, message=<value optimized out>, data=0x13e0c50) at qdbusintegrator.cpp:541
Comment 12 Lamarque V. Souza 2011-08-23 01:38:51 UTC
*** Bug 280298 has been marked as a duplicate of this bug. ***
Comment 13 Lamarque V. Souza 2011-09-03 13:36:50 UTC
*** Bug 281266 has been marked as a duplicate of this bug. ***
Comment 14 Christoph Feck 2011-09-14 21:41:22 UTC
*** Bug 282031 has been marked as a duplicate of this bug. ***
Comment 15 Lamarque V. Souza 2012-01-25 19:39:20 UTC
Is this still happening?