please get a backtrace as documented in the debugging crashes section on
https://wiki.ubuntu.com/DebuggingNetworkManager
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
Status: New => Incomplete
--
Cannot connect to a WPA
I assume that the wiki page meant tail -f -n0 /var/log/syslog >
/tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which
outputs nothing.
Happily (or I guess unfortunately, depending on how you look at it) I
wasn't able to replicate the crash. However there is still a bug. When
I
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
do you still see this in latest hardy? If so, please attach your
_complete_ /Var/log/syslog taken _after_ you reproduced this problem.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim
Yes, it still happens on the first connections. I have to manually
enter the network information, and even then, it only connects after
several reattempts.
Here is the syslog as requested.
** Attachment added: "syslog"
http://launchpadlibrarian.net/13010977/syslog
--
Cannot connect to a WPA
Sorry, that log has other information from boot (in order to reproduce
the problem, I have to delete the connection from gconf as it only
happens on the first connection attempts). This log contains only the
boot where the config info wasn't present and I had to enter manually.
** Attachment adde
do you still have problems with prism chipset with intrepid kernel?
** Changed in: linux (Ubuntu)
Sourcepackagename: network-manager => linux
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notifi
I'm not sure, I've retired that laptop. I still have it though so I
will dig it out of storage and give it a try later in the week.
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification bec
Yes, now the option for WPA is not given anywhere, even under the manual
setup. I don't have a network cable handy at the moment to see if there
are any updates available. I don't know what logs might be useful in
this case either.
--
Cannot connect to a WPA enabled network with NetworkManager
do you still have problems with prism chipset with intrepid kernel?
** Changed in: linux (Ubuntu)
Sourcepackagename: network-manager => linux
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notifi
do you still see this in latest hardy? If so, please attach your
_complete_ /Var/log/syslog taken _after_ you reproduced this problem.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim
Yes, it still happens on the first connections. I have to manually
enter the network information, and even then, it only connects after
several reattempts.
Here is the syslog as requested.
** Attachment added: "syslog"
http://launchpadlibrarian.net/13010977/syslog
--
Cannot connect to a WPA
Sorry, that log has other information from boot (in order to reproduce
the problem, I have to delete the connection from gconf as it only
happens on the first connection attempts). This log contains only the
boot where the config info wasn't present and I had to enter manually.
** Attachment adde
I'm not sure, I've retired that laptop. I still have it though so I
will dig it out of storage and give it a try later in the week.
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification bec
Yes, now the option for WPA is not given anywhere, even under the manual
setup. I don't have a network cable handy at the moment to see if there
are any updates available. I don't know what logs might be useful in
this case either.
--
Cannot connect to a WPA enabled network with NetworkManager
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
please get a backtrace as documented in the debugging crashes section on
https://wiki.ubuntu.com/DebuggingNetworkManager
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
Status: New => Incomplete
--
Cannot connect to a WPA
I assume that the wiki page meant tail -f -n0 /var/log/syslog >
/tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which
outputs nothing.
Happily (or I guess unfortunately, depending on how you look at it) I
wasn't able to replicate the crash. However there is still a bug. When
I
please get a backtrace as documented in the debugging crashes section on
https://wiki.ubuntu.com/DebuggingNetworkManager
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
Status: New => Incomplete
--
Cannot connect to a WPA
I assume that the wiki page meant tail -f -n0 /var/log/syslog >
/tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which
outputs nothing.
Happily (or I guess unfortunately, depending on how you look at it) I
wasn't able to replicate the crash. However there is still a bug. When
I
Yes, it still happens on the first connections. I have to manually
enter the network information, and even then, it only connects after
several reattempts.
Here is the syslog as requested.
** Attachment added: "syslog"
http://launchpadlibrarian.net/13010977/syslog
--
Cannot connect to a WPA
Sorry, that log has other information from boot (in order to reproduce
the problem, I have to delete the connection from gconf as it only
happens on the first connection attempts). This log contains only the
boot where the config info wasn't present and I had to enter manually.
** Attachment adde
do you still see this in latest hardy? If so, please attach your
_complete_ /Var/log/syslog taken _after_ you reproduced this problem.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim
do you still have problems with prism chipset with intrepid kernel?
** Changed in: linux (Ubuntu)
Sourcepackagename: network-manager => linux
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notifi
I'm not sure, I've retired that laptop. I still have it though so I
will dig it out of storage and give it a try later in the week.
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification bec
Yes, now the option for WPA is not given anywhere, even under the manual
setup. I don't have a network cable handy at the moment to see if there
are any updates available. I don't know what logs might be useful in
this case either.
--
Cannot connect to a WPA enabled network with NetworkManager
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
do you still have problems with prism chipset with intrepid kernel?
** Changed in: linux (Ubuntu)
Sourcepackagename: network-manager => linux
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notifi
I'm not sure, I've retired that laptop. I still have it though so I
will dig it out of storage and give it a try later in the week.
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification bec
Yes, now the option for WPA is not given anywhere, even under the manual
setup. I don't have a network cable handy at the moment to see if there
are any updates available. I don't know what logs might be useful in
this case either.
--
Cannot connect to a WPA enabled network with NetworkManager
Yes, it still happens on the first connections. I have to manually
enter the network information, and even then, it only connects after
several reattempts.
Here is the syslog as requested.
** Attachment added: "syslog"
http://launchpadlibrarian.net/13010977/syslog
--
Cannot connect to a WPA
Sorry, that log has other information from boot (in order to reproduce
the problem, I have to delete the connection from gconf as it only
happens on the first connection attempts). This log contains only the
boot where the config info wasn't present and I had to enter manually.
** Attachment adde
do you still see this in latest hardy? If so, please attach your
_complete_ /Var/log/syslog taken _after_ you reproduced this problem.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim
do you still have problems with prism chipset with intrepid kernel?
** Changed in: linux (Ubuntu)
Sourcepackagename: network-manager => linux
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notifi
I'm not sure, I've retired that laptop. I still have it though so I
will dig it out of storage and give it a try later in the week.
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification bec
Yes, now the option for WPA is not given anywhere, even under the manual
setup. I don't have a network cable handy at the moment to see if there
are any updates available. I don't know what logs might be useful in
this case either.
--
Cannot connect to a WPA enabled network with NetworkManager
please get a backtrace as documented in the debugging crashes section on
https://wiki.ubuntu.com/DebuggingNetworkManager
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
Status: New => Incomplete
--
Cannot connect to a WPA
I assume that the wiki page meant tail -f -n0 /var/log/syslog >
/tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which
outputs nothing.
Happily (or I guess unfortunately, depending on how you look at it) I
wasn't able to replicate the crash. However there is still a bug. When
I
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Yes, it still happens on the first connections. I have to manually
enter the network information, and even then, it only connects after
several reattempts.
Here is the syslog as requested.
** Attachment added: "syslog"
http://launchpadlibrarian.net/13010977/syslog
--
Cannot connect to a WPA
Sorry, that log has other information from boot (in order to reproduce
the problem, I have to delete the connection from gconf as it only
happens on the first connection attempts). This log contains only the
boot where the config info wasn't present and I had to enter manually.
** Attachment adde
do you still see this in latest hardy? If so, please attach your
_complete_ /Var/log/syslog taken _after_ you reproduced this problem.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim
please get a backtrace as documented in the debugging crashes section on
https://wiki.ubuntu.com/DebuggingNetworkManager
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
Status: New => Incomplete
--
Cannot connect to a WPA
I assume that the wiki page meant tail -f -n0 /var/log/syslog >
/tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which
outputs nothing.
Happily (or I guess unfortunately, depending on how you look at it) I
wasn't able to replicate the crash. However there is still a bug. When
I
please get a backtrace as documented in the debugging crashes section on
https://wiki.ubuntu.com/DebuggingNetworkManager
Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Alexander Sack (asac)
Status: New => Incomplete
--
Cannot connect to a WPA
I assume that the wiki page meant tail -f -n0 /var/log/syslog >
/tmp/syslog, rather than tail -n0 /var/log/syslog > /tmp/syslog, which
outputs nothing.
Happily (or I guess unfortunately, depending on how you look at it) I
wasn't able to replicate the crash. However there is still a bug. When
I
Yes, it still happens on the first connections. I have to manually
enter the network information, and even then, it only connects after
several reattempts.
Here is the syslog as requested.
** Attachment added: "syslog"
http://launchpadlibrarian.net/13010977/syslog
--
Cannot connect to a WPA
Sorry, that log has other information from boot (in order to reproduce
the problem, I have to delete the connection from gconf as it only
happens on the first connection attempts). This log contains only the
boot where the config info wasn't present and I had to enter manually.
** Attachment adde
do you still see this in latest hardy? If so, please attach your
_complete_ /Var/log/syslog taken _after_ you reproduced this problem.
Thanks!
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim
do you still have problems with prism chipset with intrepid kernel?
** Changed in: linux (Ubuntu)
Sourcepackagename: network-manager => linux
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notifi
I'm not sure, I've retired that laptop. I still have it though so I
will dig it out of storage and give it a try later in the week.
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification bec
Yes, now the option for WPA is not given anywhere, even under the manual
setup. I don't have a network cable handy at the moment to see if there
are any updates available. I don't know what logs might be useful in
this case either.
--
Cannot connect to a WPA enabled network with NetworkManager
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
Cannot connect to a WPA enabled network with NetworkManager and Prisim 2.5
chipset
https://bugs.launchpad.net/bugs/141620
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
54 matches
Mail list logo
