We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
still a problem with NetworkManager 0.7 in intrepid?
--
nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' characters
https://bugs.launchpad.net/bugs/155304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
No, it doesn't work.
--
nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' characters
https://bugs.launchpad.net/bugs/155304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Hi all!
Just has resolved the problem.
Add to /etc/rc.local
sleep 15s
/etc/init.d/networking restart
before "exit" string
reboot
wi-fi starts as it should
It's like network start up earlier than something that need for wifi..
--
nm-applet (network manager) - don't remember settings when SSID
Hi all!
Just has resolved the problem.
Add to /etc/rc.local
sleep 15s
/etc/init.d/networking restart
before "exit" string
It's like network start up earlier than something that need for wifi..
--
nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' charact
I have the problem on Hardy.
In my case the SSID is 4 alphanumeric characters but the password includes a ?
The SSID is hidden, MAC filtering is on, WPA2, AES.
On boot the SSID is show in the list of networks but selecting it fails.
You have to COnnect to another network and enter all the details
Hi all,
I have just installed Ubuntu 8.04 on my Toshiba notebook and I can say that
this bug doesn't exist.
Now (with Ubuntu 8.04), wifi works fine.
Regards.
--
nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' characters
https://bugs.launchpad.net/bugs/
Hi Alexander,
if you ask me I can say that I have not installed hardy beta on my laptop yet.
Now, I am using windows on my lapotop (it's shame for me ;) but I have no
problems with wifi on windows :( ).
Maybe dnquark tested hardy on his laptop?
--
nm-applet (network manager) - don't remember se
Hi,
do you still see this with 0.6.6-0ubuntu5 package in hardy?
--
nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' characters
https://bugs.launchpad.net/bugs/155304
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I am facing the same bug when using Purdue University's wireless
network: the SSID is PAL2.0 (note the ".") and all settings pertaining
to the connection get lost upon reboot or resume from suspend. This is
problem, since the process of setting up that connection is relatively
involved, and at the
Paul, I think that everything I described earlier (with kind of characters used
in ssid) is still true and this is still a problem.
Therefore I think, that previous status "confirmed" was ok.
Second problem (last post) which I noticed is, that password can't be
changed to the other password, beca
Ok (marking bug as incomplete, time to get a better picture of what is
going on)
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' characters
https://bugs.launchpad.net/bugs/
Paul, I thought that after changing ssid to shorter name, without strange
characters, everything will be ok but I was wrong :(
When I only changed password to the new one, after reboot wifi didn't work too
:(
I have no idea what is wrong.
I tried to delete all old keys in keyring-manager and all
Jonj, what you described is a known bug (the number I don't have right now).
Gareth, I guess you should open a new bug, as zajjar is now describing
something different than you.
I am confirming this bug as I believe there is enough information for a
developer to 'at least investigate if not fix'
Jonj, what you described is a known bug (the number I don't have right now).
Gareth, I guess you should open a new bug, as zajjar is now describing
something different than you.
I am confirming this bug as I believe there is enough information for a
developer to 'at least investigate if not fix'
** Summary changed:
- nm-applet (network manager) - don't remember settings
+ nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' characters
--
nm-applet (network manager) - don't remember settings when SSID contains some
'uncommon' characters
https://bugs.
I tested many settings with WPA2 on my fresh Ubuntu installation and I
noticed that probably problem is in SSID name.
For example I had problem when I used this SSID:
sM&jK,*.$:")X'Z{c;/[EMAIL PROTECTED](!S6+R-QLt
(it's not a joke :) this is for test only)
With this SSID WiFi works fine only to
Oops, marking back as Incomplete.
Syslog_fail is Gareth file, which does not seems to get fixed the same way for
zajjar (bug reporter).
Zajjar, please your /var/log/syslog file afer a fail connection.
Jonj, please do the same.
Please keep all in mind bug #140422!
** Changed in: network-manager
Marking as Confirmed (was New).
Syslog_fail contains this:
Oct 21 21:00:46 localhost NetworkManager:
nm_utils_supplicant_request_with_check(): real_write_supplicant_config:
supplicant error for 'SET_NETWORK 0 psk '. Response: 'FAIL'
** Description changed:
I use Ubuntu 7.10 GutsyGibbon.
+
Very similar here. Network manager remembers the key for WEP
encryption, but not for WPA encryption
Network manager was working fine with WEP encryption on the router. I
changed the router to WPA encryption, rebooted the laptop etc. and
attempted to connect to the wireless. First of all, NM d
Thank you Gareth for your help but your solution doesn't work for me :(
I tested it in fresh installation Ubuntu. I had only two entries in my keyring
manager: "login" and "session" and I deleted, like you said, only "login" entry.
When I restarted my laptop I didn't see any request for wireless d
Solution:
I have just discovered that my Keyring Manager was muddled.
This is what worked for me:
1/ restart PC & get wireless going.
2/ Goto Keyring Manager.
3/ You should see perhaps 4 entries (under the view drop-down menu choose
keyrings).
Entries will probably be "SSID name", Login", "
** Attachment added: "syslog_success"
http://launchpadlibrarian.net/10106967/syslog_success
--
nm-applet (network manager) - don't remember settings
https://bugs.launchpad.net/bugs/155304
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I can confirm this also for 7.10.
This occurs for both "roaming mode" & manual setup (dhcp).
See attached syslog extracts: one for fail & one for success.
It appears that the Network Manager requests a key and is given a key
but the key appears to be incorrect.
Also, [Logout] and then [Log back
** Changed in: network-manager (Ubuntu)
Sourcepackagename: None => network-manager
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: network-manager (Ubuntu)
Importance: Low => Medium
--
nm-applet (network manager) - don't remember settings
https://bugs.l
25 matches
Mail list logo
