Bug 694743 - Cannot connect to "Red Hat" wireless network
Summary: Cannot connect to "Red Hat" wireless network
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-08 08:21 UTC by Vít Ondruch
Modified: 2011-05-11 10:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-11 10:56:29 UTC
Type: ---


Attachments (Terms of Use)
dmesg output (3.83 KB, text/plain)
2011-04-15 13:29 UTC, Jason Montleon
no flags Details

Description Vít Ondruch 2011-04-08 08:21:28 UTC
Description of problem:
I can successfully connect to various wireless networks, but I cannot connect to "Red Hat" wireless network. No error message appears in /var/log/messages neither in dmesg

Version-Release number of selected component (if applicable):
$ rpm -q NetworkManager
NetworkManager-0.8.998-2.git20110406.fc15.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Choose "Red Hat" from network indicator menu.
2. Nothing happens.
3. Choose "Red Hat" from control-center,
4. Nothing happens.
  
Expected results:
Should request credentials and connect to network.


Additional info:

Comment 1 Jason Montleon 2011-04-15 13:29:03 UTC
I had exactly the same result. Nothing is logged to /var/log/messages, wpa_supplicant.log, or dmesg.

I attempted to create the connection manually, and after doing that it at least asks for a password, but it doesn't even try to connect before failing after that; in this case I did get some output in dmesg which I am attaching.

03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
	Subsystem: Intel Corporation Device 1010
	Flags: bus master, fast devsel, latency 0, IRQ 49
	Memory at df3ff000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [c8] Power Management version 2
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Legacy Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 00-1f-3c-ff-ff-53-a8-68
	Kernel driver in use: iwl3945
	Kernel modules: iwl3945


NetworkManager-glib-devel-0.8.998-2.git20110406.fc15.x86_64
NetworkManager-0.8.998-2.git20110406.fc15.x86_64
NetworkManager-devel-0.8.998-2.git20110406.fc15.x86_64
NetworkManager-openconnect-0.8.1-7.git20110326.fc15.x86_64
NetworkManager-openvpn-0.8.998-1.git20110405.fc15.x86_64
NetworkManager-glib-0.8.998-2.git20110406.fc15.x86_64
NetworkManager-gnome-0.8.998-2.git20110406.fc15.x86_64
NetworkManager-pptp-0.8.998-1.fc15.x86_64
NetworkManager-vpnc-0.8.998-1.git20110405.fc15.x86_64

Comment 2 Jason Montleon 2011-04-15 13:29:49 UTC
Created attachment 492377 [details]
dmesg output

Comment 3 Jason Montleon 2011-04-20 14:59:28 UTC
I just updated to:
NetworkManager-devel-0.8.998-3.git20110419.fc15.x86_64
NetworkManager-glib-0.8.998-3.git20110419.fc15.x86_64
NetworkManager-gnome-0.8.998-3.git20110419.fc15.x86_64
NetworkManager-0.8.998-3.git20110419.fc15.x86_64
NetworkManager-openvpn-0.8.998-1.git20110405.fc15.x86_64
NetworkManager-openconnect-0.8.1-9.git20110419.fc15.x86_64
NetworkManager-pptp-0.8.998-1.fc15.x86_64
NetworkManager-glib-devel-0.8.998-3.git20110419.fc15.x86_64
NetworkManager-vpnc-0.8.998-1.git20110405.fc15.x86_64

and after restarting NetworkManager and nm-applet (restarting NetworkManager alone did not work) this now works as expected.

Comment 4 Jason Montleon 2011-04-20 15:03:36 UTC
Looking at the changelog for NetworkManager-0.8.998-3.git20110419.fc15.x86_64 it looks like this is probably a duplicate of Bug 694765 - Can't connect to WPA2 Enterprise networks

Comment 5 Vít Ondruch 2011-04-26 12:30:58 UTC
I have updated NetworkManager but nothing changed :(

$ rpm -q NetworkManager
NetworkManager-0.8.998-3.git20110419.fc15.x86_64

So it seems to be something different.

Comment 6 Vít Ondruch 2011-05-11 10:56:29 UTC
Update to gnome-shell-3.0.1-2 solved the remaining issues.


Note You need to log in before you can comment on or make changes to this bug.