# Testing 22.04 - Are you brave enough?

**URL:** <https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461>\
**Category:** Get Involved\
**Created:** [November 5, 2021, 1:05pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461 "2021-11-05T13:05:43Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![Frogshair](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/frogshair/32/1515_2.png) [@Frogshair](https://discourse.ubuntubudgie.org/u/Frogshair)\
**Post date:** [January 13, 2022, 5:45pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/61 "2022-01-13T17:45:04Z")

</div>

Unable to install Chrome OS layout is there a software source I need to enable ?

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 13, 2022, 5:47pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/62 "2022-01-13T17:47:36Z")

</div>

The budgie extras daily ppa … information on the first post.

---

<div class="post-metadata">

**Author:** ![Frogshair](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/frogshair/32/1515_2.png) [@Frogshair](https://discourse.ubuntubudgie.org/u/Frogshair)\
**Post date:** [January 13, 2022, 5:54pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/63 "2022-01-13T17:54:07Z")

</div>

The PPA has been installed for weeks . I see a notification that says failed to install.

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 13, 2022, 6:19pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/64 "2022-01-13T18:19:58Z")

</div>

Ah - good spot - yeah welcome should install the backports PPA

```
sudo add-apt-repository ppa:ubuntubudgie/backports

```

Will send out a welcome update soonish

---

<div class="post-metadata">

**Author:** ![Frogshair](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/frogshair/32/1515_2.png) [@Frogshair](https://discourse.ubuntubudgie.org/u/Frogshair)\
**Post date:** [January 13, 2022, 6:25pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/65 "2022-01-13T18:25:17Z")

</div>

Thanks, installing a new daily build , having other issues. I’ve had this build since the beginning of the cycle.

Edit: Reinstalled, all is well !

---

<div class="post-metadata">

**Author:** ![frenchy](https://avatars.discourse-cdn.com/v4/letter/f/b9e5f3/32.png) [@frenchy](https://discourse.ubuntubudgie.org/u/frenchy)\
**Post date:** [January 14, 2022, 5:11pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/66 "2022-01-14T17:11:41Z")

</div>

on live ISO , the French keyboard is installed as you can see on the picture below but this setting does not seem to be applied. The qwerty keyboard is actually used and yes it’s a budgie specific bug i think

 ![budgie keyboard](https://canada1.discourse-cdn.com/flex035/uploads/ubuntubudgie/original/2X/5/565c4166733f1d45e43c7c4ee699ca45ea829081.png)

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 18, 2022, 10:19am UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/67 "2022-01-18T10:19:52Z")

</div>

![image](https://canada1.discourse-cdn.com/flex035/uploads/ubuntubudgie/original/2X/e/eeb25f1e47e395cbbb8876f14c13154fcb58ba65.jpeg)

Hopefully this is a key new area that will debut in 22.04 - we need your help to refine it.

We have forked gnome-control-center - its now called budgie-control-center. We have been removing all the gnome-shell specifics. This is a key area we need your help to confirm.

Also a few changes have been made specifically to this initial release:

" Forked at v41 from gnome-control-center, budgie-control-center has undergone extensive refactoring to ensure install artifacts do not clash from those produced by gnome-control-center.

For this initial release, much of the gnome-shell specific capabilities have been removed.

In addition the following changes have been added:

1. Display tab shows fractional scaling options if the distro carries Mutter X11 xrandr fractional scaling patches.
2. Display tab now logically shows display privacy options
3. Mouse acceleration options are shown on the Mouse properties tab
4. Info overview tab shows the budgie-desktop version (if the version of budgie-desktop is later than the published 10.5.3)
5. Info overview tab defaults to the Budgie Desktop logo
6. Distros and Distro flavors can show their own logo - [d4c6707](https://github.com/BuddiesOfBudgie/budgie-control-center/commit/d4c6707b1fe609335fdcb49391892689163b87f5)"

If you want to help test there is a Jammy PPA available

```
sudo add-apt-repository ppa:ubuntubudgie-dev/budgie-control-center
sudo apt full-upgrade
sudo apt purge gnome-control-center
```

---

<div class="post-metadata">

**Author:** ![makitso](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/makitso/32/4961_2.png) [@makitso](https://discourse.ubuntubudgie.org/u/makitso)\
**Post date:** [January 18, 2022, 9:55pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/68 "2022-01-18T21:55:23Z")

</div>

Daily ISO hangs system.  
Downloaded daily 22.04 and booted live on my Thinkpad T560 with a SSD.

After selecting to try UB it hung tight, nothing worked, hard reset needed.  
These messages flashed

DMAR DRHD handling fault status reg 3  
DMAR [DMA Write NO\_PAID] Request dev fault add…  
[fault reason 0x05] PTE Write access is not set

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 18, 2022, 10:01pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/69 "2022-01-18T22:01:30Z")

</div>

k - that sounds like a linux kernel 5.15 issue. This arrived in todays ISO.

Please manually file a bug here - tag the issue “jammy” [OpenID transaction in progress](https://bugs.launchpad.net/ubuntu/+source/linux/+filebug)

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 18, 2022, 10:13pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/70 "2022-01-18T22:13:27Z")

</div>

Do note - I did a quick google and in Arch they saw the first “status reg 3” message - their recommendation was to boot the kernel with the parameter

```auto
intel_iommu=off

```

So its worth (after filing the bug report) trying that

---

<div class="post-metadata">

**Author:** ![makitso](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/makitso/32/4961_2.png) [@makitso](https://discourse.ubuntubudgie.org/u/makitso)\
**Post date:** [January 19, 2022, 3:27pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/71 "2022-01-19T15:27:12Z")

</div>

I can confirm that intel\_iommu=off does work

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 19, 2022, 3:31pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/72 "2022-01-19T15:31:50Z")

</div>

sounds like Canonical should switch a flag or two in their kernel build back to pre 5.15 days.

Suggest adding the observation to your report - boot with the intel\_iommu parameter and run the apport\_collect request on your bug report. Then the bug status can be change from “incomplete” to “new”

---

<div class="post-metadata">

**Author:** ![makitso](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/makitso/32/4961_2.png) [@makitso](https://discourse.ubuntubudgie.org/u/makitso)\
**Post date:** [January 19, 2022, 10:21pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/73 "2022-01-19T22:21:47Z")

</div>

This was my first successful install of 22.04 onto my dual boot Thinkpad T510.

First, I needed to add the intel\_iommu=off parameter to the live CD kernel boot.  
I started the install and when it came to the point where I selected the partitions to install into I selected “something else” since I have a Windows partition and a separate /home partition.

My first anxious moment came with the system said that there was no EFI partition and that installing may cause problems. Well, since the Thinkpad did not use EFI I continued and the rest of the install went correctly.

Once the install was completed I rebooted, expecting the GRUB display but there was none. I rebooted and then changed the boot parameters to finish booting.

However, there was no dual boot, or windows partition. I was a bit anxious here thinking that the windows partition had been destroyed until I discover that GRUB\_DISABLE\_OS\_PROBER was not running. I needed to update the grub file to include the GRUB\_DISABLE\_OS\_PROBER=false and then run update-grub to get the windows partition back.

The next thing I noticed after the install was the need to complete the language support install. Seems like the installer should be able to figure this out??

My concern is that folks installing 22.04 on older dual-boot machines are in for some choppy times.

I have the backports PPA installed and the budgie-screenshot applet will not install.

Oh yes, Firefox load time still is going to loose customers.

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 19, 2022, 11:32pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/74 "2022-01-19T23:32:45Z")

</div>

> [@makitso](#):
>
> GRUB\_DISABLE\_OS\_PROBER

Yeah. That’s a grub upstream decision due to perceived security concerns. Before Christmas when the Canonical devs were discussing this no definitive conclusions were reached. From your observations still no progress. Guess we will have to wait for a few more weeks.

As to the language issues. Yeah. If the network was OK during the install then the locales should have been automatically installed I would have thought.

Worth reporting this issue against the ubiquity package to confirm.

---

<div class="post-metadata">

**Author:** ![makitso](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/makitso/32/4961_2.png) [@makitso](https://discourse.ubuntubudgie.org/u/makitso)\
**Post date:** [January 20, 2022, 12:01am UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/75 "2022-01-20T00:01:40Z")

</div>

I understand the need for security. But, can you imagine the dual boot guy that does an upgrade and their windows partition is gone.

---

<div class="post-metadata">

**Author:** ![makitso](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/makitso/32/4961_2.png) [@makitso](https://discourse.ubuntubudgie.org/u/makitso)\
**Post date:** [January 20, 2022, 4:03pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/76 "2022-01-20T16:03:52Z")

</div>

So, the way I see it there are two potential land mines hidden in 22.04, intel\_iommu and GRUB\_DISABLE\_OS\_PROBER.

The dual-boot person who does an automatic update from 20.04 or 21.10 to 20.04 will think the upgrade went well only to have their other OS partitions gone and the desktop hangs. Seems ugly to me ☹

---

<div class="post-metadata">

**Author:** ![Frogshair](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/frogshair/32/1515_2.png) [@Frogshair](https://discourse.ubuntubudgie.org/u/Frogshair)\
**Post date:** [January 20, 2022, 5:14pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/77 "2022-01-20T17:14:14Z")

</div>

> GRUB\_DISABLE\_OS\_PROBER

Saw this today after the kernel update, but don’t see any problems after reboot.

---

<div class="post-metadata">

**Author:** ![Linux4Everyone](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/linux4everyone/32/3760_2.png) [@Linux4Everyone](https://discourse.ubuntubudgie.org/u/Linux4Everyone)\
**Post date:** [January 20, 2022, 9:10pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/78 "2022-01-20T21:10:55Z")

</div>

Hi everyone, the 22.04 daily ISO (downloaded Jan. 20) crashes for me during installation. I’ve tried installing to the metal on a ThinkPad P53 (for which I’m attaching logs) and two other laptops to no avail. This is using both live environment and the dedicated install option.

Here’s a Nextcloud link to /var/log/syslog and /var/log/partman, captured immediately after the installation failed: [Cloud L4E](https://l4e.yourownnet.eu/s/t5CwT2dcKHHLtXS)

The exact error message is “ubi-partman failed with exit code 10.”

I hope this helps. Please let me know how I can be of service to resolve this!

---

<div class="post-metadata">

**Author:** ![fossfreedom](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/fossfreedom/32/1405_2.png) [@fossfreedom](https://discourse.ubuntubudgie.org/u/fossfreedom)\
**Post date:** [January 20, 2022, 9:41pm UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/79 "2022-01-20T21:41:54Z")

</div>

If I understand the syslog correctly it is crashing at the point trying to grab packages from `http://hr.archive.ubuntu.com/ubuntu` - various 404 errors and a specific issue trying to install the nvdia 470 driver. You are using nvidia graphics?

Assuming yes - this must be due to the kernel 5.15 that landed in the ubuntu repo a couple of days ago. Looking at the bug reports - must be a bumpy ride here and this is part of the issue.

The [hr.archive.ubuntu.com](http://hr.archive.ubuntu.com) issues are probably temporary - the archive might not be fully up-to-date - it will be hopefully after some time assuming that the archive is working correctly.

So two things.

First - I’m hoping after the crash you would have been directed to the live session - please report the bug to launchpad via

```
ubuntu-bug ubiquity

```

Two suggestions to force an install.

1. launch into the live session - when installing, don’t tick the third party/wifi option - this will mean installing via the opensource graphics
2. disconnect your network/wifi - so that it doesn’t try to retrieve packages from the broken archive

On install you can see force an alternative archive via `software-properties-gtk`.  
Secondly, hopefully one of the other Hardware Drivers nvidia graphics will work. You might just have to wait for Canonical kernel devs/graphics devs/nvidia to work through the issues.

Ah well - the joy of early testing … major components such as the linux kernel causing issues like this.

---

<div class="post-metadata">

**Author:** ![Linux4Everyone](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.ubuntubudgie.org/linux4everyone/32/3760_2.png) [@Linux4Everyone](https://discourse.ubuntubudgie.org/u/Linux4Everyone)\
**Post date:** [January 21, 2022, 8:28am UTC](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461/80 "2022-01-21T08:28:16Z")

</div>

This was extraordinarily helpful!

I am using Nvidia graphics (RTX Quadro 4000), was connected via WiFi, and was checking the option to download updates.

Your suggestions solved the problem. I stayed disconnected but DID check install 3rd party drivers.

I’ll recreate the scenario and submit the bug to launchpad. (One quirk though: it appears you can only attach ONE file there, and I need to attach two logs…)

Thanks again!

[Previous page](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461.md?page=3)

[Next page](https://discourse.ubuntubudgie.org/t/testing-22-04-are-you-brave-enough/5461.md?page=5)
