| 2008-09-16 22:16:40 |
Patrick |
bug |
|
|
added bug |
| 2008-09-18 13:16:30 |
Mackenzie Morgan |
None: status |
New |
Incomplete |
|
| 2008-09-18 13:16:30 |
Mackenzie Morgan |
None: statusexplanation |
|
What isn't saving the password? Network Manager? WICD? Wifi-radar? Which wifi application are you using? |
|
| 2008-09-18 15:30:52 |
Mackenzie Morgan |
None: bugtargetdisplayname |
Ubuntu |
network-manager (Ubuntu) |
|
| 2008-09-18 15:30:52 |
Mackenzie Morgan |
None: bugtargetname |
ubuntu |
network-manager (Ubuntu) |
|
| 2008-09-18 15:30:52 |
Mackenzie Morgan |
None: statusexplanation |
What isn't saving the password? Network Manager? WICD? Wifi-radar? Which wifi application are you using? |
|
|
| 2008-09-18 15:30:52 |
Mackenzie Morgan |
None: title |
Bug #271097 in Ubuntu: "wireless password is not being saved (intrepid)" |
Bug #271097 in network-manager (Ubuntu): "wireless password is not being saved (intrepid)" |
|
| 2008-09-18 17:37:11 |
Mackenzie Morgan |
network-manager: status |
Incomplete |
Confirmed |
|
| 2008-09-18 17:37:11 |
Mackenzie Morgan |
network-manager: statusexplanation |
|
I think it's still supposed to store it in the keyring, but it's happened once before (and I wouldn't be surprised if it happened again) that NM and the keyring weren't interracting with each other properly. |
|
| 2008-09-20 11:09:33 |
Thomas Schewe |
description |
Using a Lenovo Notebook N200, Intel wireless, Intrepid Alpha5.
The Wireless password is not being saved and needs to be entered after every startup. |
Using a Lenovo Notebook N200, Intel wireless, Intrepid Alpha5.
The Wireless password is not being saved and needs to be entered after every startup.
This problem occurs on all types of wireless connections (WLAN and GSM). |
|
| 2008-09-22 20:48:03 |
C de-Avillez |
network-manager: importance |
Undecided |
Medium |
|
| 2008-09-22 20:48:03 |
C de-Avillez |
network-manager: statusexplanation |
I think it's still supposed to store it in the keyring, but it's happened once before (and I wouldn't be surprised if it happened again) that NM and the keyring weren't interracting with each other properly. |
setting IMportance to medium. This is still not clear: Both N-M and Evolution would be using gnome-keyring to store the passwords. So... what does the keyring have on passwords (Applications/Accessories/Passwords and Encryption Keys/Passwords); what keyrings are in use? Which keyring is set to automatically open on login? |
|
| 2008-09-27 19:40:55 |
Chris Jones |
bug |
|
|
added subscriber Alex Stansfield |
| 2008-09-28 16:17:12 |
Alexander Sack |
network-manager: status |
Confirmed |
Incomplete |
|
| 2008-09-28 16:17:12 |
Alexander Sack |
network-manager: statusexplanation |
setting IMportance to medium. This is still not clear: Both N-M and Evolution would be using gnome-keyring to store the passwords. So... what does the keyring have on passwords (Applications/Accessories/Passwords and Encryption Keys/Passwords); what keyrings are in use? Which keyring is set to automatically open on login? |
OK, since there is a bunch of different statements in here, lets try to start from scratch. If you see this bug please provide the following information: (please keep the questions inlined in your answer as it makes it easier to screen the content):
1. does this happen after upgrading from hardy without taking any configuration in connection editor?
2. have you used a vpn plugin in hardy? which plugin? does it still work?
3. what wireless security are you using? WEP, WPA-PSK, WPA-EAP?
4. can you connect at all? how many attempts does it usually take before a connect attempt succeeds?
5. is the password sometimes remembered or are you asked on _any_ connect attempt?
attachment A. please restart your system, reproduce the bug and attach your complete /var/log/syslog
attachment B. please attach your /etc/network/interfaces
Thanks,
- Alexander |
|
| 2008-09-28 17:25:31 |
Thomas Schewe |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-09-28 17:28:29 |
fimbulvetr |
bug |
|
|
added attachment 'interfaces' (interfaces) |
| 2008-09-28 17:47:20 |
Gert Kulyk |
bug |
|
|
added attachment 'syslog' (Relevant part of syslog, attachment a) |
| 2008-09-28 17:51:31 |
Dan Andreșan |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-09-28 18:11:29 |
Thomas Schewe |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-09-28 19:33:56 |
James Dupin |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-09-28 20:06:35 |
Nick B. |
bug |
|
|
added attachment 'syslog' (syslog) |
| 2008-09-28 20:07:01 |
Nick B. |
bug |
|
|
added attachment 'interfaces' (interfaces) |
| 2008-09-29 02:00:35 |
Martin Pool |
network-manager: status |
Incomplete |
Confirmed |
|
| 2008-09-29 02:00:35 |
Martin Pool |
network-manager: statusexplanation |
OK, since there is a bunch of different statements in here, lets try to start from scratch. If you see this bug please provide the following information: (please keep the questions inlined in your answer as it makes it easier to screen the content):
1. does this happen after upgrading from hardy without taking any configuration in connection editor?
2. have you used a vpn plugin in hardy? which plugin? does it still work?
3. what wireless security are you using? WEP, WPA-PSK, WPA-EAP?
4. can you connect at all? how many attempts does it usually take before a connect attempt succeeds?
5. is the password sometimes remembered or are you asked on _any_ connect attempt?
attachment A. please restart your system, reproduce the bug and attach your complete /var/log/syslog
attachment B. please attach your /etc/network/interfaces
Thanks,
- Alexander |
(marking confirmed as several people have provided the requested information.) |
|
| 2008-10-03 04:20:45 |
Alexander Sack |
network-manager: status |
Confirmed |
Fix Released |
|
| 2008-10-03 04:20:45 |
Alexander Sack |
network-manager: statusexplanation |
(marking confirmed as several people have provided the requested information.) |
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-01-15 04:00:24 |
Ross Patterson |
network-manager: status |
Fix Released |
Confirmed |
|
| 2009-01-15 04:00:24 |
Ross Patterson |
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 |
I can also confirm that this is still happening on a fully updated intrepid system. I also tried the solution of copying login.keyring to default and default.keyring. |
|
| 2009-10-02 22:04:20 |
Omegamormegil |
removed subscriber Omegamormegil |
|
|
|
| 2009-10-08 23:59:02 |
Nick B. |
removed subscriber Nick B. |
|
|
|
| 2010-04-30 15:25:06 |
Jack Leigh |
summary |
wireless password is not being saved (intrepid) |
wireless password is not being saved |
|
| 2010-04-30 16:00:55 |
Phil Turner |
removed subscriber Phil Turner |
|
|
|
| 2010-05-16 14:59:16 |
Bernhard Schuster |
removed subscriber soxs |
|
|
|
| 2010-05-17 09:32:35 |
Anton |
removed subscriber Anton |
|
|
|
| 2010-05-18 16:11:17 |
Alan Knowles |
removed subscriber Alan Knowles |
|
|
|
| 2010-05-18 20:20:43 |
Ross Patterson |
removed subscriber Ross Patterson |
|
|
|
| 2011-04-25 16:32:55 |
Victor Van Hee |
removed subscriber Victor Van Hee |
|
|
|
| 2012-05-30 09:32:19 |
Thomas Hood |
summary |
wireless password is not being saved |
System asks for the wireless password every time |
|
| 2012-06-04 14:26:29 |
H.-Dirk Schmitt |
bug |
|
|
added subscriber H.-Dirk Schmitt |
| 2012-06-23 04:05:35 |
Thomas Hood |
summary |
System asks for the wireless password every time |
NetworkManager asks for the wireless password every time |
|
| 2012-06-23 04:10:31 |
Thomas Hood |
marked as duplicate |
|
854833 |
|
