Bug 351421 - nm-applet can't connect WPA networks in last rawhide version (NetworkManager-gnome-0.7.0-0.3.svn3014.fc8)
Summary: nm-applet can't connect WPA networks in last rawhide version (NetworkManager-...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-24 22:24 UTC by Adrien Bustany
Modified: 2007-11-30 22:12 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-24 23:07:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
backtrace (8.23 KB, text/plain)
2007-10-24 22:24 UTC, Adrien Bustany
no flags Details

Description Adrien Bustany 2007-10-24 22:24:33 UTC
Description of problem:
When trying to connect a WPA network through the applet, the applet will crash

Version-Release number of selected component (if applicable):
NetworkManager-gnome-0.7.0-0.3.svn3014.fc8 (and -gnome too)

How reproducible:
Connect to a WPA/PSK (TKIP) network with the applet

Actual results:
The applet crashes

Expected results:
Well, I let you guess :-)

Additional info:
see attachment for backtrace

Comment 1 Adrien Bustany 2007-10-24 22:24:33 UTC
Created attachment 236721 [details]
backtrace

Comment 2 Adrien Bustany 2007-10-24 22:55:38 UTC
Tested with the svn3016 release, crashes too...

In the console I get a lot of
Error in get_property: Method "Get" with signature "ss" on interface
"org.freedesktop.DBus.Properties" doesn't exist

Driver : iwl3945


Comment 3 Adrien Bustany 2007-10-24 23:05:37 UTC
Here's the log of me (webustany) telling wwoods how I removed this behaviour,
this may be filed as another bug :

<webustany> actually, I was tired of unlocking the keyring at each login
<webustany> so I created an empty "login" keyring
<webustany> but even if I checked the "unlock at login" case, it still asked me
for the password
<webustany> si I set login as the default keyring, and added a few passes to it
<webustany> didn't work eithe
<webustany> r
<webustany> so I restored my default keyring, and let login
<webustany> then, nm would first ask me to unlock login, then to unlock default
<webustany> and crash
<webustany> I removed the login keyring, and everything works fine
<webustany> hard to guess huh ? :)


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