| 2006-05-20 01:57:11 |
IFRFlyer |
bug |
|
|
added bug |
| 2006-12-12 21:26:59 |
Kees Cook |
None: status |
Unconfirmed |
Needs Info |
|
| 2006-12-12 21:26:59 |
Kees Cook |
None: statusexplanation |
|
Thanks for your report. Based on the path you list, it doesn't sound like you were running the Ubuntu network-manager. Can you confirm the problems with the stock network-manager? |
|
| 2007-01-23 12:56:43 |
Matt Zimmerman |
network-manager: status |
Needs Info |
Confirmed |
|
| 2007-01-23 12:56:43 |
Matt Zimmerman |
network-manager: importance |
Medium |
High |
|
| 2007-01-23 12:56:43 |
Matt Zimmerman |
network-manager: statusexplanation |
Thanks for your report. Based on the path you list, it doesn't sound like you were running the Ubuntu network-manager. Can you confirm the problems with the stock network-manager? |
This happens to me all the time with the stock NetworkManager in edgy and feisty. The cause seems to be:
Jan 23 04:51:13 localhost NetworkManager: <WARNING>^I nm_add_initial_devices (): could not find existing networking devices:
The maximum number of pending replies per connection has been reached
|
|
| 2007-01-23 12:57:16 |
Matt Zimmerman |
description |
Problem with NetworkManager, not nm-applet, but NetworkManager didn't appear in the package list - When suspending to RAM, NetworkManager shuts down connection prior to suspend. After the latest update, NetworkManger consistently crashes on resume from suspend, and gives the error "No network devices can be found" despite the device functioning perfectly. Killing
/usr/local/sbin/NetworkManager
required a -9 before it would die. Upon its death, running (as root) NetworkManager then restarting nm-applet worked to restart.
Note: the original reporter indicated the bug was in package 'nm-applet'; however, that package was not published in Ubuntu. |
Problem with NetworkManager, not nm-applet, but NetworkManager didn't appear in the package list - When suspending to RAM, NetworkManager shuts down connection prior to suspend. After the latest update, NetworkManger consistently crashes on resume from suspend, and gives the error "No network devices can be found" despite the device functioning perfectly. Killing
/usr/local/sbin/NetworkManager
required a -9 before it would die. Upon its death, running (as root) NetworkManager then restarting nm-applet worked to restart.
Note: the original reporter indicated the bug was in package 'nm-applet'; however, that package was not published in Ubuntu. |
|
| 2007-01-23 12:57:16 |
Matt Zimmerman |
title |
NetworkManager can't find interface on resume from Suspend after update 19 may |
NetworkManager can't find interface on resume from suspend |
|
| 2007-01-23 12:59:13 |
Matt Zimmerman |
description |
Problem with NetworkManager, not nm-applet, but NetworkManager didn't appear in the package list - When suspending to RAM, NetworkManager shuts down connection prior to suspend. After the latest update, NetworkManger consistently crashes on resume from suspend, and gives the error "No network devices can be found" despite the device functioning perfectly. Killing
/usr/local/sbin/NetworkManager
required a -9 before it would die. Upon its death, running (as root) NetworkManager then restarting nm-applet worked to restart.
Note: the original reporter indicated the bug was in package 'nm-applet'; however, that package was not published in Ubuntu. |
Often, after resuming from suspend, NetworkManager no longer recognizes any network interfaces. It logs the following messages when this happens:
Jan 23 04:51:13 localhost NetworkManager: <information>^IWaking up from sleep.
Jan 23 04:51:13 localhost NetworkManager: <WARNING>^I nm_add_initial_devices (): could not find existing networking devices:
The maximum number of pending replies per connection has been reached
|
|
| 2007-03-15 16:06:10 |
Scott James Remnant (Canonical) |
network-manager: assignee |
|
tfheen |
|
| 2007-03-15 16:06:10 |
Scott James Remnant (Canonical) |
network-manager: statusexplanation |
This happens to me all the time with the stock NetworkManager in edgy and feisty. The cause seems to be:
Jan 23 04:51:13 localhost NetworkManager: <WARNING>^I nm_add_initial_devices (): could not find existing networking devices:
The maximum number of pending replies per connection has been reached
|
|
|
| 2007-07-13 00:21:57 |
Serge |
bug |
|
|
added attachment 'network-log' (Terminal commands in relation) |
| 2007-09-28 07:52:19 |
Olivier Cortès |
bug |
|
|
added attachment 'dmesg' (Dmesg of the Dell Precision M4300.) |
| 2007-10-04 10:44:40 |
Alexander Sack |
network-manager: status |
Confirmed |
Fix Released |
|
| 2007-10-04 10:44:40 |
Alexander Sack |
network-manager: assignee |
tfheen |
asac |
|
| 2007-10-18 22:58:56 |
Leann Ogasawara |
linux-source-2.6.20: status |
New |
Invalid |
|
