Description of problem: I tried enabling Mobile Broadband from the mate desktop nm-applet and it segfaulted and thus disappeared. I had to manually restart nm-applet. Version-Release number of selected component: network-manager-applet-0.9.9.0-9.git20140123.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: nm-applet crash_function: gtk_status_icon_is_embedded executable: /usr/bin/nm-applet kernel: 3.13.7-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_status_icon_is_embedded at /lib64/libgtk-3.so.0 #1 applet_do_notify at applet.c:887 #2 applet_do_notify_with_pref at applet.c:956 #3 ffi_call_unix64 at ../src/x86/unix64.S:76 #4 ffi_call at ../src/x86/ffi64.c:522 #5 g_cclosure_marshal_generic at gclosure.c:1454 #8 g_signal_emitv at gsignal.c:3063 #9 mm_gdbus_modem_proxy_g_signal at mm-gdbus-modem.c:4353 #10 ffi_call_unix64 at ../src/x86/unix64.S:76 #11 ffi_call at ../src/x86/ffi64.c:522
Created attachment 881986 [details] File: backtrace
Created attachment 881987 [details] File: cgroup
Created attachment 881988 [details] File: core_backtrace
Created attachment 881989 [details] File: dso_list
Created attachment 881990 [details] File: environ
Created attachment 881991 [details] File: exploitable
Created attachment 881992 [details] File: limits
Created attachment 881993 [details] File: maps
Created attachment 881994 [details] File: open_fds
Created attachment 881995 [details] File: proc_pid_status
Created attachment 881996 [details] File: var_log_messages
To be more specific about when this crash happens.. nm seems to often go to a "weird" state where the mobile broadband doesn't work anymore, so then i have to stop (restart) the NetworkManager and ModemManager services with systemctl. The segfault happens when I first stop NetworkManager service, and then when I stop the ModemManager service I get the segfault.
To reproduce the nm-applet segfault/crash: systemctl stop NetworkManager.service sleep 2 systemctl stop ModemManager.service .. and at this poing nm-applet segfaults.
I can see something that might cause this, but I can't reproduce the exact issue. Could you try running the applet under valgrind for me and see what output valgrind gives? Bonus points if you install network-manager-applet-debuginfo and NetworkManager-glib debuginfo, though you don't need to drag in all the dependencies. eg, you can just hit up http://download.fedoraproject.org/ and find them, if you don't want to install the whole dependency chain using debuginfo-install. It may not be reproducible with valgrind, since valgrind slows everything down, but it might help find the issue. I've also built an nm-applet with the fix at http://koji.fedoraproject.org/koji/taskinfo?taskID=6708612 . You could also download and install those packages, and see if they fix the issue for you. If they don't, valgrind would be greatly appreciated. Thanks!
One more detail about reproducing the crash.. "Enable Mobile Broadband" needs to be enabled in the nm-applet right-click menu, then the stop/start services sequence crashes the applet for me. If Mobile Broadband is disabled in the nm-applet right-click menu, then I'm able to restart the services without nm-applet crash. I'll see about playing with the debuginfo/valgring in the coming days.. Thanks!
Created attachment 883490 [details] backtrace of a crash in applet-device-broadband.c:add_menu_item() While trying to reproduce the crash, I managed to crash nm-applet in a different place. in applet-device-broadband.c:add_menu_item() info = g_object_get_data (G_OBJECT (device), "devinfo"); returned NULL
I'm still seeing nm-applet crashes with network-manager-applet-0.9.9.0-10.git20140123.fc20.x86_64 (latest in F20 updates). I'll try the valgrind stuff soon. Let me know if there's anything else I should try.
btw I can't find NetworkManager-glib-debuginfo .. No package NetworkManager-glib-debuginfo available.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.