Anyone know if this guide still works for noble?

[tertitten74]

Hi, first, thanks a lot for this guide, I just have one simple question, anyone know if this still works on noble desktop?
I've been using cubic for my images so far, but unfortunately it works less than optimal for noble.

[Runa-Chin]

Hi, first, thanks a lot for this guide, I just have one simple question, anyone know if this still works on noble desktop? I've been using cubic for my images so far, but unfortunately it works less than optimal for noble.

This tutorial also last updates two years ago, but it still works. Even little complicated, you just need change it into Noble. I'd using this tutorial and change the value from Jammy into Noble.

[oldtime54]

I also have used this tutorial and had to change some settings in the build.sh, chroot._build.sh and my config.sh file.
It also uses the old installer and not the new flutter one. No snaps installed as I remove them in my config.sh file.

[Runa-Chin]

I also have used this tutorial and had to change some settings in the build.sh, chroot._build.sh and my config.sh file. It also uses the old installer and not the new flutter one. No snaps installed as I remove them in my config.sh file.

You had block an Snapd installation with APT rule look like what Linux Mint do ? And you know, Ubiquity are still good even now Ubuntu had no more cares and priority new installer than improve what the best thing ever they develop and make user satisfied. And I think this original repo are being olds and may incompatible with newest LTS version or incompatible with Ubuntu Devel (rolling version of Ubuntu).

What should we do ?

Copy/Clone this repo by importing into your GitHub or whatever Git platform you had use and make some changes. Don't forget to add credits from original repo and always check your own cloned repo.

[tba-devel]

Everything works fine until dpkg-reconfigure resolvconf which cannot be accomplished because this version uses systemd-resolved instead. Was anyone able to overcome this?

[oldtime54]

I had changed this in the chroot_build.sh file to fix that issue. I changed it to systemd-resolved and that fixes that.