[Bug 227819] Re: New networkmanager null assert in Hardy

2012-10-30 Thread Thomas Hood
** Changed in: network-manager (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/227819 Title: New networkmanager null assert in Hardy To manage

[Bug 227819] Re: New networkmanager null assert in Hardy

2010-09-16 Thread Bug Watch Updater
** 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 Desktop Bugs,

[Bug 227819] Re: New networkmanager null assert in Hardy

2009-12-05 Thread Marc MERLIN
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

[Bug 227819] Re: New networkmanager null assert in Hardy

2009-01-20 Thread Magnus Wissler
*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

[Bug 227819] Re: New networkmanager null assert in Hardy

2009-01-20 Thread Marc MERLIN
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

[Bug 227819] Re: New networkmanager null assert in Hardy

2008-09-25 Thread Davias
Same problem: NetworkManager: info 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