| 2007-06-20 21:36:56 |
yostral |
bug |
|
|
added bug |
| 2007-06-20 22:03:34 |
Brian Murray |
network-manager: status |
Unconfirmed |
Needs Info |
|
| 2007-06-20 22:03:34 |
Brian Murray |
network-manager: assignee |
|
brian-murray |
|
| 2007-06-20 22:03:34 |
Brian Murray |
network-manager: statusexplanation |
|
Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the full contents of '/var/log/daemon.log' as an attachment to your bug report? Thanks in advance. |
|
| 2007-06-22 00:06:31 |
Brian Murray |
network-manager: status |
Incomplete |
Triaged |
|
| 2007-06-22 00:06:31 |
Brian Murray |
network-manager: importance |
Undecided |
High |
|
| 2007-06-22 00:06:31 |
Brian Murray |
network-manager: statusexplanation |
Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the full contents of '/var/log/daemon.log' as an attachment to your bug report? Thanks in advance. |
I have recreated this bug on Gutsy using network-manager version 0.6.5-0ubuntu2. |
|
| 2007-06-22 00:06:31 |
Brian Murray |
network-manager: assignee |
brian-murray |
|
|
| 2007-06-22 00:07:10 |
Brian Murray |
bug |
|
|
added attachment 'daemon.log' (daemon.log) |
| 2007-06-22 00:07:47 |
Brian Murray |
network-manager: statusexplanation |
|
|
|
| 2007-06-22 00:17:31 |
Brian Murray |
network-manager: status |
Triaged |
Confirmed |
|
| 2007-06-25 11:03:19 |
yostral |
bug |
|
|
added attachment 'daemon.log' (daemon.log) |
| 2007-06-26 17:55:20 |
Martin Pitt |
network-manager: status |
Confirmed |
Incomplete |
|
| 2007-06-26 17:55:20 |
Martin Pitt |
network-manager: statusexplanation |
|
It generally works for me (with the bcm43xx driver, though) with the latest packages in gutsy. Can you please upgrade network-manager and network-manager gnome and see whether they fix the connection? Thank you! |
|
| 2007-07-01 08:16:04 |
Kyle S |
bug |
|
|
added attachment 'daemon.log-with-comments.txt' (daemon.log with play-by-play) |
| 2007-07-04 14:19:24 |
Bipolar |
bug |
|
|
added attachment 'syslog-ipw3945.log' (syslog-ipw3945.log) |
| 2007-07-05 21:05:50 |
Trond Thorbjørnsen |
bug |
|
|
added attachment 'daemon.log' (daemon.log) |
| 2007-07-17 06:10:47 |
Sarah Kowalik |
network-manager: assignee |
|
asac |
|
| 2007-07-17 06:10:47 |
Sarah Kowalik |
network-manager: statusexplanation |
It generally works for me (with the bcm43xx driver, though) with the latest packages in gutsy. Can you please upgrade network-manager and network-manager gnome and see whether they fix the connection? Thank you! |
|
|
| 2007-07-19 16:50:18 |
Nic |
bug |
|
|
added attachment 'attach1.txt' (attach1.txt) |
| 2007-07-30 01:59:25 |
Jonathan Anderson |
description |
Binary package hint: network-manager
I have a Intel wireless 3945 chip, using the ipw3945 driver, and working wonderfully with Feisty.
With Gutsy up to date (kernel 2.6.22-6 generic, network-manager 0.6.5, but it was the same with NM 0.6.4), NM is unable to connect to my wireless network. It shows the SSID, the strength of the signal, but can't connect, even when my network is open (no wep, nothing...).
I can connect without any problem from term or from the Networks admin GUI.
I have a kill switch button. But it's the same is I start with wireless on or off.
In the logs, everything is ok. But time out after 120s. |
Binary package hint: network-manager
I have a Intel wireless 3945 chip, using the ipw3945 driver, and working wonderfully withcomment Feisty.
With Gutsy up to date (kernel 2.6.22-6 generic, network-manager 0.6.5, but it was the same with NM 0.6.4), NM is unable to connect to my wireless network. It shows the SSID, the strength of the signal, but can't connect, even when my network is open (no wep, nothing...).
I can connect without any problem from term or from the Networks admin GUI.
I have a kill switch button. But it's the same is I start with wireless on or off.
In the logs, everything is ok. But time out after 120s. |
|
| 2007-07-30 21:59:43 |
exactt |
bug |
|
|
added attachment 'daemon.log' (/var/log/daemon.log) |
| 2007-08-08 07:15:10 |
Martin Pitt |
network-manager: statusexplanation |
|
This was confirmed as fixed for two people, Chris still experienced it. Chris, can you please check with 0.6.5-0ubuntu9 again?
Moving over to Tribe 5, this is not a blocker any more since it seems to work now. |
|
| 2007-08-09 05:50:59 |
Ashton Batty |
bug |
|
|
added attachment 'daemon.log' (relevant (hopefully) excerpt of daemon.log) |
| 2007-08-09 21:57:12 |
Jose Bernardo |
bug |
|
|
added attachment 'syslog' (syslog extract) |
| 2007-08-10 00:10:37 |
Alex Wauck |
bug |
|
|
added attachment 'daemon.log' (daemon.log) |
| 2007-08-17 13:42:49 |
Alexander Sack |
network-manager: statusexplanation |
No luck for me either. Network manager still doesn't want to connect to wpa2-enterprise network, (works fine in Fedora 7, so I know network manager *can* do it). I never got the various workarounds to work either, though I have not had trouble using wpa_supplicant manually. I'll try again tomorrow after purging and reinstalling network-manager et al, and using clean gconf. |
we should take a close look for tribe-6 |
|
| 2007-08-31 16:32:47 |
Alexander Sack |
network-manager: status |
Incomplete |
Confirmed |
|
| 2007-09-06 09:17:04 |
Alexander Sack |
network-manager: status |
Confirmed |
In Progress |
|
| 2007-09-09 10:47:08 |
stdPikachu |
bug |
|
|
added attachment 'wpa_auth_fail' (syslog entry for WPA conection) |
| 2007-09-10 09:27:28 |
Alexander Sack |
network-manager: status |
In Progress |
Fix Released |
|
| 2008-02-20 12:04:14 |
drink |
bug |
|
|
added attachment 'daemon.log.bz2' (daemon.log.bz2) |
