As I said before, with the new version I still have this problem (but
not related to wpa or suspend/resume). When the system boots I get right
away 100% cpu and must kill NetworkManager. I tried reinstalling the
packages for NM several times and it doesn't work. I'm alone on that
boat it seems? Any
Just a note, it happened again. It's more difficult to trigger now than before
the update, but it's not gone. Switching from wireless to wired across suspends
seems to trigger it.
My wireless is ndiswrapper and wired r8169, if this can make a difference.
--
Network manager crash with WPA
https:
Copied to gutsy-updates.
** Changed in: network-manager (Ubuntu Gutsy)
Status: Fix Committed => Fix Released
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
Although the update is not perfect, there have been no reports about
apparent regressions, there is some good feedback here, and excellent
feedback in bug 83623. Considering verified.
** Tags added: verification-done
** Tags removed: verification-needed
--
Network manager crash with WPA
https:/
I tried the 0.6.5 17 package from proposed but I am still not able to
connect to my universities 802.1X wpa enterprise network. After this
update it is for me also not possible to access the open university
network which has a little low signal quality
--
Network manager crash with WPA
https://bu
You can turn on the proposed updates, then refresh the list of updates.
Only tick the ones you want and update, then disabled the proposed
updates.
Stéphane
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubu
It is working well now for me too, that first hang seems to be not
reproducible.
By the way, there is a trick to install just one gutsy-proposed package without
having to enable the repository, did the upgrade of just that one over the 20
or so available there, and then re-disabling it?
Thank
** Tags added: metabug
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
** Description changed:
NetworkManager crashes on my system when I roam from an open network to
a WPA-protected one.
- please test proposed fix: https://bugs.edge.launchpad.net/ubuntu/+source
- /network-manager/+bug/145683/comments/15
+ To reproduce:
+ + suspend/resume often triggers this
I tried too with the package 0.6.5-0ubuntu16.7.10.0, and so far the
suspend/resume seems to work great... I've tested it 4-5 times.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
I tried the package from gutsy-proposed, I have had the crash again...
here it is:
Nov 26 09:50:41 rukbat NetworkManager: [Thread debugging using libthread_db
enabled]
Nov 26 09:50:41 rukbat NetworkManager: [New Thread -1212455248 (LWP 11942)]
Nov 26 09:50:41 rukbat NetworkManager: [New Thread -1
I still have this problem with this package (0.6.5-0ubuntu16.7.10.0),
but maybe there's another bug, since I don't see the relation to WPA. I
just boot and get this 100% cpu. I must kill it in order for the system
to function correctly, and use the normal manual networking to connect
to wireless/ne
With 0.6.5-0ubuntu16.7.10.0, out of three suspend/resume cycles, my
*wired* network has only resumed correctly once. Both other times I
tried to 'sudo dhclient eth0', but this failed as well. I fixed it both
times by using nm-applet to first disable networking and then enable it.
I still had to man
With gutsy's original version, after a few suspend/resume cycles,
networking did not wake up (only tried wireless). It worked fine with
the ppa3 version, and now, the new version of gutsy-proposed works fine
as well.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You rec
Testing the gutsy-proposed package:
- Wireless works fine returning from suspend.
- Wireless also works fine returning from hibernation.
Yep, seems to be fixed! At least for me. ;-)
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification becau
Accepted into gutsy-proposed, please test.
** Tags added: verification-needed
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
network-manager (0.6.5-0ubuntu17) hardy; urgency=low
* upload 0.6.5-0ubuntu17 to hardy
network-manager (0.6.5-0ubuntu16.7.10.0) gutsy-proposed; urgency=low
Release changes from test package previously known as 0.6.5-0ubuntu16~ppa3:
* drop gracefull supplicant shutdown feature and its follo
** Changed in: network-manager (Ubuntu Gutsy)
Status: New => Fix Committed
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
joss, please try the 0.6.5-0ubuntu16~ppa3 version from comment #15.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
I'm still getting this with the latest Gutsy package. My syslog is
attached.
This might be the relevant part:
Nov 4 16:03:23 localhost anacron[7018]: Normal exit (0 jobs run)
Nov 4 16:03:24 localhost kernel: [ 6384.58] ipw3945: Detected geography
ABG (13 802.11bg channels, 23 802.11a chan
~ppa3 seems to fix the problem for me (I didn't see high CPU loads, just
the crashes after resuming from suspend).
However, would it be possible to build a package with a version number
that apt does not consider to be a downgrade from the version released
in Gutsy? apt, aptitude and update-manage
I'm having a similar issue on Gutsy (release version): NetworkManager
doesn't actually crash, but pegs the CPU at 100% and loses the
connection. My wi-fi card is an Intel ProSet using open-source drivers
on a Centrino notebook (Toshiba M35X S311) .
--
Network manager crash with WPA
https://bugs.l
Is my problem different from this? Because I know that the latest ppa
package does NOT fix it for me - my NetworkManager still randomly
crashes...
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs,
Confirm ~ppa3 solves this problem for me as well.
I have had similar problems with ipw3945 causing random crashes as
described above. I haven't had any problems since switching from the
NEWER 0.6.5-0ubuntu16 to the PPA repository's 0.6.5-0ubuntu16~ppa3,
which according to the changelogs has a dif
I was also having CPU spikes and crashes in NM (requiring a dbus restart
to fix), usually when switching wireless networks or interfaces (i.e.
wireless to wired). There was also considerable lag in detecting new
wireless networks and between when I chose a new network and it actually
started connec
I just came back from lunch and NM (ppa3) was using 95% CPU again.
However, I can't see any crashes in the log, just various dhcp requests
and responses.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Since I switched to ppa3, I haven't seen any cpu spikes, nm crashes, or
nm-related suspend/resume issues. Huge step up in reliability.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Maybe I spoke too soon: several hours later network-manager is using
about 50% CPU. The main things that have happened in the meantime
according to daemon.log are:
* I used vpnc to connect and disconnect to a remote network.
* A virtual network used by vmware-server has been regularly requesting a
I did a test and ppa3 seems to fix my problem as well (mine wasn't
related to WPA, but to using nm-applet to change the wired connection to
a static address - see bug #153816).
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you
if the proposed package in this bugs fixes your crashes as well, please
let us know.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Committed
Target: ubuntu-7.10-rc => gutsy-updates
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You recei
ppa3 has been working fine for me for the last 4 days. Will update with
results next week.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs ma
The proposed fix resolved my issue (LP bug 153758):
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/153758
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Description changed:
NetworkManager crashes on my system when I roam from an open network to
a WPA-protected one.
+
+ please test proposed fix: https://bugs.edge.launchpad.net/ubuntu/+source
+ /network-manager/+bug/145683/comments/15
+
Backtrace from NM:
Program received signal
this is obviously confirmed. any instructions on how to reproduce with
the ~ppa3 package still appreciated.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because
Ryan, please open a new bug and attach your /var/log/syslog
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
OK, so it probably is a different issue - my problem is that NetworkManager
dies after working properly for a while...
On 10/16/07, Ryan Gordon <[EMAIL PROTECTED]> wrote:
>
> No, it doesn't work if I reset my virtual machine. I've tried it several
> times before already.
>
> What I did was:
> 1) B
No, it doesn't work if I reset my virtual machine. I've tried it several
times before already.
What I did was:
1) Burn Gusty ISO to a DVD
2) Setup Ubuntu in VM
3) Install VMWare Tools (Note: It still worked after I installed it)
4) Installed Updates
5) Restarted computer
6) No internet connection
If you reset your virtual machine, does NetworkManager work for a while
after the reset?
On 10/16/07, Ryan Gordon <[EMAIL PROTECTED]> wrote:
>
> Just wanted to let you know that I'm experiencing the same problems as
> Tim Hull. I'm on Ubuntu Gusty installed into VMWare - Everything was
> working f
please outline your setup (in vm) and explain how you trigger it ...
maybe i can finally reproduce this issue as well.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Just wanted to let you know that I'm experiencing the same problems as
Tim Hull. I'm on Ubuntu Gusty installed into VMWare - Everything was
working fine until I updated and then it gives me the same "No Network
Devices Have Been Found" error as Tim.
I can join the IRC channel. I've had some experi
Here's the output before the crash...
[EMAIL PROTECTED]:/root/network-manager-0.6.5/src$ sudo gdb
.libs/lt-NetworkManager
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or
Here's the thread apply all backtrace:
(gdb) thread apply all bt
Thread 3 (Thread -1221059696 (LWP 3394)):
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7c8b647 in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7dac593 in ?? () from /usr/lib/libglib-2.0.so.0
#3 0x0809d628 in ?? ()
#4 0x00
Here's the backtrace info...
Program received signal SIGPIPE, Broken pipe.
[Switching to Thread -1212664144 (LWP 3388)]
0xe410 in __kernel_vsyscall ()
(gdb) bt
#0 0xe410 in __kernel_vsyscall ()
#1 0xb7c8ddce in writev () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7e9deb6 in ?? () from /usr/
is this a patch for my issue? If so, could you post a .deb?
On 10/15/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
>
> ** Attachment added: "patch to drop supplicant shutdown feature and its
> followup patches"
>http://launchpadlibrarian.net/10004427/lp145683-proposed.patch
>
> --
> Network
** Attachment added: "patch to drop supplicant shutdown feature and its
followup patches"
http://launchpadlibrarian.net/10004427/lp145683-proposed.patch
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubu
Tim?
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
thanks a lot.
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
Yes, I know that - this just isn't the greatest time at the moment. I
should have time tomorrow, though - and Monday/Tuesday...
I just installed your new package, and will report if it improves anything.
On 10/12/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> well ... time is not on our side .
well ... time is not on our side ... we release next week ... so please
test asap.
anyway ... there are new packages in my ppa:
0.6.5-0ubuntu16~ppa3 ...
http://ppa.launchpad.net/asac/ubuntu/pool/main/n/network-manager/
Thanks,
- Alexander
--
Network manager crash with WPA
https://bugs.la
I will try sometime in the next few days - I've been busy...
On 10/11/07, Alexander Sack <[EMAIL PROTECTED]> wrote:
>
> Tim, if you can reproduce this, please come to #ubuntu-mozillateam
> channel on irc.freenode.net and ping me (asac).
>
> Thanks,
> - Alexander
>
> --
> Network manager crash with
Tim, if you can reproduce this, please come to #ubuntu-mozillateam
channel on irc.freenode.net and ping me (asac).
Thanks,
- Alexander
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is th
Is there anything else I can do to help resolve this issue? Is my issue
different from that originally reported? This is quite annoying, as I
have to deal with network-manager randomly crashing on a regular
basis...
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You re
I just had a crash occur with the newly-updated packages from the PPA.
After the crash, nm-applet continues to run, but reports "no network
devices found". This just occured out of the blue - I wasn't
associated with any networks and didn't suspend-to-RAM, log out, or
anything of that sort.
I ha
I just installed it, and will keep you updated as to whether the problem
comes back or disappears...
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
pleae test the 0.6.5-0ubuntu16~ppa1 package from my ppa:
http://ppa.launchpad.net/asac/ubuntu/pool/main/n/network-manager/
Thanks,
- Alexander
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bug
Since the patch, I am noticing that while NetworkManager doesn't seem to
disappear from the system tray spontaneously as before, it does become
non-operational (i.e. the nm-applet says "No network Devices have been
found"). Thus, if the problem I'm experiencing is indeed a duplicate of
this bug (w
network-manager (0.6.5-0ubuntu15) gutsy; urgency=low
* debian/patches/41z_lp138217_use_timeout_to_schedule_activation.patch,series:
don't use idle_source to schedule activation, but rest a bit by using a
timeout_source with 250ms delay (LP: #138217).
* debian/network-manager.postinst:
network-manager (0.6.5-0ubuntu15) gutsy; urgency=low
* debian/patches/41z_lp138217_use_timeout_to_schedule_activation.patch,series:
don't use idle_source to schedule activation, but rest a bit by using a
timeout_source with 250ms delay (LP: #138217).
* debian/network-manager.postinst:
It seems like my issue intermittently occurs - and occurs most when I'm
resuming from suspend. I'm not connecting to any wireless networks when
it happens, though there are many in range.
Could we possibly restart NetworkManager on resume from suspend? It
seems that this would help somewhat in g
** Attachment added: "Output of gdb 'thread apply all bt full'"
http://launchpadlibrarian.net/9678548/nm-backtrace.txt
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Committed
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
any findings?
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listi
** Attachment added: "proposed patch that explicitly cancels scans in
supplicant cleanup"
http://launchpadlibrarian.net/9671678/41w_lp145683_cancel_scan_in_supplicant_cleanup.patch
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification be
** Attachment added: "Output of debugging NetworkManager with bt full"
http://launchpadlibrarian.net/9544175/nm-crash3.txt
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug cont
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Alexander Sack (asac)
Status: New => Confirmed
Target: None => ubuntu-7.10-rc
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
Network manager cr
** Changed in: network-manager (Ubuntu)
Sourcepackagename: None => network-manager
--
Network manager crash with WPA
https://bugs.launchpad.net/bugs/145683
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing lis
66 matches
Mail list logo
