Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Topolino
    replied
    Originally posted by MrCooper View Post
    Canonical must have been aware of this, or it raises questions about why they weren't.
    Canonical mutter developers were definitely aware. Probably even happy about it.

    The policy change came from the x team. Specifically from Chris Halse Rogers (Mir author). Apparently he is not over Mir yet.

    Leave a comment:


  • Topolino
    replied
    Originally posted by F.Ultra View Post

    That it was on the road-map doesn't change anything, GNOME moved away from how point releases was before.
    x.1 releases had new features before as well. This is just another example of Ubuntu getting stuck on old kernels and protocols. They are aware and actually changed policy. They are probably also going to revert the SRU decision as well.

    Leave a comment:


  • Melcar
    replied
    Well at least it did not force install snap and remove my deb packages this time. I'm beginning to think that only LTS releases do that.

    Leave a comment:


  • darkdragon-001
    replied
    After several years of seamless updates, this time I had two problems:
    1. Docker failed to start because containerd config now requires full URL plugin names
    2. Flatpak startup is very very slow from the UI (many minutes): https://github.com/flatpak/flatpak/issues/5968

    Leave a comment:


  • F.Ultra
    replied
    Originally posted by MrCooper View Post



    The linux-drm-syncobj-v1 Wayland protocol support landed in mutter 46.1, not 46.2.

    It's a well-known fact that mutter had been branching only after the .1 release (at least since 3.2 in 2011), and that it was thus possible in principle for new features to land in .1. Canonical must have been aware of this, or it raises questions about why they weren't.

    That said, mutter has already branched after the 47.0 release, so 47.1 won't have any new features.


    I believe Malsabku's point was that the linux-drm-syncobj-v1 Wayland protocol support is patched out of those packages, which means nvidia driver users still get to enjoy all the glitches.

    In summary, this was a tempest in a teapot.
    47 is completely out of context since we are talking about 24.04LTS which was released before 47 was a thing and since 24.04 is stable it cannot change from 46 to 47.

    Leave a comment:


  • MrCooper
    replied
    Originally posted by Malsabku View Post

    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.
    Originally posted by F.Ultra View Post

    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.
    The linux-drm-syncobj-v1 Wayland protocol support landed in mutter 46.1, not 46.2.

    It's a well-known fact that mutter had been branching only after the .1 release (at least since 3.2 in 2011), and that it was thus possible in principle for new features to land in .1. Canonical must have been aware of this, or it raises questions about why they weren't.

    That said, mutter has already branched after the 47.0 release, so 47.1 won't have any new features.

    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:
    I believe Malsabku's point was that the linux-drm-syncobj-v1 Wayland protocol support is patched out of those packages, which means nvidia driver users still get to enjoy all the glitches.

    In summary, this was a tempest in a teapot.

    Leave a comment:


  • Espionage724
    replied
    Originally posted by andre30correia View Post

    vmware and virtualbox this are working very bad even in windows guest better to use kvm or hyper v
    I was trying to get a game's performance good through a VM; the D3D12 driver didn't perform well (afaik that's what hyperv does), but VMware performed notably better with 3D graphics in W7, W10, and Ubuntu guests vs VirtualBox.

    I found that Lubuntu 24.10 (UEFI guest), oibaf PPA, Liquorix kernel, VMware Workstation Pro 17, and Windows 10 host, with VMware with vsync disabled and Mesa/gfx env tweaks on Lubuntu got the best OpenGL performance.

    Leave a comment:


  • andre30correia
    replied
    Originally posted by Espionage724 View Post
    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.
    vmware and virtualbox this are working very bad even in windows guest better to use kvm or hyper v

    Leave a comment:


  • abu_shawarib
    replied
    Originally posted by F.Ultra View Post

    Since point releases of GNOME can include regressions and new functionality ...
    No. There's still a feature freeze, and any exceptions must be approved by the release team. See https://release.gnome.org/calendar/

    Leave a comment:


  • Rovano
    replied
    Originally posted by Espionage724 View Post
    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.
    And why you're amazed. It's a common thing that it is annoying in VM. Everything.
    After a few years, I tried Virtualbox with something and I was very unpleasantly surprised.​

    Leave a comment:

Working...
X