This should still have an open bug task. Tentatively assigning to ubuntu-sdk-libs, but of course that's too broad.
Suggestions how to continue debugging: * Bisect http://people.canonical.com/~lzemczak/landing- team/96.commitlog and see which new component actually introduced this regression and then assing to that, and possibly revert * This assertion: process 7262: arguments to dbus_connection_close() were incorrect, assertion "connection->generation == _dbus_current_generation" failed in file ../../dbus/dbus-connection.c line 2890. seems to be the best hint we have at the moment, and it's consistent with having a bus connection which is still registered (dbus-monitor doesn't show it as closed), but already dead as the application tried to close it in an invalid way. This is coming from libdbus-1-3, so it's not anything using gdbus or qdbus. Suggesting to add a breakpoint there and when the assertion hits see where/what in the stack tries to close that connection. ** Also affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-touch-meta (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1334676 Title: Applications have a dead open dbus connection (since image #96) To manage notifications about this bug go to: https://bugs.launchpad.net/autopilot/+bug/1334676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
