** Changed in: network-manager
Importance: Unknown => Critical
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
hmm interesting- the crash comes everytime i logon the system - 9.04 -
and network manager has the same issue in versions before that first
time connect to hidden wpa(2) wlan is not possible but second time works
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
ht
** Changed in: network-manager
Status: New => Fix Released
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Just wanted to comment that I haven't seen this problem recently on my
system, so *knock-on-wood* the update seems to have fixed it for me.
Thank you.
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug noti
I'm sorry about the messages in quick succession... Should have read
"...but after upgrading the packages and rebooting something
crashes"
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification
New version compiles fine using apt-build on my system, something
crashes when I select a network and I'm unable to establish a connection
using iwconfig and dhclient like I am usually able to when other methods
fail.
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request(
This bug was fixed in the package network-manager -
0.7~~svn20080908t183521+eni0-0ubuntu1
---
network-manager (0.7~~svn20080908t183521+eni0-0ubuntu1) intrepid; urgency=low
[ Alexander Sack <[EMAIL PROTECTED]> ]
* new upstream snapshot (Mon 2008-09-08 18:35:21 rev3504)
* merge im
Executing "Edit Connections" also triggered the same error message on
exit (after doing nothing).
After manually copying the directory (and contents) /lib/firmware/b43
from the previous install of Hardy (Ubuntu 8.04) into the same place in
the Intrepid install file system, I now can left click on
After installing Intrepid on a Dell Inspiron 1521 with the Broadcom 4312
wireless, and updating to the current repositories (as of ~22:00 GMT),
NetworkManager still crashed as described by Allberto Emiliani.
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://
NetworkManager crashed as soon as I enabled the firmware for my wireless
Broadcom 4311. I mean, I just checked "enable" in the popup window and
closed it.
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug
I had both b43 and ndiswrapper loading (accidentally) after my upgrade
to intrepid and 2.6.27. The purpose of the upgrade was to test the b43
driver on the 2.6.27 kernel (as requested by one of the automated
launchpad systems). Crash occurred shortly after running "modprobe -r
ndiswrapper" to rem
Not fixed with this patch. I rebuilt the package with this patch
included, but I still have crashes.
I resumed from suspend, NM does not reconnect to my AP, I removed the
device, and plugged it back in-> crash.
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
http
Removing and replacing the device causes the crash.
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Changed in: network-manager
Status: Unknown => New
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
patch forwarded upstream.
** Bug watch added: GNOME Bug Tracker #549401
http://bugzilla.gnome.org/show_bug.cgi?id=549401
** Also affects: network-manager via
http://bugzilla.gnome.org/show_bug.cgi?id=549401
Importance: Unknown
Status: Unknown
--
MASTER NetworkManager 0.7 crashed
the attached patch (committed as rev 2865/2866) appears to fix the crash
here for both: unplug and unload module.
** Changed in: network-manager (Ubuntu Intrepid)
Status: Triaged => Fix Committed
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs
** Attachment added: "patch that got checked-in"
http://launchpadlibrarian.net/17080649/80_lp259503_access_to_freed_device_struct.patch
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification b
What appears to happen here is that NM uses a scheduled callback to
perform actions on device objects. however, those device objects are
neither refcounted nor are the callbacks cancelled when the device goes
down and we end up accessing freed memory in the callback.
--
MASTER NetworkManager 0.7
Targeted for Intrepid as this is a regression
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I can confirm that removing and replacing the device causes the crash.
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see a similar crash which is reliably reproducible on my system if a
network interface disappears (e.g. unloading my wireless module).
--
MASTER NetworkManager 0.7 crashed with SIGSEGV in nm_device_get_act_request()
https://bugs.launchpad.net/bugs/259503
You received this bug notification becau
I just tried unplugging my usb wireless adapter and plugging it in
again, and it did cause nm-applet to disappear, but I received no
notification of a crash(does it notify you if you are on a non
administrative desktop or if it has already been reported?). I did get
some messages in daemon.log(atta
I believe this is the same bug I'm seeing.
I'm using an external USB wireless card. I share this between two
notebooks (both have unsupported internal cards), so I'm constantly
pulling it from one notebook and putting it in the other.
Under Hardy, this is no problem. Pull card out, plug it back
23 matches
Mail list logo
