just updated on 14 Oct. this included a kernel update to 2.6.27-7. the
problem is gone. all is working now.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
NetworkManager crashed with SIGSEGV in dbus_connection_unregister_object_path()
https://bugs.launchpad.
This is still present in 8.10 beta
--
NetworkManager crashed with SIGSEGV in dbus_connection_unregister_object_path()
https://bugs.launchpad.net/bugs/261808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
I have done more testing and have found the following:
1. Tested live CD on different machine - every thing works as expected.
2. Put a 3com net card in the problem machine - everything works as
expected.
This bug report started as a follow on bug from 256919. the fix to that one
was to upgrade to
Two other pieces of information.
This is also present when running alpha6 live cd.
If I boot with the net cable unplugged there are no repeating
"nm_dbus_manager_start_service()" messaged until the net cable is plugged
in, after plug in they start. It appears that it gets an ip address then
drops i
yep its still there. just did the update and reboot and still have to
restart network manager. see attached syslog. note there are several
restarts in there. look for the last one.
On Mon, Sep 22, 2008 at 6:19 PM, Alexander Sack <[EMAIL PROTECTED]> wrote:
> can you still reproduce this issue with
can you still reproduce this issue with
0.7~~svn20080908t183521+eni0-0ubuntu3 ?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
NetworkManager crashed with SIGSEGV in dbus_connection_unregister_object_path()
https://bugs.launchpad.net/bugs/261808
You received this bug
This happened for me while testing some switches. I set a server on one
port and let my laptop do "ping -f SERVER_IP", while moving the network
cable from port to port on the switch. After six or seven different
ports, it seems NetworkManager became unresponsive - the process was
running (as seen w
I have had this problem as well. Ironically, you "have" to send a
bugreport using a nonexistent network connection (unless you do what I
did, which is kill nm-applet and manually restart the NetworkManager
daemon).
--
NetworkManager crashed with SIGSEGV in dbus_connection_unregister_object_path()
** Visibility changed to: Public
--
NetworkManager crashed with SIGSEGV in dbus_connection_unregister_object_path()
https://bugs.launchpad.net/bugs/261808
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
