sigh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059907
Title:
missing option to erase and use the whole drive
To manage notifications about this bug go to:
Before starting Calamares I unmounted it (of course), and there was no
swap partition (only zram).
There was a live Lubuntu system on the target drive, and obviously this
was recognized by Calamares.
The running live system was booted from another drive, but Calamares
either 'assumed' that
Well, today I found a case, where unmounting and swapping off does not
help. I had to wipe the first mibibyte.
In my Toshiba Satellite Pro c850-19w I connected a target SSD with a
current daily live Lubuntu system, and it was not identified as a target
device (until I wiped the partition table).
@ԜаӀtеr Ⅼарсһуnѕkі (wxl),
Yes, unmount what can be unmounted (unless when using the boot option
'toram', I think some partition(s) on the live drive should be left
mounted (not be forced to be unmounted)). And swapoff everything except
the zram.
I think that would squash this bug.
--
You
Why struggle to understand why the partition on the target drive is
mounted? Maybe because the target SSD is connected via USB (and not via
SATA). During these tests there is no internal drive in my Toshiba, only
two SSDs, the live drive and the target drive.
In the case of these tests with my
1. Fresh boot into iso in (UEFI mode).
2. The partition on the target drive is mounted automatically. I unmount
it now. This should be done automatically by Calamares.
3. I leave the zram swap on (I don't think it must be swapped off; I
want to check that.)
4. Fix for 2054795 and start the
I can try in another computer (not the Toshiba). But the zram swap
should not be linked to any SSD or HDD; it resides in RAM.
When trying to reproduce, did you manually unmount all partitions on the
target drive before starting Calamares?
I don't think that beginners will do that.
But when I
No, I shut down the computer after installing in BIOS mode, cold boot
into the installed system, shut down again, boot in UEFI mode into the
Lubuntu Noble live. The problem is *not* caused by running the installer
twice in one session.
But I agree, that it would be a good idea to run the umount
See also this link
https://discourse.lubuntu.me/t/report-about-iso-testing-and-two-
questions-about-reporting-or-not-reporting-bugs/4793
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059907
Title:
Public bug reported:
After installing in BIOS mode there was an MSDOS partition table with a
single partition. When trying to install in UEFI mode onto the same
target drive (an SSD), the only option was ‘Manual partitioning’. This
can be an obstacle, at least for beginners, who want to use an
See also Bug #2058375 reported by Miguel Angel Noguera 53 minutes ago
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/2058375
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2047295
Title:
I think this bug is closely related to Bug #2047295
https://bugs.launchpad.net/ubuntu/+source/lubuntu-installer-
prompt/+bug/2047295
where I asked (in vain) for comments from other users. Unfortunately few
people who have problems with English (dialogue and keyboard) might take
part in this
If you have problems to boot live systems (from USB), I think it can be
solved with mkusb
https://help.ubuntu.com/community/mkusb
because it makes the live system use GFXMODE set to 800x600 except when
cloning. So select 'live-only' and in the next menu 'dus-iso2usb' ...
Please report the
Congratulations Thomas (for theory) and Chris (for experiments). This is
like development of physics ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session takes ages
I agree with Thomas about the problems to boot some old computers.
I'm continuing to develop/tweak dus-iso2usb, added an extra (optional)
parameter 'boot-flag' that can be added when mkusb partition table is
selected. It helps HP computers, but may spoil booting some other
computers.
So I think
@ guiverc,
I think you have suitable hardware and the best experience of us to
answer the question in comment # 99.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
Impish live session
At
https://releases.ubuntu.com/22.04/
you find the amd64 iso file and its sha256sum, and at
http://cdimage.ubuntu.com/lubuntu/releases/22.04/release/
you find the corresponding Lubuntu files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hi again Thomas,
The grub comes from a compressed tarball, that is extracted onto the
target drive. This makes it independent of the current operating system
and its version of grub.
So in order to look at it, use dus-iso2usb, or if you want only the
basics, extract only the tarball, in this
Hi Thomas Schmitt,
> I wonder what is meant by "add some tweaks".
1. Made grub use UUID instead of device name to identify partition where
to find the grub files
---
# create grub.cfg to match iso file's name
echo -e "$inversvid tweak grub ...$resetvid"
# tweak 3: search by UUID
sleep 2
There is a check for an Ubuntu signature in order to accept iso files,
but no corresponding check to accept img files.
@ Canonical, It should be easy to fix, if you want to do it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think your patch is helpful, Renan :-)
I will ask at the Ubuntu Forum thread,
https://ubuntuforums.org/showthread.php?t=240=3=14075403#post14075403
if the people there agree that this suffices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Unfortunately, until [re]solved, several people are suspecting that
there is a security hole here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955471
Title:
Why is Extended Maintenance needed
Public bug reported:
There seems to be a misleading, incorrect message in
ubuntu-security-status
ESM wouldn’t be needed (or even enabled) until 20.04 is EOL, in 2025.
---
See this link:
https://discourse.ubuntu.com/t/why-is-extended-security-maintenance-
You can trick the Startup Disk Creator to clone non-Ubuntu iso files,
because it is willing to clone 'any' image file with the extension img.
So make a symbolic link, for example
$ ln -s debian-live-11.0.0-amd64-standard.iso
debian-live-11.0.0-amd64-standard.img
$ ls -ltr
total 924676
I can confirm this bug, tested in a Lenovo V130 running Ubuntu 20.04.2
LTS
There is an internal nvme drive, but hardinfo cannot see it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940749
Title:
@ Julian Andres Klode (juliank),
Please explain:
How does this bug affect the old versions Xenial and Bionic?
And how should we test that our computers are affected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested the current Lubuntu Impish live also in a Dell Precision M4800.
It works in UEFI mode too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937115
Title:
Unable to boot/install Impish daily
Tested the current Lubuntu Impish iso file dated
2021-08-17 17:22 "impish-desktop-amd64.iso"
Booting a cloned USB drive works [not only in BIOS mode but also] in
UEFI mode in a Dell Latitude E7240 :-)
So I can confirm that the bugfix works also to boot Lubuntu Impish in my
Dell.
--
You
Booted the current Ubuntu iso files from the iso testing web-site
-rw--- 2,9G2021-08-16 08:21 "focal-desktop-amd64.iso"
-rw--- 2,9G2021-08-16 08:30 "impish-desktop-amd64.iso"
in a Dell Latitude E7240 in UEFI mode.
The impish iso file fails :-(
Then I
When will the bugfixed impish iso file be uploaded and available for us
to test?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937115
Title:
Unable to boot/install Impish daily in UEFI boot mode
Requested debug data for Dell Latitude E7240:
---
$ efibootmgr -v
BootCurrent: 0012
Timeout: 0 seconds
BootOrder: 0007,0001,000E,0006,000A,0003,,0010,0012,0013,0002,0004,0011,0005
Boot* ubuntu
A USB drive with Impish made by Rufus 'UEFI only' & GPT fails in my Dell
Latitude E7240 with the same message as a cloned drive.
@juliank,
Where (in which operating system) and when (at what stage) should we run
efibootmgr -v
tar -cvf boot-debug,tar /sys/firmware/efi/efivars/Boot*
Maybe I'm
@leok,
Thanks again :-)
Now we can conclude that the booting problem is only affecting the live
system, maybe only a cloned live system (we have not yet tested systems
made with Rufus; probably such systems will work too).
--
You received this bug notification because you are a member of
@leok,
Thanks for testing :-)
I think it could be interesting if you have time to test in one of your
Dell Optiplex computers, if it is possible to *install Lubuntu Impish*
from a persistent live session, and that the installed system can boot.
--
You received this bug notification because you
I should add, that I installed in a Toshiba,
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
and then moved the [internal] SSD to a USB3 to SATA adapter and booted
my Dell Latitude E7240 and it works in UEFI mode. I don't want to
overwrite the internal M2 drive of my
I can report about a workaround:
The current Lubuntu Impish file, impish-desktop-amd64.iso, dated
2021-07-28 17:22 worked for me this way:
- Create a persistent live drive with mkusb-dus.
- Verify that it can boot both in UEFI and legacy BIOS mode.
- Install Lubuntu in UEFI mode (there was no
This bug affects my Dell Latitude E7240 in UEFI mode (but booting works
in BIOS mode).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937115
Title:
Unable to boot/install Impish daily in UEFI boot
The link in comment #17 works only for you, Norbert.
remove the tail '?u=norbert' to make it work for us too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884538
Title:
Removing debian-installer
I tested also the current Xubuntu Groovy version dated Okt 17 02:07 from
zsync,
Conclusion: This bug seems squashed with casper version 1.455 :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
The current Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 17
08:30 from zsync,
- '20201017' in the testing tracker
ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2942062592 okt 17 08:30 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
Hi Thomas,
The output of the partition editor commands is in the attached file.
** Attachment added: "p-ed-commands.txt"
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+attachment/5422669/+files/p-ed-commands.txt
--
You received this bug notification because you are a member of
Hi Thomas,
1. Yes, the software in the ISO fiddles with the USB stick partitioning.
I think this was introduced in Ubuntu 19.10. I think it is used to log
the installer (to help debug failures) and to store crash dumps. (I
would be happy to turn it off.)
Please tell me which partition editor
@ everybody,
In the light of the lasts findings, questions and suggestions, I did
some more tests, this time with yesterday's Xubuntu Groovy iso file,
that failed booting yesterday.
I think I started testing the cloned USB drive in the Lenovo V130 (which
worked), and continued testing in the HP
@ Thomas,
1. I know that it can improve things to start from a wiped drive, but I
don't know why. I know that before you got involved and started to
improve the booting, the systems could not create the ext4 partition in
my computers, unless the USB drive was wiped, and I *think* this was
@ Steve,
Booting 'nopersistent' is a mild tweak, and it seems to improve things a
lot.
Please consider if this should be the default (in other words modify the
iso file accordingly). At least now for Groovy, so that we can release a
set of iso files, that work in the [amd64] computers, that we
Hi again Jags Desai,
I'm glad that you managed to boot when using mkusb. When you want to
install Ubuntu-MATE, please read the tips at this link:
https://help.ubuntu.com/community/mkusb/persistent#Installing_-
_using_the_Install_icon_on_the_desktop
--
You received this bug notification because
Hi Chris,
1. In the meantime I tested the current Lubuntu Groovy iso file in the
HP Elitebook 8560p.
It boots when I made a nopersistent live drive using mkusb-plug, and I
could repeat it.
2. I don't know if the error that you see at shutdown causes failure at
the next boot (when there is an
You need the package 'usb-pack-efi' too.
sudo add-apt-repository ppa:mkusb/ppa # and press Enter
sudo apt update
sudo apt install mkusb usb-pack-efi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Jags Desai,
Yes, mkusb-dus (alias dus) is part of the mkusb package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily (again)
To manage notifications
Hi Jags Desai,
It is possible that your problem depends on the graphics, if there is
nvidia graphics. Have you tried to boot in recovery mode or with the
boot option 'nomodeset'?
But if your HP does not even reach grub, you may need a workaround for
the boot process. Please try to install mkusb
Hi Chris,
There seems to be a difference between the first boot and the subsequent
boots in your
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
It might depend on the creation of the ext4 partition behind the image
of the iso file, which happens only in the first attempt to boot.
Another
Thanks for all the improvements, Thomas and Steve :-)
Although we feel frustrated now, we must remember that the Groovy iso
files have improved a lot and can boot many more computers than when we
started.
-o-
There are workarounds to make also the remaining computers boot: for
example to make a
Hi Thomas,
> All Ubuntu flavors use the same bootloader logic; there is no
> distinction here.
>
> And I have checked that the latest xubuntu image has the same
> partition setup.
...
> So a failure to boot Xubuntu where Ubuntu works is not explained
> by missing/different xorriso options.
The current Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 14
08.30 from zsync,
- '20201014' in the testing tracker
$ sha256sum groovy-desktop-amd64.iso
20b9b69600470e6641406a6ab975f985903bde4555b552f3155693aa10a862a1
groovy-desktop-amd64.iso
when cloned to USB can boot an old HP
@ Steve Langasek (vorlon),
The current Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 13
08:36 from zsync,
- '20201013.1' in the testing tracker
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2894153728 okt 13 08:36 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop
Hi Chris,
Please test Ubuntu Desktop (standard Ubuntu) Groovy version dated Okt 13
08:36 from zsync,
- '20201013.1' in the testing tracker
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2894153728 okt 13 08:36 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
The current Lubuntu Groovy iso file
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 1894162432 okt 13 16:56 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
2bc2b6bf2a14a4a293ce5280e754ed9ef4913873a529c99bfe0bcfe222aff2b5
groovy-desktop-amd64.iso
when cloned does
Hi Thomas,
> > Please notice that the option -compliance no_emul_toc may cause
problems.
> Do you have any tangible indications for this (beyond the fact that MBR
> table does not work for the Lenovos) ?
I wrote maybe (which includes maybe not). I may have drawn faulty
conclusions when I
It seems I was too early to test the new current daily Ubuntu Desktop
iso file. Now I found this one:
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2894153728 okt 13 08:36 groovy-desktop-amd64.iso
$ sha256sum groovy-desktop-amd64.iso
The current daily Ubuntu Desktop iso file
-rw--- 1 sudodus sudodus 2938152960 okt 13 06:25 groovy-desktop-
amd64.iso
$ sha256sum groovy-desktop-amd64.iso
a1ee702fd38036ac3b22a34657c94a9f1f7cb476bc13b4712ee34dad20499fc2
groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
@ Chris,
I was almost sure, that the bug was squashed. But I cannot see anything
wrong with what you describe in comment #19, so it seems there more to
do until we have iso files that can boot all our computers (if at all
possible before the release of 20.10).
Anyway, I look forward to both your
Hi Steve,
I hope there is still time to improve booting of Groovy iso files, to
make also it work in old HP computers in BIOS mode. Thomas Schmitt
suggested a modification of the iso files, and according to my tests, it
works without destroying anything for other computers.
--
You received this
You are a wizard Thomas,
This tweak:
original=groovy-desktop-amd64_20201010_gpt.iso
test -f test_mbr.iso && rm test_mbr.iso
xorriso \
-indev "$original" \
-outdev test_mbr.iso \
-boot_image any replay \
-boot_image any appended_part_as=gpt \
-boot_image any
@guiverc,
> The dc7700 has no booting OS on it; last a failed xubuntu qa-test install but
> I bet
> it'd legacy/BIOS/MBR, and I know the dc7900 has legacy/MBR (no GPT) as my
> boxes are
> mostly 80-160GB disks & I don't bother with GPT
The problem is that the current Groovy *iso files contain
This morning (CET) I tested a cloned system from a modified iso file
according to Thomas Schmitt;
original=groovy-desktop-amd64_20201010_gpt.iso
test -f test_mbr.iso && rm test_mbr.iso
xorriso \
-indev "$original" \
-outdev test_mbr.iso \
-boot_image any replay \
I could get a signal to an external screen from the HP Elitebook 8560p.
As I expected, it failed to boot to the current Lubuntu Groovy iso file.
In mkusb's settings menu for a persistent live drive I selected
- MSDOS partition table
- usb-pack-efi
and I could boot to this persistent live
typo fix in comment #6
this bug needed MSDOS partition table --->
this computer needed MSDOS partition table
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy
I have access to one old and slow HP computer, a Probook 6450b with an
Intel i5-M520 CPU. But it seems to be too new to be affected by this
bug. It boots in BIOS mode with this new Groovy iso file.
My son has another and older HP Elitebook, and this bug needed MSDOS
partition table to boot via
@ Chris,
This bug might correspond to an observation, that I made years ago with
persistent live drives made by mkusb.
Some old (at that time maybe middle-aged) HP computers refuse to boot
. in BIOS mode
- from a USB drive
- via grub
- in a GUID partition table (GPT).
That made me add an entry
I tested also with the current daily Lubuntu Groovy iso file (dated
2020-10-10) and when cloned to a USB pendrive and booted, a 'writable'
partition is created as it should. This is a third indication that this
bug is squashed.
--
You received this bug notification because you are a member of
I have tested the current daily (2020-10-10) Xubuntu and Lubuntu iso
files too. When cloned to a USB drive, they can also boot the Lenovo
V130 in UEFI mode (and secure boot). It seems that bug #1895329 is
squashed too.
--
You received this bug notification because you are a member of Ubuntu
I zsynced the current daily Xubuntu Groovy iso date (dated 2020-10-10),
and when cloned to a USB pendrive and booted, a 'writable' partition is
created as it should.
This system was cloned directly after testing a larger Ubuntu Groovy
system, and with earlier iso files, it was likely to fail to
More tests - here is a list of all computers tested by me with the
Ubuntu Groovy system
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2936969216 okt 9 21:15 groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
00cbcce8855c00dd2231077e3a01aebc groovy-desktop-amd64.iso
I can report *success* from testing with the current daily Ubuntu Groovy
iso file
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2936969216 okt 9 21:15 groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
00cbcce8855c00dd2231077e3a01aebc groovy-desktop-amd64.iso
After
The first test results from the current daily Ubuntu Groovy iso file
$ ls -l groovy-desktop-amd64.iso
-rw--- 1 sudodus sudodus 2936969216 okt 9 21:15 groovy-desktop-amd64.iso
$ md5sum groovy-desktop-amd64.iso
00cbcce8855c00dd2231077e3a01aebc groovy-desktop-amd64.iso
indicate
Thanks Thomas for your insight in booting from a cloned image of an iso
file and the efficient method to find how to squash this bug :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
Hi Leo,
This sounds good, but please tell us if you tested a system
- cloned or
- persistent live made by mkusb or
- made some other way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Now I have tested how mkusb can create persistent live drives with
Thomas Schmitt's modifications with the xorriso command line.
It is still working when using usb-pack-efi (and the default GPT)
- in the Lenovo V130 in UEFI mode with secure boot and
- in the Dell Precision M4800 both in BIOS
@ Leó Kolbeinsson (leok),
Now I have uploaded my modified Groovy iso file and the corresponding
md5sum to
https://phillw.net/isos/linux-tools/alpha-beta/groovy/
$md5sum -c groovy-desktop-amd64_2020-10-08_fixed-by-xorriso.iso.md5
groovy-desktop-amd64_2020-10-08_fixed-by-xorriso.iso: OK
Good
Hi Thomas,
1. There was a name error, wrong name of the input iso file - easy to
understand and fix, but I asked before thinking twice. There was also an
ownership/permission error, the file was owned by root and there were
not enough permissions for the standard user (because I had copied it
@ Thomas,
There was a problem with permissions. I fixed it ...
@ everybody,
This test.iso file modified according to comment #181, when cloned,
makes USB drive that can boot the Lenovo V130 in UEFI mode with secure
boot.
Now there is a temporary boot option 'Linpus Lite' again (and it works).
Hi Thomas,
I failed according to your instructions at comment #174.
$ xorriso \
> -indev groovy-desktop-amd64.iso \
> -outdev test.iso \
> -boot_image any replay \
> -boot_image any appended_part_as=gpt \
> -boot_image any mbr_force_bootable=off
xorriso 1.5.2 : RockRidge
@ Leó Kolbeinsson (leok),
I am surprised, that what works in my Lenovo does not work in yours. But
the computers are different, and we can only guess what works before we
have tested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Leó Kolbeinsson (leok),
I am not sure what test you reported in comment #175. Maybe I am too
late, but this morning I uploaded my minimal iso file and the
corresponding md5sum to
https://phillw.net/isos/linux-tools/alpha-beta/groovy/
$ md5sum -c bug-1886148_comment-172-173.iso.md5
Booting this minimal device behaves differently in the Lenovo V130 in
UEFI mode. Linpus Lite is *not* activated, but in the temporary menu
there is an entry
EFI USB device ()
1. Secure boot stops further booting, so the Lenovo will not reach to a
grub prompt.
2. When I turn off secure boot, the
Thanks Steve :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage notifications about this bug go to:
Hi Thomas,
I tried to make a minimal grub iso file, but failed. After installing
xorriso too, I had the following error:
$ sudo grub-mkrescue -o output.iso minimal
grub-mkrescue: error: `mformat` invocation failed
.
I tried in an Ubuntu Groovy system. What is mformat? What should I add
to make
If the Ubuntu iso file according to comment #163 is the one you want us
to test, I'm sorry, but it is still failing when cloned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure
The Ubuntu Groovy iso file dated Oct 8 13.02
$ md5sum groovy-desktop-amd64.iso
0ca0a6242caffcb7c67497fc659f2b8c groovy-desktop-amd64.iso
is still affected by this bug. Maybe you should ask the manufacturer
what they are looking for instead of this trial and error game?
--
You received this
So you want us to test only USB boot drives with the live system
*cloned* from the iso file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage
@ Steve Langasek (vorlon),
Would you be able to ask the manufacturer, either Lenovo or InsydeH2O,
what they are looking for in their "Linpus Lite" boot option (in order
to boot in UEFI mode)?
In my computer, on the 'title line' of the BIOS information page is
written:
InsydeH2O Setup Utility
I tested the current daily Ubuntu Desktop Groovy iso file with the
Lenovo V130. The results match those of comments #155-156.
After that I made persistent live drives with mkusb (using usb-pack-
efi), and they worked as before. So I can confirm the results by Leó
Kolbeinsson (leok).
--
You
The same current daily Lubuntu Groovy iso file, when cloned, boots as it
should in a Dell Precision M4800.
But cloned drives are still affected by bug #1895329.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested the current daily Lubuntu Groovy iso file with the Lenovo V130.
When cloned to a USB drive, it does not boot in UEFI mode (the same
problem as before) :-(
When extracted to a FAT32 partition with boot and esp flags in a USB
drive, it boots in UEFI mode :-)
--
You received this bug
@ Akeo,
If I understand correctly, this bug is fixed in the current daily Groovy
iso files. These files are newer than the Groovy beta iso files.
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds
I can extract the content of an iso file to a FAT32 partition and get a
USB boot drive, that
@ Steve Langasek (vorlon),
Yes, it is a regression vs 20.04. The early Groovy iso files worked too,
until you made the big modification of the boot structure near the
beginning of July.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is still alive in the current Ubuntu Desktop Groovy daily iso
file dated October 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895329
Title:
when booting cloned live drive 3rd
Wrong reference to the other bug. It should be bug #1895329
http://launchpad.net/bugs/1895329
"when booting cloned live drive 3rd partition is created without file
system"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Lubuntu
---
I started testing the current daily Lubuntu Groovy iso file (faster to zsync)
with the Lenovo V130.
1. When cloned to a USB drive, it does not boot in UEFI mode (the same
problem as before).
2. When extracted to a FAT32 partition with boot and esp flags in a USB
drive, it boots
This bug is still alive in the current Ubuntu Desktop Groovy daily iso
file dated October 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886129
Title:
xubuntu : displays have become blank &
1 - 100 of 1165 matches
Mail list logo
