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 & unusa
@ RussianNeuroMancer,
> I guess this bugreport is about first behavior rather about the
second?
- Yes, because cloning (e.g. with usb-creator-gtk) is what the
developers say should work.
- On the other hand, no, several users (including me) would like the new
boot configuration to work (in UEFI
@ Chris Guiver (guiverc),
Yes, there is a workaround.
The Lenovo V130 can boot with the current daily Lubuntu Groovy iso file
also in UEFI mode, when making a persistent live drive by mkusb-dus and
selecting 'usb-pack-efi'.
See also the following link,
https://help.ubuntu.com/community/mkusb/pe
The bug is still there in the current daily Lubuntu Groovy iso file
(beta candidate). See the attached screenshot.
Please notice that the error is not temporary. It persists after reboot.
** Attachment added: "bug-1895329-in-lubuntu-beta-candidate.jpg"
https://bugs.launchpad.net/ubuntu/+sourc
@ Norbert (nrbrtx),
When you have time and energy, please test
- a current daily iso file of a developing version of the flavour that
you like
- *cloned* to a USB drive
- in both BIOS and UEFI mode
- in the computers where you want future versions of Ubuntu flavours to
work, and that are avail
Thanks for the details about the computer, where Ubuntu Groovy fails in
UEFI mode, @C.S.Cameron.
Now I think there is information for the developers as well as for users
with similar hardware as yours.
See comments # 115,117-119,121,127.
Summary:
Computer : Gigabyte GB-BXi7-5775R
Processor : In
@ Norbert (nrbrtx),
You are welcome to systemize all our findings on public Google
Spreadsheet :-)
--
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 mana
@ C.S.Cameron,
Thanks for the details about the computer.
Please add the output of the following command to get info about the
graphics chip/card:
sudo lshw -C display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
@ C.S.Cameron,
It is strange that it works fine in BIOS mode but needs nomodeset in
UEFI mode. Something must fail to get activated in UEFI mode.
There are obvious problems with Ubuntu Groovy in this computer. Please
specify the details about it: Brand name and model of the computer
itself as wel
I tested the current daily Ubuntu Desktop Focal iso file (with a
persistent live system), and fractional scaling works with a 4k monitor,
where is used to fail. So I see a big improvement :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
@ C.S.Cameron,
What happens if you try with the same computer, iso file, and USB drive
as in comment #115 to make the USB drive persistent live with mkusb-dus
using
1. default settings,
2. usb-pack-efi,
and if you
3. *clone* from the iso file to the USB drive?
-o-
@ Steve Langasek (vorlon),
Now I tested the current Lubuntu Groovy iso file dated Sept 21. I could
repeat the results from yesterday: The Lubuntu iso file makes USB boot
drives, that can create a file system in the third partition, while the
Ubuntu Desktop and Xubuntu iso files (of the same date, Sept 21, fail to
do so.
--
Something has happened, that I discovered today: Lubuntu works.
I tested the current Groovy iso files of Ubuntu Desktop, Lubuntu and
Xubuntu.
- with the USB drives in used state (with various data, typically
leftovers after previous tests with live or persistent live systems)
- both in UEFI mode
mkusb version 12.6.1 (mkusb-dus) can create persistent live drives, that
boot both in BIOS mode and UEFI mode, also with secure boot from the
current daily Ubuntu Groovy iso file.
I used the setting 'usb-pack-efi'. This works also with a Lenovo V130 in
UEFI with secure boot, so there is a work-aro
- A Lenovo V130 finds the Linpus Lite boot option, but when selected it
skips directly to the internal drive's grub menu (with dual boot Ubuntu
and Windows). Back to square one.
- A Toshiba Satellite Pro C850 19w boots both in UEFI mode with *secure
boot* and in BIOS mode.
- An old Lenovo X131e w
I started testing with my Dell Precision M4800 with a 4th generation
Intel Core i7-4810MQ CPU, and its works
- to clone the current Ubuntu Groovy iso file to a USB drive and make
the Dell Precision M4800 boot both in BIOS mode and UEFI mode. See the
attached file :-)
- But there is no file system
This bug is still alive when tested with the current daily Ubuntu Groovy
iso file cloned to a USB drive and tested in a Dell Precision M4800.
This iso file is improved in many other ways, but this bug remains to be
fixed. Maybe there is some kind of race condition, that affects drives,
that were n
I can confirm that the current daily iso files make cloned USB drives
that
- boot in BIOS mode
- fail to boot UEFI mode (not even recognized as a bootable drive).
I tested the current daily Ubuntu iso file dated Sep 15 08:54
$ <<<'920c90aa90b81c48e6ef57c1579dcad97a168fc3e460b3cbdb6a096a0daadbbf
w--- 1 sudodus sudodus 1803091968 sep 12 02:07
xubuntu/groovy-desktop-amd64.iso
See the attached screenshot.
-o-
When cloned to a USB drive, this file does not boot in BIOS mode.
** Attachment added: "xubuntu-persistent-live.jpg"
https://bugs.launchpad.net/ubuntu-cdimage/+bug
I could reproduce the bug with today's daily Xubuntu Groovy iso file
(with the leftovers after testing yesterday's daily Lubuntu Groovy iso
fil in the 60 GB SSD, OCZ-AGILITY ITY3 drive).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have seen several cases, where bugs appear in situations typical for
end users, who want to install Ubuntu and Ubuntu family flavours in
their computers.
If I understand correctly, you have not seen these bugs in your internal
tests. Instead of testing only in virtual machines, I think at least
Sorry for the garbled list in 'details.txt', the non-standard characters
are not rendered nicely by Firefox. Here is a better list from this
computer:
lubuntu@lubuntu:~$ lsblk -lo name,fstype,label,size
NAME FSTYPE LABEL SIZE
loop0 squashfs 1.6G
sda
@ Steve Langasek (vorlon),
See Bug #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.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to b
Public bug reported:
When iso testing the current daily Lubuntu iso file (dated 2020-09-11),
I notice that a third partition is created (during the boot process),
but no file system is recognized by lsblk -f, and it is not used for
logging (as we are used to from Focal and previous versions of Gro
... minor correction: I used a small SSD connected via a USB to SATA
adapter instead of a pendrive because it is so much faster.
--
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
I tested also with plain extraction from the current Lubuntu Groovy iso
file to a FAT32 partition with what I think are the correct flags
$ LANG=C sudo parted /dev/sdc p
Model: OCZ-AGIL ITY3 (scsi)
Disk /dev/sdc: 60,0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
@ Leo,
I made an installed Lubuntu 20.04 LTS system in an HP Probook 6450b to
be up to date. This computer used to be my daughter's, but it is now
degraded to an occasional test computer for this kind of purpose. And I
double-checked the Groovy iso file with sha256sum:
$ <<<'43eff66f35b78b933b983
... The problem occurs only in BIOS mode. As before, it boots in UEFI
mode, where I get
"Check finished. No errors found"
and I reach to the desktop as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
@ Thomas Schmitt (scdbackup),
Thanks for chipping in and offering help :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895131
Title:
Groovy Desktop *BREAKS* the most common method of creating UE
@ Leo,
My experience is that cloning is cloning is cloning, whereever it is
done, as long as the cloning operation is done correctly, and it is not
too difficult. And the test of the files at boot indicates no error, so
I am rather confident.
Anyway, I can do the cloning elsewhere, in another com
I am working with these current iso files:
$ md5sum ../[lx]ubuntu/groovy-desktop-amd64.iso
5d4756194e6d917b45584a10109f8e0e ../lubuntu/groovy-desktop-amd64.iso
8ad63bfc247563dae765af648ea62b47 ../xubuntu/groovy-desktop-amd64.iso
and, Leo, I looked at the links provided by Steve.
Now a cloned U
I can find today's groovy iso files of lubuntu and xubuntu. But there
are no
groovy-desktop-amd64.iso
groovy-desktop-amd64.iso.zsync
files (only arm files). How come?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I can find today's groovy iso files of lubuntu and xubuntu. But there
are no
groovy-desktop-amd64.iso
groovy-desktop-amd64.iso.zsync
files (only arm files) for Ubuntu Desktop. How come?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@ Michael Hudson-Doyle (mwhudson),
Please let us know, when this change will be available for iso testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895131
Title:
Groovy Desktop *BREAKS* the m
@Akeo,
I have seen the problem that you address in this bug report, and I was
afraid that it may cause problems for you[r tool] and others who use
extracting methods. Thanks for speaking out load about it.
There is an additional problem too, that some computers do not even boot
from cloned drives
I can report progress: There are new compressed image files to be
extracted and cloned to USB drives for UEFI and BIOS mode, that can boot
also with secure boot in a computer updated to squash the boothole bug.
You find these image files at
https://phillw.net/isos/linux-tools/uefi-n-bios/?C=M;O=D
> We can't debug or support a boot entry that we can't examine.
I can understand that. I do hope that this "Linpus Lite" is a corner
case. Otherwise, if this kind of USB boot systems will get common in
UEFI mode, Ubuntu will have severe problems.
> When you say AHCI, do you mean UEFI? AHCI has no
@ Leó Kolbeinsson (leok),
Thanks for this heads up :-)
It was likely that an updated version of the BIOS system could fix this
issue. I did the BIOS update, and it was successful. The computer works
after the update :-)
But it did not fix this bug. The temporary boot option
"Linpus Lite ()"
is
@ Steve Langasek (vorlon),
According to your request I continue the dialogue about the Lenovo V130
issue at
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I attach a photo of the temporary boot menu to this comment too, so that
you need not skip between the bug reports.
I am almost 100% sure that no user has tampered with the boot settings
until yesterday, when I turned off first secure boot, then UEFI. The
boot menu option
"Linpus Lite ()"
was th
@ Steve Langasek (vorlon),
According to your request I continue the dialogue here about problems to
boot a Lenovo V130 in UEFI mode with the current daily Groovy iso files.
This problem was reported in comment #31
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/comments/31
- When I selec
I attach the output of mokutil to this comment too, so that you need not
skip between the bug reports.
** Attachment added: "mokutil-of-lenovo-v130.txt"
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+attachment/5407573/+files/mokutil-of-lenovo-v130.txt
--
You received this bug notif
... continuing:
This is when using the boot option in the temporary boot menu (F12)
"Linpus Lite ()"
in the picture attached to the previous comment. This is the only
available USB boot option in UEFI mode.
Then I turned off UEFI mode and set teh computer to boot in 'legacy
mode'. Now there wer
@ Steve Langasek (vorlon),
Previously I have not touched the UEFI/BIOS system of the *Lenovo V130*
that I have access to, but now, that you ask about it, I had better do
it in order to help identify what goes wrong, when trying to boot USB
drives cloned from Groovy ISO files.
When testing Groovy
The problem with the Lenovo V130 was reported at this bug
report/comment:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/comments/31
** Attachment added: "mokutil-of-lenovo-v130.txt"
https://bugs.launchpad.net/ubuntu/+source/cd-boot-images-amd64/+bug/1892754/+attachment/5407095/+fi
Thanks, this bug is squashed :-)
I can confirm that a USB drive cloned from the current daily Lubuntu iso
file boots in UEFI mode with secure boot in my Dell Precision M4800.
(This computer can also boot in UEFI mode without secure boot and in
BIOS mode with the current daily Lubuntu iso file.)
This bug affects the current Ubuntu Desktop Groovy iso file too (not
only Lubuntu).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
Unable to boot in UEFI+secure boot mode
To manage no
I tried again in the Lenovo V130, and this second time the internal UEFI
system is upgraded so that it no longer allows booting (not even when
the current daily Lubuntu Groovy iso file is used to create a persistent
live drive with mkusb (with the setting 'upefi', using 'usb-pack-efi').
So the bugf
Additional test results:
- As before, the Lenovo V130 can boot when the current daily Lubuntu
Groovy iso file is used to create a persistent live drive with mkusb
(with the setting 'upefi', using 'usb-pack-efi'). This indicates that
there is a security problem with grub.
- The Dell Precision M480
Need I say that the old failure mode is still there in a Lenovo V130:
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/comments/60
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892754
Title:
This bug affects my Dell Precision M4800 too.
A current daily Lubuntu Groovy iso file cloned to a USB drive works in
BIOS mode and UEFI mode without secure boot, but with secure boot I get
this message:
'Error: security violation'
and the boot process cannot continue.
I double-checked and a Foc
@leok,
When cloning works (in all computers and boot modes), we can consider
this bug as squashed.
When Rufus fails in its default mode, we can select 'dd-mode' which
means cloning, and the result should be identical to that of the Ubuntu
Startup Disk Creator and other cloning tools (Disks, mkusb
Now one of the failure modes is removed. Congratulations to the Ubuntu
developers and to guiverc :-)
I tested the current daily iso files cloned into USB drives
#perms sizedatetimefile-name
-rw--- 1,8G2020-07-17 17:09
"lubuntu/groovy-desktop-amd64
@guiverc,
I think you have confused leok's boxes with my boxes. Please modify the
summary @top.
I have tested this bug with a USB drive *cloned* from a Groovy daily iso
file in a
+ Dell Precision M4800 (and Dell Latitude E7240 - not reported before,
but behaves like the other Dell) - work now
+
Now that a new Lubuntu Groovy iso file is uploaded I tested it as well
as the current Focal iso file,
#perms sizedatetimefile-name
-rw--- 1,8G2020-07-13 16:53 "focal-desktop-amd64.iso"
-rw--- 1,8G2020-07-13 17:00 "groovy-desktop-
The boot performance of the Lubuntu Groovy iso file on my computers are
the same with today's current daily iso file,
#perms sizedatetimefile-name
-rw--- 1,8G2020-07-12 16:56 "groovy-desktop-amd64.iso"
as with the previous iso files. At least, I cou
The boot performance of the Ubuntu Groovy iso file on my computers are
the same with today's daily iso file,
#perms size date time file-name
-rw--- 2,6G 2020-07-10 08:27 "groovy-desktop-amd64.iso"
as with yesterday's iso file. At least, I could not see any difference.
Most of my computers boo
Trying to explain better:
The Lenovo V130 is set to boot in UEFI mode with secure boot. The
problem is that it cannot boot from a USB drive *cloned* from the
current Ubuntu Groovy iso file dated 2020-07-10 08:27.
Instead it skips to the internal drive and its grub menu (even when I
select the USB
The boot performance of the Ubuntu Groovy iso file on my computers are
the same with today's daily iso file,
#perms sizedatetimefile-name
-rw--- 2,6G2020-07-10 08:27 "groovy-desktop-amd64.iso"
as with yesterday's iso file. At least, I could not see
My Lenovo V130 does not boot from a cloned drive, and did not boot from
a persistent live drive by mkusb-dus. But with today's iso file, there
is progress. It boots into a persistent live system with the boot option
'upefi', usb-pack-efi, (and there is persistence). So another way to see
what works
Let us continue like this: *You* make the images 'more like the ones
from June', and *we* (iso-testers) test how it works in our computers.
I have a good experience from booting USB drives via grub also in BIOS
mode, so I think and hope that we can keep that feature. Via the link in
comment #26 yo
Cloned Groovy USB drives boot again, at least in some of my computers
:-)
+ I tested in my Dell Precision M4800 and it works as usual in UEFI mode
(and via grub) in BIOS mode.
- But the Lenovo V130 does not boot in UEFI mode and secure boot - When
I select the USB drive from the temporary menu, i
I found another mode in which the current groovy iso files make bootable
drives: 'grub-n-iso' alias isoboot. I can make a bootable USB drive that
boots
- both in UEFI and BIOS mode
- both live-only and persistent live
when booting into a 'grub template' and then into an iso file according
to the
Do you think this bug is somehow related to the following bug?
https://bugs.launchpad.net/bugs/1886148
For example, are there problems to boot into a live system from a USB
drive in a real system, or booted from a virtual hard disk drive with
the image in a virtual machine? (I know that it boots
I'm glad that there is work in progress, and I am willing to help
testing, whenever you have something 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/1886148
Title:
failure to boot groovy
Via this link:
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/213471/testcases
and its 'Link to the download information' you *should* be able to
download the relevant mini.iso file. That way I find #621, the same as
you refer to. But your results indicate that it is not upgraded from
f
@guiverc,
[Unfortunately for squashing this bug] I got rid of some old computers
when I moved to a smaller apartment last summer. My oldest 64-bit
computer now has an Intel i3 processor, and it is not affected by this
bug.
- Can you boot the current groovy mini.iso into the computers affected
by
@guiverc,
Yes, syslinux is not involved at all in persistent live drives by mkusb-
dus, so it is innocent.
Will you get more information, when you remove 'quiet splash' from the
linux line in grub?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Item 3 above concerns cloned live drives, that I think you have been
using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
To
@guiverc,
1. Apropos xnox's comment: You could create a persistent live drive with
mkusb. It boots via grub (not syslinux) also in BIOS mode. That way you
could make sure that it is not related to syslinux.
2. I have seen [the same or similar] complaints about missing optical
media recently, but
@robert key,
Please post a link here to that new bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863672
Title:
The 'new' persistent live method starting in 19.10 no longer works
To mana
@Wolf Pichler,
I understand that you write this comment because you want the Ubuntu
Startup Disk Creator to be improved.
But that you do not use it since the days of Trusty. At that time it was
an extracting tool with ability to create persistent live drives, and I
think it was buggy. In Ubuntu X
I can confirm that the bug is squashed in the current daily Ubuntu
desktop iso file
-rw--- 1 nio nio 2,6G maj 28 08:40 /media/multimed-2/test/ubuntu
/groovy-desktop-amd64.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
@ Jean-Baptiste Lallement,
Please explain what you mean by 'opinion':
- Are you not affected by this bug?
- Do you think that we should live with this bug?
- Should we wait a few more days to let the bug-fix reach the iso files?
- Or something else (in this case please specify)?
--
You recei
Today's daily iso files are still affected by this bug, for example
$ ls -l /media/multimed-2/test/ubuntu/groovy-desktop-amd64.iso
-rw--- 1 nio nio 2734686208 maj 26 11:28
/media/multimed-2/test/ubuntu/groovy-desktop-amd64.iso
--
You received this bug notification because you are a member o
This bug affects me too, and I want Swedish, which is not easy unless a
remember from previous versions 'where it is located genometrically'.
For some reason the language selection screen of syslinux boot is
rendered differently compared to what has been working for decades.
--
You received this
1. Maybe the bugfix is only addressing Groovy, which has casper 1.447
now.
2. It seems that the bugfix is only an update of the casper manpage
because the integrity check is still there for persistent live systems
unless I add the boot option
fsck.mode=skip
(tested in Lubuntu Groovy).
--
You r
@ C.S.Cameron,
> I will fill out a separate bug report when I get time.
Please post a link here to that separate bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback c
I have succeeded doing what you try to do, when I booted with the two
boot options 'toram' and 'nopersistent' (both at the same boot) with the
other Ubuntu flavours that use Ubiquity.
Installing with Calamares works for me (to install Lubuntu 20.04 LTS)
without the boot option 'toram', for example
After testing older versions of Ubuntu, it seems that 'fsck.mode=skip'
is simply ignored, and does not create any problem. So I have included
it in some of the menu entries for persistence and 'live-only to RAM'
created by mkusb version 12.4.7.
--
You received this bug notification because you ar
@ Brian Murray,
That is a good idea. I tested and it works with Focal Fossa :-)
What happens when we use the boot option 'fsck.mode=skip' for older
versions of Ubuntu (for example 18.04 LTS)? Will it cause some error or
simply be ignored?
--
You received this bug notification because you are a
I can confirm this bug. It appeared with Focal Fossa (does not affect
previous versions).
I suggest to store a small file in the partition with the label
'writable' or 'casper-rw', that tells the system that the live USB disk
check has been performed, and is no longer necessary.
--
You received
@ C.S.Cameron (cscameron),
I think I understand now. You can remove the boot option maybe-ubiquity
from the 'linux line' of grub.cfg:
from
menuentry "Ubuntu - persistent live" {
search --set=root --fs-uuid 2020-04-23-07-51-42-00
set gfxpayload=keep
linux ($root)/casper/vmlinuz
@ Michael Hudson-Doyle,
When booting a live system of Ubuntu 20.04 there is file and disk
checking.. Not just with Live USB but with Persistent USB also.
If not fast enough with ctrl-C it runs until over 80% complete. Very
irritating. If it was just a run once it would not be so bad.
Is there so
The cloning version of usb-creator introduced with Ubuntu Xenial (16.04
LTS) should work also in Trusty.
Other cloning tools work, so if you want to bother with this bug, I
suggest that you port that version to Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs
After further testing several times I think I pinned the problem:
The bug appears when booted 'toram'. With everything the same except the
the boot option 'toram', Calamares can install Lubuntu. So this is an
annoying glitch, but I think debugging it can wait until Lubuntu 20.04.1
LTS.
--
You re
** Description changed:
Booting in my 'standard test computer' a Toshiba laptop, Calamares
failed with the most basic mode, to use the whole drive for the new
Lubuntu installation.
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
Booted in BIOS mode. The par
Public bug reported:
Booting in my 'standard test computer' a Toshiba laptop, Calamares
failed with the most basic mode, to use the whole drive for the new
Lubuntu installation.
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
Booted in BIOS mode. The partition table in t
** Attachment added: "calamares-mount-failed.jpg"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1873950/+attachment/5357383/+files/calamares-mount-failed.jpg
** Description changed:
Booting in my 'standard test computer' a Toshiba laptop, Calamares
failed with the most basic mo
The package casper version 1.445 is bundled with the current Lubuntu iso
file dated 2020-04-09. I tested it (made a persistent live USB-connected
SSD) in one of my computers that were affected by this bug, the Toshiba.
Persistence works with the label 'casper-rw' :-)
So my alert in comment #62 can
Your observation is correct and I have seen it too. RAM is bigger and
processes are buffering in RAM more aggressively in recent computers
with recent versions of linux operating systems. Be aware that also
Windows uses this feature and for that reason you must 'remove the USB
drive safely' or your
By the way, today and during the weekend (Easter) 3 more persons are
testing your 'hack', capeer-initrd.gz. We have found a few more
computers that are affected by this bug, and your hack works in those
computers. You find some results via
https://ubuntuforums.org/showthread.php?t=2440260
So it l
It seems to me that the description of the bug-fix does not match this
bug.
Are you describing a fix for another bug, or is it only the description,
that is wrong or difficult to understand?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
... or like asking the US to change the name of the 'dollar' to
'valuable' ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863672
Title:
The 'new' persistent live method starting in 19.10 no long
Affects Focal Beta and current daily iso file (2020-04-07)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
Grub 2.04 Out of memory error, No server error
To manage notifications about
Please squash this bug before Ubuntu 20.04 LTS is released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
Grub 2.04 Out of memory error, No server error
To manage notifications about
I tested with the current casper-initrd with a current Lubuntu Focal
persistent live system, and it works with a 'casper-rw' partition also
in the computers where it did not work before as described in post #25:
1. a Toshiba laptop with an Intel i5 generaton 3 CPU (in BIOS mode and
UEFI mode)
htt
> I'm seeing "access beyond end of device" for /dev/sda and
> "I/O error while writing superblock" for /dev/sda2
> (peristent partition) on powerdown/reboot.
I can confirm this. I have tested in several computers and it happens in
all of them.
--
You received this bug notification because you ar
> So can we please revert support for 'writable' in 20.04, and use the next
> release to try to fix the issues with trying to support 2 partition labels?
...
> Again, unless you have confidence that you know precisely what the issue is,
> and should be able to fix it right now, I would advocate a
I tried (and failed) with the current Focal iso files of Ubuntu and
Lubuntu. Should I try with Ubuntu 19.10 or specifically with Ubuntu
Focal Beta?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863672
101 - 200 of 1166 matches
Mail list logo
