abrt 1.0.0 detected a crash. How to reproduce ----- 1. Just clicked on the Network Manager icon at the top to see what wireless networks were available. 2. Connected to my wireless network. 3. Clicked on Network Manage icon again to see if I see it listed since it was hidden before. 4. List did not expand and I clicked on the icon for volume by accident 5. Red light starts flashing and I click on it. Comment: Let's see. I am an extreme beginner with Fedora (well Linux period). Just installed it yesterday! What I did, was what I listed above. Attached file: backtrace cmdline: nm-applet --sm-disable component: NetworkManager executable: /usr/bin/nm-applet kernel: 2.6.31.9-174.fc12.i686 package: NetworkManager-gnome-1:0.7.996-7.git20091113.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 381377 [details] File: backtrace
NetworkManager icon is not at the top any more. However, I am still connected to the WLAN.
I think this issue will soon be corrected by a software update. You can retrieve the icon by opening a terminal (Applications -> System Tools -> Terminal) and typing: nm-applet & and then closing the terminal. *** This bug has been marked as a duplicate of bug 546901 ***
Ah ok, thank you very much for the tip. Network manager just crashed on me again and I just performed the action and received the following before I could close the terminal: [user@localhost ~]$ nm-applet & [1] 2203 [user@localhost ~]$ ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed [user@localhost ~]$ ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2203): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed The icon did come back up. Was I to run this in root? Again, thank you for the help.
A few minutes after closing the terminal the icon closed again. This time I tried the command under root and received the feedback below. As soon as I clicked on the network manager icon it just disappeared. No longer usable. [root@localhost User]# libnotify-Message: Unable to get session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nm-applet:2252): libnotify-CRITICAL **: notify_get_server_caps: assertion `proxy != NULL' failed ** (nm-applet:2252): WARNING **: <WARN> bus_init(): Could not get the session bus. Make sure the message bus daemon is running! Message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.) ** (nm-applet:2252): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2252): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (nm-applet:2252): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (nm-applet:2252): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (nm-applet:2252): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2252): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2252): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2252): WARNING **: <WARN> bus_init(): Could not get the session bus. Make sure the message bus daemon is running! Message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ** (nm-applet:2252): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed ** (nm-applet:2252): CRITICAL **: nm_utils_ssid_to_utf8: assertion `ssid != NULL' failed