The reason for the failure in g_alloc is because the osmo config.xml is rewritten with invalid information. In this case the <window_size_x> and <window_size_y> have huge numbers causing the over memory allocation for the window. Appears there are many fields in this file that have suspect values.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1298013 Title: Unable to start Osmo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/osmo/+bug/1298013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs