| 2006-03-25 23:31:59 |
hackel |
bug |
|
|
added bug |
| 2006-03-28 22:19:38 |
Kai F. Lahmann |
marked as duplicate |
|
35225 |
|
| 2007-08-10 09:27:45 |
Duncan Lithgow |
removed duplicate marker |
35225 |
|
|
| 2007-08-10 09:48:55 |
Duncan Lithgow |
description |
Version: 0.5.1-0ubuntu19
Network manager is working fine for me aside from requiring me to type in my WEP password again each time I start my computer or re-init the wireless connection. First it asks for my gnome-keyring password, then a short time later it asks for my WEP key again. I've tried deleting my keyring and starting from scratch but it doesn't seem to help. It won't remember it no matter what. This is really annoying, since now I have to type in BOTH my gnome-keyring password and my WEP key for my home network every time I start my computer.
I'm not sure how to debug this further, but here are the relevent bits from my syslog:
Mar 25 16:52:32 localhost NetworkManager: process_scan_results: assertion `res_buf_len > 0' failed
Mar 25 16:52:32 localhost NetworkManager: <WARNING>^I (): nm_device_wireless_process_scan_results(wlan0): process_scan_results() returned an error.
[repeats many times]
<information>^ISWITCH: no current connection, found better connection 'wlan0'.
Mar 25 16:53:11 localhost NetworkManager: <information>^IActivation (wlan0/wireless): access point 'xxx' is encrypted, but NO valid key exists. New key needed.
Then I give it the key and it works fine. I can't wait for the next version without gnome-keyring, but hope this problem gets fixed before then! Let me know what additional information is required. |
- Version: 0.5.1-0ubuntu19
+ Version: network-manager-gnome 0.6.5-0ubuntu8
Network manager is working fine for me aside from requiring me to type in my WEP password again each time I start my computer or re-init the wireless connection. First it asks for my gnome-keyring password, then a short time later it asks for my WEP key again. I've tried deleting my keyring and starting from scratch but it doesn't seem to help. It won't remember it no matter what. This is really annoying, since now I have to type in BOTH my gnome-keyring password and my WEP key for my home network every time I start my computer.
I'm not sure how to debug this further, but here are the relevent bits from my syslog:
Mar 25 16:52:32 localhost NetworkManager: process_scan_results: assertion `res_buf_len > 0' failed
Mar 25 16:52:32 localhost NetworkManager: <WARNING>^I (): nm_device_wireless_process_scan_results(wlan0): process_scan_results() returned an error.
[repeats many times]
<information>^ISWITCH: no current connection, found better connection 'wlan0'.
Mar 25 16:53:11 localhost NetworkManager: <information>^IActivation (wlan0/wireless): access point 'xxx' is encrypted, but NO valid key exists. New key needed.
Then I give it the key and it works fine. I can't wait for the next version without gnome-keyring, but hope this problem gets fixed before then! Let me know what additional information is required. |
|
| 2007-08-20 20:25:53 |
Pedro Villavicencio |
network-manager: status |
New |
Incomplete |
|
| 2007-08-20 20:25:53 |
Pedro Villavicencio |
network-manager: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? the gnome-keyring part is already fixed btw. Thanks in advance. |
|
| 2007-08-25 02:28:13 |
Aaron Whitehouse |
title |
Network Manager does not remember WEP key |
Network Manager does not remember WEP/WPA key |
|
| 2007-10-03 19:30:24 |
Pedro Villavicencio |
network-manager: status |
Incomplete |
Fix Released |
|
| 2008-04-16 08:23:37 |
Slight Slightly |
network-manager: status |
Fix Released |
Confirmed |
|
| 2008-06-23 22:33:10 |
Fabio M. Panico |
bug |
|
|
added attachment 'unnamed' (unnamed) |
| 2008-07-26 12:20:18 |
xens |
bug |
|
|
added attachment 'syslog_output.txt' (syslog_output.txt) |
| 2008-09-11 00:46:24 |
Alexander Sack |
network-manager: status |
Confirmed |
Invalid |
|
| 2008-09-11 00:46:24 |
Alexander Sack |
network-manager: statusexplanation |
|
i think this issue doesnt exist anymore. if i am wrong reopen. |
|
| 2008-09-24 17:27:01 |
der_vegi |
network-manager: status |
Invalid |
Confirmed |
|
| 2008-09-24 17:27:01 |
der_vegi |
network-manager: statusexplanation |
i think this issue doesnt exist anymore. if i am wrong reopen. |
|
|
| 2008-10-01 11:55:27 |
Andres Mujica |
description |
- Version: 0.5.1-0ubuntu19
+ Version: network-manager-gnome 0.6.5-0ubuntu8
Network manager is working fine for me aside from requiring me to type in my WEP password again each time I start my computer or re-init the wireless connection. First it asks for my gnome-keyring password, then a short time later it asks for my WEP key again. I've tried deleting my keyring and starting from scratch but it doesn't seem to help. It won't remember it no matter what. This is really annoying, since now I have to type in BOTH my gnome-keyring password and my WEP key for my home network every time I start my computer.
I'm not sure how to debug this further, but here are the relevent bits from my syslog:
Mar 25 16:52:32 localhost NetworkManager: process_scan_results: assertion `res_buf_len > 0' failed
Mar 25 16:52:32 localhost NetworkManager: <WARNING>^I (): nm_device_wireless_process_scan_results(wlan0): process_scan_results() returned an error.
[repeats many times]
<information>^ISWITCH: no current connection, found better connection 'wlan0'.
Mar 25 16:53:11 localhost NetworkManager: <information>^IActivation (wlan0/wireless): access point 'xxx' is encrypted, but NO valid key exists. New key needed.
Then I give it the key and it works fine. I can't wait for the next version without gnome-keyring, but hope this problem gets fixed before then! Let me know what additional information is required. |
== Regression details ==
Discovered in version: 0.7~~svn20080908t183521+eni0-0ubuntu4
Last known good version: 0.6.6-0ubuntu5
- Version: 0.5.1-0ubuntu19
+ Version: network-manager-gnome 0.6.5-0ubuntu8
Network manager is working fine for me aside from requiring me to type in my WEP password again each time I start my computer or re-init the wireless connection. First it asks for my gnome-keyring password, then a short time later it asks for my WEP key again. I've tried deleting my keyring and starting from scratch but it doesn't seem to help. It won't remember it no matter what. This is really annoying, since now I have to type in BOTH my gnome-keyring password and my WEP key for my home network every time I start my computer.
I'm not sure how to debug this further, but here are the relevent bits from my syslog:
Mar 25 16:52:32 localhost NetworkManager: process_scan_results: assertion `res_buf_len > 0' failed
Mar 25 16:52:32 localhost NetworkManager: <WARNING>^I (): nm_device_wireless_process_scan_results(wlan0): process_scan_results() returned an error.
[repeats many times]
<information>^ISWITCH: no current connection, found better connection 'wlan0'.
Mar 25 16:53:11 localhost NetworkManager: <information>^IActivation (wlan0/wireless): access point 'xxx' is encrypted, but NO valid key exists. New key needed.
Then I give it the key and it works fine. I can't wait for the next version without gnome-keyring, but hope this problem gets fixed before then! Let me know what additional information is required. |
|
| 2008-10-03 04:20:17 |
Alexander Sack |
network-manager: status |
Confirmed |
Fix Released |
|
| 2008-10-03 04:20:17 |
Alexander Sack |
network-manager: statusexplanation |
|
network-manager (0.7~~svn20080928t225540+eni0-0ubuntu2) intrepid; urgency=low
[ Alexander Sack < asac@ubuntu.com> ]
* remove patches forwarded/applied upstream
- delete debian/patches/80_lp259503_access_to_freed_device_struct.patch
- delete debian/patches/honour_resolvconf_exitcode.patch
- delete debian/patches/lp269010_keyfile_secrets_crash.patch
- update debian/patches/series
* LP: #276253 - NM 0.7 sets hostname to localhost.localdomain instead of
what is in /etc/hostname - we fallback to hostname configured in
/etc/hostname even when no distro specific system plugin is enabled; we
do this for all cases until a proper solution was found.
- add debian/patches/fix_system_hostname.patch
- update debian/patches/series
[ Matt Zimmerman < mdz@ubuntu.com> ]
* (apport hook) Use [].append rather than the += operator, to avoid things
like: "InterestingModules: b 4 4" (should be b44)
- update debian/source_network-manager.py
-- Alexander Sack < asac@ubuntu.com> Thu, 02 Oct 2008 20:37:20 +0200 |
|
| 2009-11-17 18:21:54 |
Ubuntu QA Website |
tags |
8.10 regression-potential |
8.10 iso-testing regression-potential |
|
| 2009-11-17 18:31:30 |
Mike Carpenter |
removed subscriber Mike Carpenter |
|
|
|
| 2009-11-17 20:10:20 |
Mathieu Pillard |
removed subscriber Mathieu Pillard |
|
|
|
| 2009-11-19 17:16:34 |
Scott Wegner |
removed subscriber Scott Wegner |
|
|
|
| 2009-11-21 10:38:53 |
wisecapt |
removed subscriber wisecapt |
|
|
|
| 2010-05-03 19:35:57 |
Simon Walker |
removed subscriber Simon Walker |
|
|
|
| 2010-08-13 21:03:40 |
Xodetaetl |
network-manager (Ubuntu): status |
Fix Released |
Confirmed |
|
| 2010-08-24 16:30:37 |
Pedro Villavicencio |
network-manager (Ubuntu): status |
Confirmed |
Fix Released |
|
