Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install

Bug #1951399 reported by Chris Guiver
322
This bug affects 35 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned

Bug Description

Ubiquity crashes when user tries to run ISO QA testing by following the procedure from:

http://iso.qa.ubuntu.com/qatracker/testcases/1300/info
http://iso.qa.ubuntu.com/qatracker/testcases/1305/info

The actual result is the same: installer crashes with the following line in the syslog - "chroot: failed to run command ‘tempfile’" .
Result does not depend on system type - happens on real hardware, QEMU, Virtualbox.

This tempfile came from debianutils package until 20211105. Now it is missed.

Expected result is completed bootable installation.

---

Xubuntu daily (jammy) install to
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

ubiquity failed with crash.

This install was attempted because Norbert had mentioned failure to install (using QEMU)
- https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951305
- https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951309
- https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951312

This install was an old BIOS box

--
possibly Useful detail on TIMING (Kubuntu/2021-11-08)
Bob H/bobicat noted in https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950132

"install crashed just before completion
previous daily (2021-11-07) installed without error"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
Date: Thu Nov 18 19:36:21 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Xubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211118)
ProcEnviron:
 LANGUAGE=en_AU.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Chris Guiver (guiverc) wrote :
Chris Guiver (guiverc)
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1951399

tags: added: iso-testing
Revision history for this message
Leó Kolbeinsson (leok) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Norbert (nrbrtx) wrote :

Main question here - how can we determine the list of duplicates?
There are 18 possible related bugs - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bugs?field.searchtext=crash&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=jammy&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.upstream_target=&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on .

I do not have time to diff the logs. I'm busy. But share love to both Xubuntu and MATE (especially MATE as team member) so I will continue to test both ISOs.
I simply followed testcases for both Xubuntu and MATE - http://iso.qa.ubuntu.com/qatracker/testcases/1300/info .

But for example Erich Eickmeyer does not want to read logs for us. Promotes some third party site instead. Not very friendly. If I understand correctly, then Ubuntu Studio is not affected but this set of bugs, they use Calamares.

It would be great to create a master bug for all these bugs and link QA test results to it.

Norbert (nrbrtx)
description: updated
Revision history for this message
Norbert (nrbrtx) wrote :

Tried to sort bugs. Set current as main for Xubuntu. Set bug 1950504 for MATE. Did not touch Ubuntu.

Both Xubuntu and MATE 20211118 installer crashed while following http://iso.qa.ubuntu.com/qatracker/testcases/1300/info .

Revision history for this message
Bob H (bobbicat) wrote (last edit ):

Something similar to this occurred on a previous version of Kubuntu.
I was test installing Kubuntu and I think it was Impish Indri.
If I remember right the tool chain had just been installed and the problem was in there somewhere.
I'm not a programmer or developer so I can't expand on that. I think tool chain might have something to do with it.

My report on 2021-11-08 was the first instance of this bug on Kubuntu Jammy Jellyfish, I had been testing every day with no problem until then. I posted at launchpad as soon as it cropped up. My report was bug 1950132.

The day before, 2021-11-07 everything had been fine.

I'm happy to engage in further testing if this is useful. I'll watch this page.

Revision history for this message
Bob H (bobbicat) wrote (last edit ):

I think this is the same bug as bug 1950132.
The process falls over during the installation in the slideshow.

Revision history for this message
Norbert (nrbrtx) wrote :

Log files differ, so I'll recommend to use bug 1950132 for Kubuntu.

Revision history for this message
Norbert (nrbrtx) wrote :

If I understand things correctly, then there are two common errors in logs for Budgie (tracked at bug 1950809), MATE and Xubuntu:

```
xubuntu plugininstall.py: log-output -t ubiquity chroot /target py3compile -p python3 /usr/share/python3/
xubuntu plugininstall.py: log-output -t ubiquity chroot /target mount -t proc proc /proc
xubuntu plugininstall.py: log-output -t ubiquity chroot /target mount -t sysfs sysfs /sys
xubuntu plugininstall.py: log-output -t ubiquity mount --bind /dev /target/dev
xubuntu plugininstall.py: log-output -t ubiquity mount --bind /run /target/run
--> xubuntu ubiquity: /usr/lib/python3/dist-packages/Onboard/LayoutLoaderSVG.py:447: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?
--> xubuntu ubiquity: raise Exceptions.LayoutFileError("Unrecognized modifier %s in" \
```

about onboard on Xubuntu and MATE. Does not exist in Kubuntu. Reported as bug 1951534 .

And

```
xubuntu ubiquity: umount: /target/cdrom: no mount point specified.
xubuntu plugininstall.py: log-output -t ubiquity umount /target/cdrom
xubuntu plugininstall.py: log-output -t ubiquity mount --bind /cdrom /target/cdrom
xubuntu ubiquity: chroot: failed to run command ‘tempfile’
xubuntu ubiquity: : No such file or directory
xubuntu plugininstall.py: log-output -t ubiquity umount /target/cdrom
xubuntu ubiquity: grep: /target/etc/apt/sources.list: No such file or directory
xubuntu plugininstall.py: Exception during installation:
xubuntu plugininstall.py: Traceback (most recent call last):
xubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1854, in <module>
xubuntu plugininstall.py: install.run()
xubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 60, in wrapper
xubuntu plugininstall.py: func(self)
xubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 188, in run
xubuntu plugininstall.py: self.configure_apt()
xubuntu plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 588, in configure_apt
xubuntu plugininstall.py: raise install_misc.InstallStepError(
xubuntu plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 127
```

about third-party components installation by Ubiquity. Happens in Budgie, Kubuntu, Xubuntu and MATE.

The first looks non-fatal, but the second seems to be fatal and possibly leads to crash.

Waiting for reaction from official Ubiquity developers as soon as possible.

Norbert (nrbrtx)
summary: - xubuntu jammy daily fails to install
+ Xubuntu, MATE: jammy daily fails to install
tags: added: ubuntu-mate
Revision history for this message
Norbert (nrbrtx) wrote : Re: Xubuntu, MATE: jammy daily fails to install
Norbert (nrbrtx)
description: updated
Norbert (nrbrtx)
description: updated
Norbert (nrbrtx)
summary: - Xubuntu, MATE: jammy daily fails to install
+ Kubuntu, MATE, Xubuntu: jammy daily fails to install
tags: added: kubuntu
Norbert (nrbrtx)
summary: - Kubuntu, MATE, Xubuntu: jammy daily fails to install
+ Budgie, Kubuntu, MATE, Xubuntu: jammy daily fails to install
tags: added: ubuntu-budgie
Revision history for this message
Norbert (nrbrtx) wrote : Re: Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install

As for today (20211119) the following flavors are affected by the current bug:
* Kylin
* Budgie
* Kubuntu
* MATE
* Xubuntu

All they are crashed on 1300 install because of "plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 127".

---

The following, Calamares-based are not affected.
* Lubuntu
* Ubuntu Studio

Surprisingly Ubuntu is not affected, so were installed normally.

---

I'll continue to test daily ISOs until bug get fixed.

summary: - Budgie, Kubuntu, MATE, Xubuntu: jammy daily fails to install
+ Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install
tags: added: kylin ubuntu-kylin
Revision history for this message
Doug Smythies (dsmythies) wrote :

Norbert wrote: "Surprisingly Ubuntu is not affected, so were installed normally."

Disagree. It is affected and does not install.

I had set bug #1950875 as a duplicate of bug #1950132, but you removed it.

Revision history for this message
Leó Kolbeinsson (leok) wrote :

I also have reported Ubuntu being affected on 3 different dailies on the QA test site.

Further ran 2 tests on the Ubuntu Jammy ISO 19-11-2021 and both failed -

See test results : http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/239955/testcases/1300/results

Revision history for this message
Bob H (bobbicat) wrote :

Ubuntu Desktop amd64 fails to install on my system. Throws up 'Installer Crashed' error message during slideshow.

Manual partitioned install to solid state drive, nvidia so using safe graphics and third party software,

This problem first appeared in Jammy Jellyfish on 08-11-2021.

Before that date all was working fine. Daily checks had proceeded with no problems.

Again I humbly suggest some change was introduced between 07-11-2021 and 08-11-2021 and is the cause of this problem.

Leó Kolbeinsson (leok)
summary: - Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install
+ Ubuntu,Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to
+ install
Revision history for this message
Bob H (bobbicat) wrote : Re: Ubuntu,Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install

In addition to the above (in bug description):-

Ubiquity crashes when user tries to run ISO QA testing by following the procedure from:

http://iso.qa.ubuntu.com/qatracker/testcases/1302/info

Ubuntu Desktop amd64 fails to install.
Stops and throws up 'Installer Crashed' error message during slideshow.

Revision history for this message
Norbert (nrbrtx) wrote :

By some mistake on the web-server http://cdimage.ubuntu.com/daily-live/current/jammy-desktop-arm64.iso.zsync is built on 2021-11-05, and not on 2021-11-19. This is not my mistake.

Manually downloaded Ubuntu 20211119 and got crash.

tags: added: ubuntu
summary: - Ubuntu,Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to
+ Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to
install
Revision history for this message
Doug Smythies (dsmythies) wrote :

On the parent page, http://cdimage.ubuntu.com/cdimage/daily-live/ , it says "Latest images to have passed any automatic testing; try this first" for the "current" directory. And indeed, those files are dated November 5th for the AMD64 versions. And yes, they do install fine, however that is not relevant to all of these bug reports.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

Norbert,

I'm not JUST with Ubuntu Studio (which may go back to Ubiquity, btw), but I'm also with the Kubuntu team, a member of the Community Council, and, in this context, a member of the Bug Squad which is here to triage bugs.

When triaging bugs, if we find a particular bug report is not helpful (or described very well), then you get a standard response like I gave you. When you say "see logs" and then upload an identical bug report later with a crash, that shows a pattern that you're not willing to help by describing where you were in the process when the installation crash. Additionally, you were filing *multiple* bugs with the same description which rightfully were marked as duplicates.

Please, do not take those personally. I was trying to be friendly by injecting into the standard response that saying "see logs" doesn't help. The standard response and my "'see logs' doesn't help" comment were multiple hints as to what are needed by the Ubuntu Foundations Team (the developers of Ubiquity) in order to solve the problem. Describing what happened when the crash occurred helps them know *where* to look in the logs for the problem.

Basically, I gave you information on how to help them help you, but instead you drag me over the coals in your comment about me being "not friendly". I don't work for Canonical, I'm not part of the Ubuntu Foundations Team. I'm just as much of a volunteer as you.

The only reason I'm commenting here publicly is that with that public comment about me, I felt the need to defend myself. In the future, if you have a problem with me, email me directly or find me in IRC so we can have a private conversation about it and thereby abide by the Code of Conduct.

Revision history for this message
Bob H (bobbicat) wrote (last edit ):

what is a masterbug?
is it about to take over the universe and beyond?
do we need to achieve herd immunity?

should this be asked as a question?

can we kill bugs without killing one another?

Chris Guiver (guiverc)
description: updated
Revision history for this message
Bob H (bobbicat) wrote :

Because this bug prevents completion of Jammy Jellyfish installation it seems testing is halted for the time being until the issue is addressed.

As this situation arose on 8-11-2021 and it seems to have had no attention since then I am guessing the developers consider this to be a matter of little or no importance at this time.

I suspect that they are aware of what is holding things up and will return the daily-live releases to a state where testing can resume when they are ready.

I also reason that until then bug reports for Jammy will be of no value.

I will watch the proceedings with interest and wait until my efforts can be of some use.

Revision history for this message
Erich Eickmeyer (eeickmeyer) wrote :

To me, this looks like it might be due to a python version difference. Minor python version changes have been known to break stuff, but I'm not an expert in this. I'm tagging with rls-jj-incoming since that should get the attention of the proper teams and marking this as triaged.

tags: added: rls-jj-incoming
Changed in ubiquity (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
dk3bi (dk3bi) wrote : AW: [Bug 1951399] Re: Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install

I installed Lubuntu first. Then added the Xfce Desktop afterwards. It's not the original Xubuntu now but everything installed well and runs perfectly now.Regards, Udo

Gesendet von Yahoo Mail auf Android

  Am Sa., Nov. 20, 2021 at 18:05 schrieb Erich Eickmeyer <email address hidden>: To me, this looks like it might be due to a python version difference.
Minor python version changes have been known to break stuff, but I'm not
an expert in this. I'm tagging with rls-jj-incoming since that should
get the attention of the proper teams and marking this as triaged.

** Tags added: rls-jj-incoming

** Changed in: ubiquity (Ubuntu)
      Status: Confirmed => Triaged

--
You received this bug notification because you are subscribed to a
duplicate bug report (1950852).
https://bugs.launchpad.net/bugs/1951399

Title:
  Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to
  install

Status in ubiquity package in Ubuntu:
  Triaged

Bug description:
  Ubiquity crashes when user tries to run ISO QA testing by following
  the procedure from:

  http://iso.qa.ubuntu.com/qatracker/testcases/1300/info
  http://iso.qa.ubuntu.com/qatracker/testcases/1305/info

  The actual result is the same: installer crashes with the following last line in the small terminal at the bottom - "plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 127" .
  Does not depend on system type - happens on real hardware, QEMU, Virtualbox.

  This plugininstall.py came from ubiquity package.

  Expected result is completed bootable installation.

  ---

  Xubuntu daily (jammy) install to
  - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  ubiquity failed with crash.

  This install was attempted because Norbert had mentioned failure to install (using QEMU)
  - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951305
  - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951309
  - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951312

  This install was an old BIOS box

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 21.10.10
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  Date: Thu Nov 18 19:36:21 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/xubuntu.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Xubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211118)
  ProcEnviron:
   LANGUAGE=en_AU.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_AU.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1951399/+subscriptions

Revision history for this message
Chris Guiver (guiverc) wrote :

@Bob H/bobbicat

Thank you for your testing; yes that's useful detail on timings so thank you. This will impact install QA-testing until fixed (ISOs using `ubiquity`) but shouldn't impact live testing :)

description: updated
Revision history for this message
Bob H (bobbicat) wrote :

@Chris Guiver
Thanks for that info, Chris. I will perform a regular Live Session test for the time being, reporting my results.

Revision history for this message
Norbert (nrbrtx) wrote :

I finally found the real problem - it is clearly stated in the [syslog](https://launchpadlibrarian.net/569529666/UbiquitySyslog.txt) (now we know how useful is to read logs!!!):

```
Nov 18 08:32:16 xubuntu ubiquity: chroot: failed to run command ‘tempfile’ <-- this
Nov 18 08:32:16 xubuntu ubiquity: : No such file or directory
```

Previous Ubuntu 20211105 has this `/bin/tempfile` executable in place, it came from `debianutils` package with version 4.11.2build1 . See search result from Impish ( https://packages.ubuntu.com/search?searchon=contents&keywords=tempfile&mode=exactfilename&suite=impish&arch=any ) .
But the modern 5.5-1 version from the newest image do not provide the `/bin/tempfile` executable, so it is missed. It is actually bug 1951742 .

So the temporary fix is the following:

1. Launch ISO (tested on Ubuntu MATE 20211120)
2. Start it in Try… mode
3. Launch Ubiquity installer
4. Wait for appearing of "Who are you?" page
5. Open terminal with <Ctrl>+<Alt>+<T> to download previous version of `debianutils` and copy /bin/tempfile to /target/usr/bin directory by

    wget http://archive.ubuntu.com/ubuntu/pool/main/d/debianutils/debianutils_4.11.2_amd64.deb
    sudo apt-get install --allow-downgrades -y ./debianutils_4.11.2_amd64.deb
    sudo mkdir -p /target/usr/bin
    sudo cp -v /bin/tempfile /target/usr/bin/

6. Return to Ubiquity window and finish the installation.
7. Enjoy installed system.

Norbert (nrbrtx)
description: updated
Revision history for this message
ajgreeny (ajg-charlbury) wrote :

I shall try the workaround from Norbert later today if I have time and report back.

If this works as easily as suggested it will be a great move forward, so thanks to Norbert for this detailed info.

Revision history for this message
ajgreeny (ajg-charlbury) wrote :

Yes. Whoopee!!
Todays iso of Xubuntu (22 Nov 2021) installed well in KVM1QEMU using UEFI after carrying out Norbert's suggested change of the debianutils to an older original version.

Brilliantly done!

Revision history for this message
vmc (vmclark) wrote :

Installed without issue, using "2021-11-24 08:32" ISO

Revision history for this message
Bob H (bobbicat) wrote (last edit ):

Ubuntu Jellyfish desktop amd64 installed without problems
from daily iso today 24-11-2021
safe graphics, third party software, manual partitioning
as far as I'm concerned this bug is fixed

Revision history for this message
Bob H (bobbicat) wrote (last edit ):

Kubuntu Jellyfish desktop amd64 installed without problem
from daily iso today 24-11-2021
safe graphics, third party software, manual partitioning
as far as I'm concerned this bug is fixed

Revision history for this message
Leó Kolbeinsson (leok) wrote :

Uubuntu Jellyfish desktop amd64 from daily iso today 24-11-2021 installed with no errors
UEFI and UEFI+ secure boot modes

Revision history for this message
ajgreeny (ajg-charlbury) wrote :

Unlike today's Ubuntu iso, 2021-11-24 08:32, today's Xubuntu iso times at 02:14 is still crashing.
I assumed all the different DE versions would be fixed at the same time but apparently not; maybe tomorrow?
I'll zsync and try again if I have time.

Revision history for this message
Bob H (bobbicat) wrote (last edit ):

@ aigreeny todays Xubuntu was released about five hours before the others, I'm guessing the corrections that were made later to the other flavours hadn't been applied that early.
I tested the Xubuntu daily almost as it was released and got a fail too.
I would imagine that, all being well, tomorrows dailies will all pass rock solid.
...and status will be 'fix released'.

Many thanks to those who worked towards a solution.

Revision history for this message
Rik Mills (rikmills) wrote : Re: [Bug 1951399] Re: Ubuntu, Budgie, Kubuntu, Kylin, MATE, Xubuntu: jammy daily fails to install

On 24/11/2021 21:41, ajgreeny wrote:
> Unlike today's Ubuntu iso, 2021-11-24 08:32, today's Xubuntu iso times at 02:14 is still crashing.
> I assumed all the different DE versions would be fixed at the same time but apparently not; maybe tomorrow?
> I'll zsync and try again if I have time.

The cron jobs that build the dailies stagger the various flavours at
different times across the day. i.e. xubuntu is about 2am, kubuntu 5am
(ish), ubuntu 8am etc.....

The fixed ubiquity did not hit the release pocket until about 3am on the
24th, so the xubuntu build that day would have just missed picking it up.

Revision history for this message
Bob H (bobbicat) wrote (last edit ):

thanks Rik

Xubuntu Jellyfish desktop amd64 installed without problem
from daily iso today 25-11-2021
safe graphics, third party software, manual partitioning

Kubuntu Jellyfish desktop amd64 installed without problem
from daily iso today 25-11-2021
safe graphics, third party software, manual partitioning

Ubuntu Jellyfish desktop amd64 installed without problem
from daily iso today 25-11-2021
safe graphics, third party software, manual partitioning

I don't have time to check the other flavours but I think they will be okay when they are updated.

Thanks again to those involved.

Revision history for this message
ajgreeny (ajg-charlbury) wrote :

Good to know that Bob, and accordingly I will xsync yesterday's ISO later today and try again.

Revision history for this message
ajgreeny (ajg-charlbury) wrote :

That was a typo by the way; should have been zsync as you probably knew.

Revision history for this message
SergeyIT (serge-i-t) wrote (last edit ):

xUbuntu Jellyfish desktop amd64 installed with 1 comment from daily iso today 25-11-2021
Old BIOS (no UEFI), MBR hdd.
Load updates (yes & no),third party software (yes & no), manual partitioning.

Comment - dialogue after partitioning:
"Go back to the menu and resume partitioning"
"No EFI System Partition was found. This system will likely not be able to boot successfully, and the installation process may fail.
Please go back and add an EFI System Partition, or continue at your own risk."
... Continue
Installed OK.
Only grub-pc installed - OK.

About live system - at shutsdown the system hold.
Last messages in console:
...
-> Starting shuts down the "live" preinstalled system cleanly
(3 times) -> /usb/bin/which this version of `which' is deprecated use `command -v' in scripts instead.

Revision history for this message
Bob H (bobbicat) wrote :

@ ajgreeny yes, I use zsync too

Revision history for this message
Julian Andres Klode (juliank) wrote :
tags: removed: rls-jj-incoming
Changed in ubiquity (Ubuntu):
assignee: nobody → Robie Basak (racb)
Revision history for this message
ajgreeny (ajg-charlbury) wrote :

I have also just installed the ISO from today, 25 Nov 2021, again using KVM/QEMU with no problems.
I used UEFI mode and allowed the installer to use the whole virtual disk, ie, no manual partitioning.
So for this ISO both the live and virtual OS are working beautifully.

Revision history for this message
Jane Atkinson (irihapeti) wrote :

Installed yesterday evening with the ISO from 25 November, and also with today's (26 November), both successfully.

I just did the Install Entire Disk (with UEFI mode), none of the other options, but I imagine those will also work correctly.

Revision history for this message
Robie Basak (racb) wrote :

debianutils in Ubuntu Jammy now has tempfile restored (with a deprecation warning) and the deprecation warning for which removed. That's the only task I was working on, so I'm unassigning myself from this bug. If this resolved this particular issue then this bug might be marked as Fix Released, except that we don't know what the status of which and tempfile will be in Ubuntu beyond Jammy. It may be the case that depending components need to move away from tempfile and which in the end anyway, in which case maybe the task should remain open.

Changed in ubiquity (Ubuntu Jammy):
assignee: Robie Basak (racb) → nobody
tags: added: rls-jj-incoming
Revision history for this message
Brian Murray (brian-murray) wrote :

I'd rather that we have a new bug report for switching ubiquity away from using tempfile or which rather than this bug with lots of comments and duplicates so I'm going to go ahead and set this to Fix Released.

Changed in ubiquity (Ubuntu Jammy):
status: Triaged → Fix Released
To post a comment you must log in.