[dapper] Doesn't notice new network devices

Please do the following before loading the driver...

$ sudo -s
# /etc/dbus-1/event.d/25NetworkManager stop
# NetworkManager --no-daemon 2>nm.log

Load the driver, and then provide the nm.log file

On Wed, May 10, 2006 at 08:41:35PM -0000, Scott James Remnant wrote:
> Please do the following before loading the driver...
>
> $ sudo -s
> # /etc/dbus-1/event.d/25NetworkManager stop
> # NetworkManager --no-daemon 2>nm.log
>
> Load the driver, and then provide the nm.log file

NetworkManager: <information> starting...
NetworkManager: <WARNING> main (): nm_data_new: Setting up dbus filter
NetworkManager: <information> Updating allowed wireless network lists.
NetworkManager: <WARNING> nm_signal_handler (): Caught signal 2, shutting down normally.
NetworkManager: <information> Caught terminiation signal
NetworkManager: <debug info> [1147300596.762180] nm_print_open_socks (): Open Sockets List:
NetworkManager: <debug info> [1147300596.762382] nm_print_open_socks (): Open Sockets List Done.

I loaded the driver after the 3rd line.

dave...

--
David Schleef
Big Kitten LLC (http://www.bigkitten.com/) -- data acquisition on Linux

My nm.log gave this error log:

NetworkManager: <information> starting...
NetworkManager: <WARNING> nm_dbus_init (): nm_dbus_init() could not acquire the NetworkManager service as it is already taken (ret=3). Is the daemon already running?
NetworkManager: <ERROR> [1148936188.961252] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded.
NetworkManager: traceback:
NetworkManager: NetworkManager(main+0x3e3) [0x8066ea8]
NetworkManager: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7d0fea2]
NetworkManager: NetworkManager [0x8052d91]

Any ideas?

This seems to be similar to the bug I'm having.

/etc/dbus-1/event.d/25NetworkManager stop --> * Stopping NetworkManager daemon [ ok ]

NetworkManager --no-daemon 2>nm.log gives the following in nm.log
NetworkManager: <information> starting...
NetworkManager: <WARNING> nm_dbus_init (): nm_dbus_init() could not acquire the NetworkManager service as it is already taken (ret=3). Is the daemon already running?
NetworkManager: <ERROR> [1149278753.118654] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded.
NetworkManager: traceback:
NetworkManager: NetworkManager(main+0x3e3) [0x8066ea8]
NetworkManager: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd2) [0xb7c4dea2]
NetworkManager: NetworkManager [0x8052d91]

Wireless interface wlan0 is working; it's neither seen nor controlled by network-manager

It seems, that NetworkManager developer know where is the problem -
 Dan Williams (NetworkManager developer, points: 15) at 2006-07-10 15:40 UTC wrote (see comments in related gnome bug):
>
> <policy user="hal">
> <allow send_destination="org.freedesktop.NetworkManager"/>
> <allow send_interface="org.freedesktop.NetworkManager"/>
> </policy>
>
> It seems only Debian/Ubuntu need those bits; not entirely sure why but without those, Hal isn't allowed to talk to NetworkManager. Let me know if that works.

As I understand problem is in Ubuntu's HAL package, right ?

The changes and noted and rationalized upstream are in edgy.

This was patched in 0.6.3-2 in unstable, and therefore never merged into dapper.

The solution if you're having this problem is to upgrade to edgy!

Fixed in Edgy and Feisty.