Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 277271 Details for
Bug 356041
Can't connect to AP with WPA-PSK
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Output from nm-applet when run from terminal as root
nm-appletoutput.txt (text/plain), 3.96 KB, created by
Chris Hackmeyer
on 2007-12-04 19:29:00 UTC
(
hide
)
Description:
Output from nm-applet when run from terminal as root
Filename:
MIME Type:
Creator:
Chris Hackmeyer
Created:
2007-12-04 19:29:00 UTC
Size:
3.96 KB
patch
obsolete
>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:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed >** Message: Found connection 'Auto Private WiFi' to activate at /org/freedesktop/NetworkManagerSettings/2. >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:4315): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): WARNING **: couldn't read 4 bytes from gnome-keyring socket: Connection reset by peer >** Message: <info> No keyring secrets found for Auto Private WiFi/802-11-wireless-security; ask the user > > >** (nm-applet:4315): WARNING **: couldn't read 4 bytes from gnome-keyring socket: Connection reset by peer >** Message: <info> New secrets for Auto Private WiFi/802-11-wireless-security requested; ask the user > > >** (nm-applet:4315): WARNING **: couldn't read 4 bytes from gnome-keyring socket: Connection reset by peer >** Message: <info> New secrets for Auto Private WiFi/802-11-wireless-security requested; ask the user > > >** (nm-applet:4315): WARNING **: applet.c.3134 (get_secrets_dialog_response_cb): canceled >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:4315): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed >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:4315): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_disconnect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed > >** (nm-applet:4315): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 356041
:
241011
|
241031
| 277271