On 17/3/2008, "Michael Biebl" <[EMAIL PROTECTED]> wrote: >Adrian Davey wrote: >> Output of NetworkManager --no-daemon and nm-tool as requested, >> >> NetworkManager: <info> starting... >> NetworkManager: <info> New VPN service 'openvpn' >> (org.freedesktop.NetworkManager.openvpn). > >> Start) started... >> NetworkManager: <info> Updating VPN Connections... >> process 23273: arguments to dbus_message_get_args() were incorrect, >> assertion "(error) == NULL || !dbus_error_is_set ((error))" failed in >> file dbus-message.c line 1667. >> This is normally a bug in some application using the D-Bus library. > > >I can't reproduce this problem. NM is running just fine with the newer glib. >It seems to crash when tries to update the vpn connections. Could you >try to uninstall network-manager-openvpn* and test with a fresh account >without any vpn configuration? > >Cheers, >Michael > > >-- >Why is it that all of the instruments seeking intelligent life in the >universe are pointed away from Earth? >
I have removed and purged network-manager-openvpn*, created a fresh account and rerun as asked, NetworkManager: <info> starting... NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch NetworkManager: <info> wlan0: Device is fully-supported using driver 'iwl4965'. NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. NetworkManager: <info> Now managing wireless (802.11) device 'wlan0'. NetworkManager: <info> Deactivating device wlan0. NetworkManager: <info> eth0: Device is fully-supported using driver 'e1000'. NetworkManager: <info> nm_device_init(): waiting for device's worker thread to start NetworkManager: <info> nm_device_init(): device's worker thread started, continuing. NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: <info> Deactivating device eth0. NetworkManager: <info> Will activate wired connection 'eth0' because it now has a link. NetworkManager: <info> Updating allowed wireless network lists. NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'. NetworkManager: <info> Will activate connection 'eth0'. NetworkManager: <info> Device eth0 activation scheduled... NetworkManager: <info> Activation (eth0) started... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started... NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting... NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete. NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started... NetworkManager: <info> Updating VPN Connections... process 26217: arguments to dbus_message_get_args() were incorrect, assertion "(error) == NULL || !dbus_error_is_set ((error))" failed in file dbus-message.c line 1667. This is normally a bug in some application using the D-Bus library. NetworkManager: <info> Error getting killswitch power arguments: - NetworkManager: <info> Wireless now enabled by radio killswitch eventually killed and again with nm-tool, NetworkManager Tool get_nm_state(): didn't get a reply from NetworkManager. NetworkManager appears not to be running (could not get its state). Regards, Adrian
