After about 12 hours of various debugging attempts, I finally found the problem: /etc/network/interfaces contains an additional "up"-rule for activating Wake-On-LAN on eth0. This caused network-manager to ignore this device, so Sugar wasn't seeing any internet connection and didn't even try connecting to the Jabber server.
Background information:[1]: Sugar starts plugins for both link-local and server-based collaboration, but only ever uses one of them. The server-based one uses NetworkManager to wait for a valid IPv4 address and thus won't be activated if NetworkManager isn't handling the internet connection.
[2]:> Only devices that are *not* listed in /etc/network/interfaces or which have been configured "auto" and "dhcp" (with no other options) are managed by NM.
There doesn't seem to be any way to enable Wake-On-LAN via NetworkManager.
[3]: There's currently no way to let a interface be managed by NetworkManager (which seems to be required for it to be shown to Sugar) _and_ activate Wake-On-LAN via custom "up"-rule.
I can work around this by moving the ethtool line into rc.local (it's a hardwired interface, so no hotplugging), but it's rather ugly and really unexpected. Will file seperate bugs about it, though.
[1] http://wiki.laptop.org/go/Presence_Service#Active_connection [2] /usr/share/doc/network-manager/README.Debian (on lenny) [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508383 CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/
signature.asc
Description: Digital signature
