Bug 246478 - Crash when joining hidden WEP network
Summary: Crash when joining hidden WEP network
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2007-07-02 15:56 UTC by Simon Goodall
Modified: 2008-05-04 15:35 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2008-05-04 15:35:34 UTC

Attachments (Terms of Use)
nm output in /var/log/messages (9.37 KB, text/plain)
2007-07-02 15:56 UTC, Simon Goodall
no flags Details

Description Simon Goodall 2007-07-02 15:56:44 UTC
Description of problem:
I was attempting to join a wireless network for the first time and NM crashed
two or three times while attempting to associate.
The wireless net is WEP-128 protected and has a hidden ssid and there was one or
two access points available. I have previously connected to these access points
before, however they had a different (hidden) ssid and WEP key.
The crash happened shortly after entering the ssid and WEP key information into
the "Connect to other wireless network" dialog.
I had several attempts to log into the network trying 128 passphase vs 128 hex
and open vs shared keys. Initially my mac address was not allowed by the AP's,
but later was. I think I managed to two or three attempts before the crashes
occurred. (Certainly not on the first attempt).

Version-Release number of selected component (if applicable):

How reproducible:
Happened a few attempts out of several attempts to connect to the network.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Simon Goodall 2007-07-02 15:56:44 UTC
Created attachment 158346 [details]
nm output in /var/log/messages

Comment 2 Dan Williams 2008-04-22 18:42:30 UTC
Does this still happen with NM 0.6.6 which is available from F7 updates?  If so,
could you install debuginfo for NM and get the system logs again?

Comment 3 Simon Goodall 2008-05-03 21:19:59 UTC
I am now running F8 and I have not experienced this problem.

Comment 4 Dan Williams 2008-05-04 15:35:34 UTC
Ok, thanks!

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