i have the same problem.Ill describe it anyways.
When my network disconnects for a long time (more than 2 mins. or so) then
network manager cannot connect to the same network again without restarting the
laptop or if i use the commands mentioned:
$ sudo /etc/init.d/network-manager restart
$ sudo
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on
the current status under the
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
I'm also having this trouble on a Dell precision m4300. I'm running:
Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929
(prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12 07:42:25 UTC 2008
The only customization I've performed is installed the driver
NVIDIA-Linu
I can confirm this on my Dell Vostro 1500. Some things happen:
*I can't use sudo
*I can't start most programs (e.g. gnome-terminal refuses to run, but say gnome
calculator works). If the program is already running, it seems to be fine.
*The hardware wifi killswitch does absolutely nothing. If the
Oh, yeah- also forgot to report that this happens very randomly, e.g. I
can't do any one thing to reproduce it. Happens about once per every two
days or so for me.
--
wi-fi connection goes down - reboot is required
https://bugs.launchpad.net/bugs/154549
You received this bug notification because
...and here goes the the last one.
Also, answering the questions in the bug policy: Kubuntu Gutsy was the
first thing installed on this laptop and -- as this is my production
computer full of data -- I don't have the chance to test it with other
distributions unless it's absolutely necessary. I ca
The dmesg log is taken a some time after a fresh boot, tell me if you
need one from right after when the bug happened.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/12070039/dmesg.log
--
wi-fi connection goes down - reboot is required
https://bugs.launchpad.net/bugs/154549
Yo
** Attachment added: "version.log"
http://launchpadlibrarian.net/12070018/version.log
--
wi-fi connection goes down - reboot is required
https://bugs.launchpad.net/bugs/154549
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
And I'm attaching more logs about my system as the kernel team bug
policy tells me to.
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/12070008/uname-a.log
--
wi-fi connection goes down - reboot is required
https://bugs.launchpad.net/bugs/154549
You received this bug notifica
I can confirm muszek's second problem in
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/154549/comments/3 -- the system becomes unstable and
I cannot sudo anymore. I'm running the latest Gutsy as of today on a
Thinkpad R61 with a stock ubuntu 2.6.22-14.52 and the ipw3495 driver
I am assigning this bug to the 'ubuntu-kernel-team' per their bug
policy. For future reference you can learn more about their bug policy
at https://wiki.ubuntu.com/KernelTeamBugPolicies .
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-
Ok, I kept switching networks until NM froze, at this point I did "sudo
iwlist eth1 scan" and it listed 12 separate networks (actually more
networks than NM was showing). So, I reloaded NM and it worked fine and
connected to my preferred network. I repeated this again until NM froze
for the secon
I read through that other thread and I'm not sure if I'm having that
exact same problem. It seems that the problem they're having with the
driver is maybe a lot more drastic, mine only goes down once in a while.
I've found recently that I don't need to reboot, per se, but just kill
the Network Man
Perhaps this bug should be marked as duplicate of
https://bugs.launchpad.net/ipw3945/+bug/134515 , which has reports of
similar or the same problem from more competent users ;
--
wi-fi connection goes down - reboot is required
https://bugs.launchpad.net/bugs/154549
You received this bug notificat
What is the meaning of the following error I'm seeing over and over and
over again? (Muszek, I followed your lead and checked my /var/log/syslog
as well)
Oct 26 08:17:01 dell NetworkManager: Error getting killswitch power:
org.freedesktop.Hal.Device.KillSwitch.NotSupported - Access type not sup
I can confirm this also.
I just upgraded to Gutsy, everything wireless was fine in Feisty, but
the network manager lags and hangs and won't switch wireless networks
and often won't connect (or takes forever) and freezes eventually if I
try to do too much with it.
I've tried reloading but for me i
2 days later. It happened a few more times. New observations:
I can observe three different behaviors when the situation occurs:
* as noted above - I kill & start NetworkManager and everything's fine.
Actually it only happened once.
* more frequent - the whole OS becomes unstable - I can use
I've lived a bit longer with this bug. Here's what I've observed.
Most important: I guess it's NetworkManager. It has just happened to me and I
noticed that System Monitor panel applet indicates that 50% CPU is used (I have
Core 2 Duo). Weird thing though: at the same time top showed that
Net
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
https://wiki.ubuntu.com/Bugs
20 matches
Mail list logo