** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/227819
Title:
New networkmanager null assert in Hardy
To manage notifica
** Changed in: network-manager
Status: Confirmed => Won't Fix
** Changed in: network-manager
Importance: Unknown => Low
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As an update, network-manager now finally works again in karmic, no more of
those various random crashes and non handling of my network interfaces.
Documentation is still poor, but at least it works.
So, after around 2 years in being broken in various ways in each release after
dapper, it seems
My recommendation at this point is apt-get remove networkmanager and try wicd
or just nothing, it's become even worse in intrepid:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/303476
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received
*bump* :-)
Second the previous comment about traffic being relevant; I recently
clean-installed 8.10 (with network-manager) on an old box. Sure enough,
as soon as I started transferring larger amounts of data across the
network (be it streaming or copying large files), network-manager thinks
the n
Same problem:
NetworkManager: SWITCH: terminating current connection 'eth0'
because it's no longer valid...
And it's happening every minute! This because I looked in the logs after
I started having serious problems.
In fact as soon as I start to increase the loads on the LAN eth0 crash and th
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Changed in: network-manager
Status: New => Confirmed
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
marking as triaged. Reasoning is sound.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Triaged
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: network-manager
Status: Unknown => New
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
** Bug watch added: GNOME Bug Tracker #548139
http://bugzilla.gnome.org/show_bug.cgi?id=548139
** Also affects: network-manager via
http://bugzilla.gnome.org/show_bug.cgi?id=548139
Importance: Unknown
Status: Unknown
--
New networkmanager null assert in Hardy
https://bugs.launchp
I will report this bug upstream even though the network seems to be
fully functional. But there should not be "Null asserts" without a
reason.
** Changed in: network-manager (Ubuntu)
Assignee: Andreas Moog (andreas-moog) => (unassigned)
Status: Incomplete => Confirmed
--
New networkm
from what I can tell, the networking pieces are working, unless I'm missing a
side function that networkmanager was supposed to provide before it finds its
null assert.
Honestly, I didn't look at the code, I'm hoping the programmer didn't put NULL
assert statements in there if they aren't import
So basically your only problem is the message appearing? Or do you have
an issue with using your network?
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
No errors or problems.
Aug 17 07:21:50 gandalf kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.
Aug 17 07:21:50 gandalf kernel: tg3: eth0: Flow control is on for TX and on for
RX.
Aug 17 07:21:50 gandalf kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes
ready
Aug 17 07:21:50 gandalf Ne
And what does the syslog look like when you plug the cable back in?
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Still happening, yes
ii network-manage 0.6.6-0ubuntu5 network management framework daemon
--
New networkmanager null assert in Hardy
https://bugs.launchpad.net/bugs/227819
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please answer these questions:
* What version of Network-manager are you running?
* Does this still happen to you?
Thanks in Advance.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Andreas
I'm getting the exact same issue:
Jun 14 22:58:48 gezim-laptop kernel: [ 1641.898529] tg3: eth0: Link is down.
Jun 14 22:58:48 gezim-laptop NetworkManager: SWITCH: terminating
current connection 'eth0' because it's no longer valid.
Jun 14 22:58:48 gezim-laptop NetworkManager: Deactivating de
19 matches
Mail list logo
