A patch to fix the crash is here: https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6
If we fail to get cairo fixed for any reason, it's probably possible to do a workaround/fix in ubiquity. But I think there are now multiple reasons to fix cairo as first preference. ** Bug watch added: freedesktop.org Bugzilla #98883 https://bugs.freedesktop.org/show_bug.cgi?id=98883 ** Also affects: cairo via https://bugs.freedesktop.org/show_bug.cgi?id=98883 Importance: Unknown Status: Unknown ** Changed in: ubiquity (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => Andrea Azzarone (azzar1) ** Changed in: ubiquity (Ubuntu Bionic) Assignee: Daniel van Vugt (vanvugt) => Andrea Azzarone (azzar1) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
