Mathieu Trudel-Lapierre pointed out that if the user has both an ethernet and 3G connection, it will correctly use the ethernet interface.
With that, I have the following branch which implements the connectivity check on top of Network Manager, reusing some code we previously had for a less comprehensive check: http://bazaar.launchpad.net/~ev/whoopsie-daisy/3g-check/revision/330?compare_revid=326 Do note that it fakes out a ConsoleKit session by writing /var/run/console/whoopsie, as NetworkManager has the at_console flag set in org.freedesktop.NetworkManager.conf. While it has code to do so, it cannot delete this file at exit, as the directory is root owned. I think this is okay. ConsoleKit removes the entire contents of /var/run/console on exit anyway and whoopsie is long running. Of course if ConsoleKit died, whoopsie would lose the ability to get connectivity updates. However, I'm pretty sure this case is not well handled anywhere (killing console-kit-daemon breaks NetworkManager on my system). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/964508 Title: whoopsie uploads crash reports, including core dumps, when on a 3G connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-daisy/+bug/964508/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
