Crash after terminal step

The host that was running Cubic that resulted in this crash was running on 18.04.03. I have now just tried running the same steps on a 19.10.04 host, and Cubic did not crash as before on the transition from the Terminal page. Perhaps it's a requirement that the host run the same version as the ISO to be generated...

There is no requirement that the versions match.

Please be sure you have free disk space available! Usually, you need a at least 25GB to customize an ISO. I've seen this issue in the past where Cubic is run in a VM without enough virtual disk space.

If you get the chance, please try the Development version, 2020.01-213, and let me know if you experience the same bug, with the exact same scenario you tested earlier.

    # Uninstall Release Version
    $ sudo apt autoremove --purge cubic
    $ sudo apt-add-repository --remove ppa:cubic-wizard/release

    # Install Development Version
    $ sudo apt-add-repository ppa:cubic-wizard/development
    $ sudo apt update
    $ sudo apt install cubic

I'll also try the 18.04.03 and 19.10.04 combination to see what's going on. If I need additional information from you, I'll let you know.

I was able to reproduce this bug:
- Running Cubic on 18.04.3 Ubuntu Host
- Customizing 19.10 Ubuntu

Regolith Linux,

This is the same problem as Issue #1 of Bug #1860345.

The fix for Bug #1860345 is currently available in the Development branch.

If you like, you can test this fix, and let me know if it works for you:

    $ sudo apt autoremove --purge cubic
    $ sudo apt-add-repository --remove ppa://cubic-wizard/release

    $ sudo apt-add-repository ppa://cubic-wizard/development
    $ sudo apt install cubic

Otherwise, if you want to wait, I will be promoting the fix to the Release branch before the end of this week.

Thank you for the quick response! I am unblocked as I'm able to generate my 19.10 ISO from another machine, but look forward to the fix for future releases.

As an aside, it would be nice if there was a global exception handler tied to the UI. The nature of the wizard is that it can take a long time for things to happen, and if there is a background crash, I end up not realizing it and just waiting at the window for something to happen. Ideally the crash would immediately be surfaced in the dialog so that the crash was obvious. I do not know how feasible this is in python+gtk but thought I'd mention it. Thanks again for your efforts!

This is an excellent suggestion, and my plan is to add such a feature in a new version of Cubic.

There are some complicities in the user interface, because Cubic is a multi threaded application. To the user, the application seems simple and linear (click next or back buttons), but managing multiple threads to make things seem simple is indeed a challenge.

Cubic’s current “wizard” framework was developed when there were less features, an the intention was that errors would be shown immediately under the progress bars (if possible). As cubic evolved, som processing work needed to be done “between” the pages.

The error you experienced is an example of this, where Cubic attempts to figure out the right kernels to display while transitioning “between” the Terminal page and the Options page.

I am working on a new framework that would allow more easily adding additional pages. This way, we can add a page to show the processing progress as we calculate the kernels, the list of manifest packages, the boot Giles, the preseeded filed, etc.

With the ability to add new pages more easily to the UI, we can also insert a general error page, to make it easier for the user to know when things didn’t work out.

Finally, I’m very interested in errors that you encounter, in addition to this one. So please do report them!

I will surely continue to report any issues I find. Your future plans sound great, and I hope the development goes smoothly!

Fix released to Development branch 214.
Fix released to Release branch 62.