Description of problem: regression after last NetworkManager update, not blocker , but sometimes crash with my old USB 3G dongle huawei e1550, but a long time that don't saw crashes with previous releases , with this one is pretty often Version-Release number of selected component: NetworkManager-0.9.8.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_active_connection_get_path executable: /usr/sbin/NetworkManager kernel: 3.8.4-202.fc18.x86_64 uid: 0 ureports_counter: 1 Truncated backtrace: Thread no. 1 (7 frames) #0 nm_active_connection_get_path at nm-active-connection.c:142 #1 get_property at nm-manager.c:4457 #2 object_get_property at gobject.c:1294 #3 g_object_get_property at gobject.c:2228 #4 get_all_object_properties at dbus-gobject.c:1322 #5 object_registration_message at dbus-gobject.c:2204 #6 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862
Created attachment 730109 [details] File: backtrace
Created attachment 730110 [details] File: cgroup
Created attachment 730111 [details] File: core_backtrace
Created attachment 730112 [details] File: dso_list
Created attachment 730113 [details] File: environ
Created attachment 730114 [details] File: limits
Created attachment 730115 [details] File: maps
Created attachment 730116 [details] File: open_fds
Created attachment 730117 [details] File: proc_pid_status
Created attachment 730118 [details] File: var_log_messages
Created attachment 730119 [details] kernel ooops Like I wrote, I test it carefully on previous version and doesn't happens. Now I also, sometimes, got an kernel oops. I do this as workaround, when it is need it systemctl stop NetworkManager.service; killall modem-manager ; systemctl start NetworkManager.service
one little crash after remove usb pen and suspend and resume laptop. Hope that help to improve NM , is not a big problem backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_active_connection_get_path executable: /usr/sbin/NetworkManager kernel: 3.8.7-201.fc18.x86_64 package: NetworkManager-0.9.8.1-1.git20130327.fc18 reason: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV) uid: 0 ureports_counter: 1
unplug usb stick backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_active_connection_get_path executable: /usr/sbin/NetworkManager kernel: 3.8.9-200.fc18.x86_64 package: NetworkManager-0.9.8.1-1.git20130327.fc18 reason: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV) uid: 0 ureports_counter: 1
Thanks for reporting the issue. Do you still experience it? The reproducer is unplugging the USB modem, right?
*** Bug 985620 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
with "new" driver cdc-wdm0, for 3G dongle huawei e1550, this bug no long exist.