Summary: | kde daemon crash after blueteathering fail | ||
---|---|---|---|
Product: | [Unmaintained] Network Management | Reporter: | shani <grawcho> |
Component: | KDED Module | Assignee: | Will Stephenson <wstephenson> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | kevin, lamarque |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 0.9.0_rc2 | |
Sentry Crash Report: |
Description
shani
2011-09-29 07:56:50 UTC
Which NetworkManager and ModemManager versions do you use? This crashlog is wierd because the crash happened during a DeviceAdd signal, which should not have been emitted since your device (your mobile broadband cellphone/modem) is already added. It seems like your device was reseted somehow. Can you reproduce this problem? Git commit 28435fd3d1dead8c6da11e337be15f2d22455d82 by Lamarque V. Souza. Committed on 26/10/2011 at 18:28. Pushed by lvsouza into branch 'nm09'. Use correct modem identifier when deciding to reset internal pointers for bluetooth devices. BUG: 283017 FIXED-IN: 0.9.0_rc2 M +1 -1 plasma_nm_version.h M +11 -7 solidcontrolfuture/solid/networkmanager-0.9/networkmodeminterface.cpp M +1 -0 solidcontrolfuture/solid/networkmanager-0.9/networkmodeminterface_p.h http://commits.kde.org/networkmanagement/28435fd3d1dead8c6da11e337be15f2d22455d82 *** Bug 294247 has been marked as a duplicate of this bug. *** |