Ubuntu 24.10 Now Available With Linux 6.11, GCC 14 & Other Upgrades

[Espionage724]

So Ubuntu 24.10 amd64 image failed horribly under VMware Workstation Pro 17 (17.6.0 build-24238078); are you kidding me? I'm trying to test a game and wanted a Linux guest, figured Ubuntu's been safe, and figured why not 24.10. The installer had stuttering audio, I clicked through two interfaces, and got multiple failure messages (reported em, since either apparently nobody else tested this, or didn't care about fixing it).



Spending some additional time now going for 24.04.1 which I'm expecting to work, but I'm definitely surprised! I gave it 6GB RAM and 4 CPU cores (i5-8400H) but mostly defaults.

And if that last line of snap implies this is at all anything unique to snap, I'll have more questions

Edit: 24.04.1 had stuttery audio also at the installer, but install finished fine and post-install looks good so far!

24.04.1 is graphically-busted on VirtualBox (can't even see the flickering Initial Set-up window) compared to VMware Workstation Xorg and Wayland. I'm impressed this is a thing with two popular VMs.

[F.Ultra]

This feature was on the 46 roadmap since 6th oct 2023. The Canonical developers were fully aware of this. No complaints or requests to move to 47. Actual implementation was moved to 46.1 because a newer wayland-protocols had to be available in distributions and CI.

Ubuntu 24.04 only got in trouble because they didn't move to a newer wayland-protocols soon enough.

That it was on the road-map doesn't change anything, GNOME moved away from how point releases was before. Move to 47 wasn't an option since the import freeze was on 2024-02-29 so the only other option than going with 46.0 would have been to keep on using 45 and I think that would have generated far more cries from users.

[Topolino]

The problem is that GNOME broke the "point releases is only bug fixes" release schedule that every other open source project follows.

This feature was on the 46 roadmap since 6th oct 2023. The Canonical developers were fully aware of this. No complaints or requests to move to 47. Actual implementation was moved to 46.1 because a newer wayland-protocols had to be available in distributions and CI.

Ubuntu 24.04 only got in trouble because they didn't move to a newer wayland-protocols soon enough.

[Rovano]

Most packages in the GNOME 46 stack in Ubuntu 24.04 LTS are outdated.

Let's take a look
Upstream version / Ubuntu 24.04 LTS version / Snap version

evince 46.3 / 46.0 / 45.0
gnome-boxes 46.1 / 46.0 / 45.0
epiphany 46.4 / 46.0 / 46.2
mutter 46.5 / 46.2
gnome-terminal 3.52.2 / 3.52.0
gnome-shell 46.5 / 46.0
etc...

gnome-calendar is still 44.1 in the snap version ( https://snapcraft.io/gnome-calendar )


Fedora was able to upgrade to MATE 1.28 with Fedora 40, over 6 months ago. So this can't be an argument.


Please don't flame.

Well, the only one who is trolling here is you. You wrote completely false information that was very easy to verify. And I also refuted them.


And then you came up with others again, so that you would still be right, but you actually shot yourself in the foot.

You forgot that versions do not correlate with patches that Ubuntu contains.


Also, study what are official and what are community projects at Canonical.


Every knowledgeable person knows that, for example. Fedora or OpenSuse TW is a bleeding edge by nature. And LTS on Ubuntu is simply LTS.

Ubuntu is always upstream, so they decided it. At least you can choose what to install and where and that's what it's about.


And you also forgot that there are people who don't necessarily have to undergo new bugs in the kernel or other software, lose data, etc.
We all have a choice.

It is also unfortunate that Fedora does not yet have some things upstream. The user needs to do it himself.

Please, don't troll are your words you don't follow.

[szymon_g]

can it use the TPM2.0 by default like Suse does (ie with no further configuration)? I know the last lts was supposed to have it but it wasn't there. if ubuntu supports that, will kubuntu do it as well?

does is support BTRFS in the installer? what's about easy rolling to the older snapshots from grub?

[F.Ultra]

But this is an inconsistent behaviour. All these point releases dont have new features, while mutter 46.2 had this nvidia thing. And its already in noble, although disabled.

The problem is that GNOME broke the "point releases is only bug fixes" release schedule that every other open source project follows. It's not also possible to vet these releases for a stable distro like Ubuntu because they will always contain both fixes and new functionality meaning that you have to isolate the fixes and apply them as backports, aka you have to perform actual software development instead of distro maintainment.

mutter 46.2 was such a release that they after deliberation decided to include in noble due to the fix for nvidia and it is not disabled, I got it in 24.04 by default:

f.ultra@Sineya:~$ apt-cache policy mutter-common
mutter-common:
  Installerad: 46.2-1ubuntu0.24.04.2
  Kandidat:    46.2-1ubuntu0.24.04.2
  Versionstabell:
     46.2-1ubuntu0.24.04.3 100
        100 http://se.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        100 http://se.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages
 *** 46.2-1ubuntu0.24.04.2 500
        500 http://se.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
        500 http://se.archive.ubuntu.com/ubuntu noble-updates/main i386 Packages
        100 /var/lib/dpkg/status
     46.0-1ubuntu9 500
        500 http://se.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        500 http://se.archive.ubuntu.com/ubuntu noble/main i386 Packages
f.ultra@Sineya:~$

[sarmad]

As usual Canonical also did a lot of packaging work on Debian. It's really great and far beyond "barely builds".

This is the kind of work that people often underestimate. It's one of the reasons why people think that Canonical doesn't contribute enough.

[Malsabku]

Since point releases of GNOME can include regressions and new functionality and not only bug fixes, Ubuntu have since some time ago stopped to automatically update the point releases and they are now only added on a case by case basis.

But this is an inconsistent behaviour. All these point releases dont have new features, while mutter 46.2 had this nvidia thing. And its already in noble, although disabled.

[F.Ultra]

Most packages in the GNOME 46 stack in Ubuntu 24.04 LTS are outdated.

Let's take a look
Upstream version / Ubuntu 24.04 LTS version / Snap version

evince 46.3 / 46.0 / 45.0
gnome-boxes 46.1 / 46.0 / 45.0
epiphany 46.4 / 46.0 / 46.2
mutter 46.5 / 46.2
gnome-terminal 3.52.2 / 3.52.0
gnome-shell 46.5 / 46.0
etc...

gnome-calendar is still 44.1 in the snap version ( https://snapcraft.io/gnome-calendar )


Fedora was able to upgrade to MATE 1.28 with Fedora 40, over 6 months ago. So this can't be an argument.


Please don't flame.

Since point releases of GNOME can include regressions and new functionality and not only bug fixes, Ubuntu have since some time ago stopped to automatically update the point releases and they are now only added on a case by case basis.

[Malsabku]

ad GNOME46.0 or Calender 44.1
is something wrong in your OS. Here is 46.1.
https://launchpad.net/ubuntu/+source/gnome-calendar

Most packages in the GNOME 46 stack in Ubuntu 24.04 LTS are outdated.

Let's take a look
Upstream version / Ubuntu 24.04 LTS version / Snap version

evince 46.3 / 46.0 / 45.0
gnome-boxes 46.1 / 46.0 / 45.0
epiphany 46.4 / 46.0 / 46.2
mutter 46.5 / 46.2
gnome-terminal 3.52.2 / 3.52.0
gnome-shell 46.5 / 46.0
etc...

gnome-calendar is still 44.1 in the snap version ( https://snapcraft.io/gnome-calendar )

I have prepared packaging for MATE Desktop 1.28, along with the associated components but encountered some bugs and regressions 🐞 I wasn’t able to get things to a standard I’m happy to ship be default, so it is tried and true MATE 1.26.2 one last time 🪨

Fedora was able to upgrade to MATE 1.28 with Fedora 40, over 6 months ago. So this can't be an argument.

Please, next time send your questions to Google.com. Thx.

Please don't flame.