flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.2K
active users

#Ubuntu2504Puffin

1 post1 participant1 post today

Upgrades to Ubuntu 25.04 Plucky Puffin are suspended

The Ubuntu release team have identified some of the issues that may affect all Ubuntu upgrades from the Oracular Oriole, which is a 20th year anniversary version of Ubuntu when it was unveiled back in 2004, to the Plucky Puffin that was released a week ago. The following issues were discovered:

The release team have decided to halt all upgrades to the Plucky Puffin while the following critical issues mentioned above are being investigated. Once they are fixed, users can upgrade to Ubuntu 25.04 again. This is done as a safety measure to avoid people having to deal with critical bugs like these after the upgrade.

#2410 #2410Oracular #2410OracularOriole #2504 #news #Tech #Technology #Ubuntu #Ubuntu2410 #Ubuntu2410Oracular #Ubuntu2410OracularOriole #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update

Where is Ubuntu 25.04 RC?

The release candidate of the upcoming version of Ubuntu 25.04 Plucky Puffin was supposed to be released on April 10th, and we were excited to see the Ubuntu release team make the RC version of Ubuntu 25.04 go live. We haven’t seen any RC release or any official release notification in any of the official announcement channels, so the question is…

Where is Ubuntu 25.04 Plucky Puffin Release Candidate?

This release candidate didn’t make it to the official release server, so we are wondering why. The official release schedule for Plucky Puffin stated that the release candidate was supposed to be released on April 10th, and that the full freeze, as well as the language packs translation deadline, was supposed to happen. However, we didn’t have any news about the Plucky Puffin release, so the question is…

What’s going on with Ubuntu 25.04 Plucky Puffin?

We are asking you for your patience as the Ubuntu team is working on ensuring that the release candidate is released within this week.

#2504 #news #Plucky #PluckyPuffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update

Ubuntu 25.04 Plucky Puffin will enter Release Candidate on April 10th!

According to the Ubuntu 25.04 Plucky Puffin release schedule, this version should enter the release candidate stage. This means that, starting from tomorrow (April 10th), all images produced from that day to the final release date (April 17th) will be under the release candidate stage.

According to the official Ubuntu wiki, the release candidate is considered to be a stage that lasts one week that leads up to the final release, assuming that no release critical bugs are discovered before the final release. Such bugs in this stage, if discovered, may cause a delay in the release. The Ubuntu developers will use this week to shake out any critical bugs that may or may not exist.

In the same day as the release candidate starts getting rolled out, the final freeze starts, which is the most intensive freeze out of all the freezes that will cause all packages to go into a state where only the bug fixes are accepted prior to the release, which results in the final release being more stable than the release candidate. The exceptions are only applied when there are either security or release critical bugs, or under exceptional circumstances.

The language packs will also be finalized in the same day as the release candidate, which means that the text displayed in every application will be delivered as is. The finalized language packs will be released in the same day to ensure that users will be able to use this version of Ubuntu in their own native language.

Get ready for the release candidate of Ubuntu 25.04 Plucky Puffin!

#2504 #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update

Ubuntu 25.04 enters Documentation String and Kernel Feature Freeze

As we are only a week away from Ubuntu 25.04 Plucky Puffin beta version scheduled for the 27th of this month, there are now two freezes to be set in place:

The documentation string freeze causes all strings (that is, text to be displayed on the screen for documentation) to be finalized in preparation for the translation that is set to end on April 10th. However, there are cases where exceptions are made, such as major typos, but the translation team must get the latest strings to avoid inconsistencies.

As for the kernel feature freeze, it’s a deadline for any new-feature-related kernel changes. It’s a point where the kernel for the upcoming version of Ubuntu, such as Ubuntu 25.04 in this case, is feature-complete and is expected to only receive bug fixes.

As an aside, GNOME 48 is expected to land to Ubuntu 25.04 today.

#2504 #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update

Ubuntu 25.04 official wallpaper revealed

The wallpaper competition has recently ended with two winners for six categories, which are:

  • Mascot Theme – Artwork that prominently features the mascot for this release. For 25.04 that’s the Plucky Puffin.
  • Digital / Abstract – Artwork created using digital creative tools e.g. Blender, GIMP, Inkscape, Aesprite, etc.
  • Photography – High resolution image taken from a conventional or digital camera.

The below wallpapers were selected as winners:

Mascot ThemeDigital / AbstractPhotography

Now, the official Ubuntu 25.04 wallpaper has been made ahead of the final release according to this blog post. You can see the colored, the dark, the dimmed, and the light versions of the official Ubuntu mascot wallpaper below.

The official version of Ubuntu 25.04 Plucky Puffin will be released on April 17th, with the expected beta release on March 27th for users to test the version before production.

#2504 #news #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update #wallpaper

Ubuntu will improve ARM64 support

Ubuntu had conducted a very interesting test for the ARM64 processor architecture support on a Qualcomm Snapdragon X Elite machine during the development of Ubuntu 24.10. It was a huge success, seeing as the ARM64 laptops and desktops are being more popular in today’s computer stores, alongside the existing ARM64 machines.

As Ubuntu 25.04 Plucky Puffin gets closer to the stable release, the Ubuntu team is considering improving support for the ARM64 machines, especially those that use the Snapdragon X Elite processors. The ubuntu-x1e-settings meta-package, which is necessary for such computers, has been promoted to the main repository. At the same time, the qcom-firmware-extract package, which is necessary for Qualcomm machines and is a script that provides a way to extract Qualcomm firmware files from the Windows partition and to create a Debian package for a specific machine, has been uploaded to the universe repository. The script currently provides support for the following Qualcomm Snapdragon X Elite machines, with more machines to be added to the list:

  • Acer Swift 14 AI (SF14-11)
  • ASUS Vivobook S 15
  • Dell XPS 13 9345
  • HP Omnibook X 14
  • Lenovo ThinkPad T14s Gen 6
  • Lenovo Yoga Slim 7x
  • Microsoft Surface Laptop 7 (13.8 inch)
  • Samsung Galaxy Book4 Edge

The Linux kernel package and the Ubuntu installer will be updated to support such machines to make sure that they run Ubuntu without any problems. This is going to be done starting from 25.04 to make sure that the next LTS, which will be released in the next April, runs flawlessly on such machines.

Alongside that, the Ubuntu team plans to improve support for all ARM64 machines by distributing a single working Ubuntu ISO file for ARM64 systems and by eliminating device-specific installers to make installing Ubuntu on such systems easier than never before. This will be a single official Ubuntu image that works on all the platforms, be it an Ampere powered workstation, a Snapdragon X Elite laptop, an ARM64 server, or in a virtual machine on your Apple Silicon Mac.

The Raspberry Pi machines will also experience improved system compatibility by changing the camera stack to work with such machines. The new PiSP driver has been added to the camera stack to make sure that the Raspberry Pi machines be able to use the camera on Ubuntu, in addition to the rpicam-apps (userspace apps), picamera2 (Python API for camera), and their dependencies. This allows for a smooth migration from the original OS, which is Raspberry Pi OS.

However, the AI features for the official AI camera that uses the Sony IMX500 imaging sensor are not available in this version of Ubuntu due to licensing concerns, but the Ubuntu team will be working on it to resolve the licensing issues so that Raspberry Pi machines will be able to use the AI features for such cameras outside the original OS.

https://audiomack.com/aptivi/song/ubuntu-will-improve-arm64-support

#2504 #news #Plucky #PluckyPuffin #Puffin #Qualcomm #QualcommSnapdragon #QualcommSnapdragonX #QualcommSnapdragonXElite #Snapdragon #SnapdragonX #SnapdragonXElite #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update #X #XElite

Ubuntu will most likely revert the -O3 optimizations

The Ubuntu team was contemplating enabling the -O3 compiler optimization level for all packages on Ubuntu as a default optimization level. It was said to improve the performance of all the packages. It was one of the most significant changes that Ubuntu had witnessed in the early cycle of development of the Plucky Puffin version around October. The mailing list entry said:

* dpkg-buildflags defaults to -O3 instead of -O2. This might require changes in package builds. Please be aware that we already build with -O3 on ppc64el, so look for possible packaging adjustments.

We told you earlier in the article that the binary size for the packages would be bigger, and that there were some uncertainty about whether all packages would benefit from this level of optimization.

Benchmarking results for the packages that were built with the -O3 optimization level were kind of disappointing, because the Ubuntu team had discovered that:

  • overall system performance slightly declined, and
  • binary sizes increased.

However, they had seen that some workloads saw improvements when enabling this optimization level. Given the uncertainty that was posted in the same plan laid out in the mailing list, the Ubuntu team will give a detailed posting about the benchmarking results in the next few weeks.

As a result, the team has decided to revert the -O3 compiler optimization level for all the packages and revert to what was previously working, which was -O2. They are likely to revert the change soon to prevent problems when this version of Ubuntu gets released in April.

#O3 #2504 #news #Optimization #Plucky #PluckyPuffin #Puffin #Tech #Technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update

Ubuntu 25.04 Plucky Puffin includes libvirt 10.10.0

Ubuntu 25.04 Plucky Puffin is still in development with brand new features and new versions of software. One of the software that we’ll cover in this article is libvirt 10.10.0. In the release notes of this version of Ubuntu expected to unveil on April 17th, 2025, the release notes says that libvirt has been updated to 10.10.0. There are newer versions of libvirt, such as 11.0.0 and 11.1.0, but they don’t make their way to Ubuntu 25.04, and are expected to land on Ubuntu 25.10.

Since Ubuntu 24.10 Oracular Oriole, the following changes were made (copied from the release notes):

  • network: make networks with <forward mode='open'/> more useful.
    • It is now permissable to have a <forward mode='open'> network that has no IP address assigned to the host’s port of the bridge. This is the only way to create a libvirt network where guests are unreachable from the host (and vice versa) and also 0 firewall rules are added on the host.It is now also possible for a <forward mode='open'/> network to use the zone attribute of <bridge> to set the firewalld zone of the bridge interface (normally it would not be set, as is done with other forward modes).
  • qemu: zero block detection for non-shared-storage migration
    • Users can now request that all-zero blocks are not transferred when migrating non-shared disk data without actually enabling zero detection on the disk itself. This allows sparsifying images during migration where the source has no access to the allocation state of blocks at the cost of CPU overhead.This feature is available via the --migrate-disks-detect-zeroes option for virsh migrate or VIR_MIGRATE_PARAM_MIGRATE_DISKS_DETECT_ZEROES migration parameter. See the documentation for caveats.
  • qemu: internal snapshot improvements
    • The qemu internal snapshot handling code was updated to use modern commands which avoid the problems the old ones had, preventing use of internal snapshots on VMs with UEFI NVRAM. Internal snapshots of VMs using UEFI are now possible provided that the NVRAM is in qcow2 format.
  • qemu: add multi boot device support on s390x
    • For classical mainframe guests (i.e. LPAR or z/VM installations), you always have to explicitly specify the disk where you want to boot from (or “IPL” from, in s390x-speak – IPL means “Initial Program Load”).In the past QEMU only used the first device in the boot order to IPL from. With the new multi boot device support on s390x that is available with QEMU version 9.2 and newer, this limitation is lifted. If the IPL fails for the first device with the lowest boot index, the device with the second lowest boot index will be tried and so on until IPL is successful or there are no remaining boot devices to try.Limitation: The s390x BIOS will try to IPL up to 8 total devices, any number of which may be disks or network devices.
  • qemu: Add support for versioned CPU models
    • Updates to QEMU CPU models with -vN suffix can now be used in libvirt just like any other CPU model.
  • qemu: Automatically add IOMMU when needed
    • When domain of qemu or kvm type have more than 255 vCPUs, IOMMU with EIM mode is required. Starting with this release libvirt automatically adds one (or turns on the EIM mode if there’s IOMMU without it).
  • The Debian (and consequently the Ubuntu) libvirt package has been significantly redesigned. To quote its NEWS file:
    • All the various drivers and storage backends come in their own separate binary packages now, which makes it possible to install exactly as many or as few as desired.
    • The system-wide configuration for the libvirtd daemon is no longer shipped separately from the daemon itself, as was the case until now. The libvirt-daemon-system package still exists, but it’s now simply a convenient way to install the “typical” libvirt deployment consisting of all the components needed to run a QEMU-based hypervisor.

Release notes

You are invited to read more changes that happened in this version of libvirt, which was released on December 2nd, 2024.

#2504 #libvirt #Linux #news #Tech #technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #update

This version of Ubuntu started the development with one of the most significant changes ever done. This time, it’s about compiler optimization level used on Ubuntu packages by default. When this version of Ubuntu had started its development, the mailing list entry said the following:

* perl 5.40 and haskell / ghc 9.6.6 already migrated to the releasepocket, to avoid entanglement with other transitions.* dpkg-buildflags defaults to -O3 instead of -O2. This might require changes in package builds. Please be aware that we already build with -O3 on ppc64el, so look for possible packaging adjustments.

While the Perl one is irrelevant in this blog post, the second entry in the toolchain changes is interesting. The default build flags for all Ubuntu packages that are determined by dpkg-buildflags have been changed so that -O3 is being used as a default instead of -O2.

This means that all future builds for all Plucky Puffin packages will be more optimized. Because of this, the build times will increase, but that doesn’t affect the end user. As a result, the packages that are built with the third optimization level will be faster than before, which means that your computer will be faster the second you upgrade to 25.04.

However, the binary size for the packages will be bigger, and there is uncertainty whether all packages benefit from this level of optimization that will be applied to all the packages. Furthermore, all builds and tests will be run, so expect delays. After that, when you test 25.04 during the development cycle, you should experience performance improvements.

On a side note, Perl 5.40 was released to Ubuntu 25.04, which brings several new features, new analyzers, and breaking changes, such as the :reader attribute for field variables, the breaking changes related to use VERSION declarations, the Infinity (inf) and Not-a-Number (nan) constants in builtin static class (module), the medium-precedence Logical XOR ^^ operator, the try...catch...finally block being a stable Perl feature, and stable support for multiple value iterations for the for loop.

Let’s see what Ubuntu 25.04 Plucky Puffin will offer as the next LTS, 26.04 RR, gets closer to the development period.

https://officialaptivi.wordpress.com/2024/11/04/ubuntu-25-04-plucky-puffins-packages-are-more-optimized/

#O2 #O3 #2504 #Acceleration #C #C_ #Computer #computers #GCC #GCCCompiler #improvements #Linux #LinuxUbuntu #news #Optimization #performance #Plucky #PluckyPuffin #speed #Tech #technology #Ubuntu #Ubuntu2504 #Ubuntu2504Plucky #Ubuntu2504PluckyPuffin #Ubuntu2504Puffin #UbuntuLinux #ubuntulinux #update