Comment 10 for bug 85113

So it gets a SIGTRAP in

        if (!nm_data->dbus_connection)
        {
                nm_error ("nm_dbus_init() failed, exiting. "
                          "Either dbus is not running, or the "
                          "NetworkManager dbus security policy "
                          "was not loaded.");
                exit (EXIT_FAILURE); <== RIGHT HERE
        }

n-m's nm_error() function attaches gdb onto the process to get a backtrace for the log, that's where the SIGTRAP comes from. So the real cause of this is that dbus is not running properly.

Can you guys please upgrade to the latest Feisty? Is this only an apport inconvenience, or does n-m really not work for you?