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 m
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 p
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 Lati
@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
@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 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 stu
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
HD(1,GPT,b3276a58-ea15-4cea-8c74-095b13ea7aa6,0x,0xefff1)/File(\EFI\ubuntu\shimx64.ef
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 *think* that this bug affects me too:
I am able to boot Lubuntu 18.10 in my Toshiba laptop with 64-bit
architecture both in UEFI and BIOS mode.
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
I used mkusb to create a persistent live drive (using default settings).
Mayb
More testing, this time also with Xubuntu 18.10, 32 bit.
1. Testing in my Toshiba laptop (link in my previous comment)
I needed the boot option nomodeset to get 'more than an underscore' on
the screen. Then the boot process of a *cloned* USB drive as well as a
persistent live USB drive (by mkusb)
More testing, this time also with Xubuntu 18.10, 32 bit.
Testing in my Dell laptop
https://www.cnet.com/products/dell-precision-mobile-
workstation-m4800-15-6-core-i7-4810mq-8-gb-ram-256-gb-ssd-english/specs/
Lubuntu 18.10, 32 bit:
The persistent live USB drive (by mkusb) boots and runs without
More testing, this time also with Xubuntu 18.10, 32 bit.
1. Testing in my Dell laptop
https://www.cnet.com/products/dell-precision-mobile-
workstation-m4800-15-6-core-i7-4810mq-8-gb-ram-256-gb-ssd-english/specs/
Lubuntu 18.10, 32 bit:
The persistent live USB drive (by mkusb) boots and runs with
I add a couplt of text files with output explaining what is different
between the working version and the no longer working version of Lubuntu
Focal Fossa. First the working one from Febr.12.
** Attachment added: "lubuntu-2020-02-12-17-00-33-00-persistent-live.txt"
https://bugs.launchpad.net/u
And then the no longer working version from Febr.16
** Attachment added: "lubuntu-2020-02-16-17-16-24-00-not-persistent-live.txt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+attachment/5329077/+files/lubuntu-2020-02-16-17-16-24-00-not-persistent-live.txt
--
You received th
Public bug reported:
I am iso-testing Focal Fossa and I am creating and maintaining tools to
create live and persistent live USB drives. Lubuntu Focal daily live
dated 2020-02-12 works. But the current version of Lubuntu Focal dated
2020-02-16 (zsynced approx. one hour ago) does not work when usin
Strange results from the continued testing:
The Xubuntu iso file dated 2020-02-17 01:04 fails too (like the
Lubuntu iso filefrom Febr.16)
The Ubuntu iso file dated 2020-02-1707:50 succeeds (there is
persistence with this method)
Lubuntu is updated:
The Lubuntu iso file dated 2020-02-17
The Lubuntu iso file dated 2020-02-17 17:40 fails too. I added
casper.log from this one, with the boot options persistent and verbose.
The live drive is still the same in my Toshiba laptop, where I run the
tests: /dev/sdc.
** Attachment added: "casper.log"
https://bugs.launchpad.net/ubuntu/+s
Here is the logfile for the boot options writable and verbose (Lubuntu
still failing). Do you want results from the working Ubuntu with the
same date? That way we might help the developers of Lubuntu and Xubuntu
(and maybe also the other community flavours, that I have not tested).
** Attachment a
and a file corresponding to the file in comment #2
** Attachment added: "lubuntu-2020-02-17-18-40-46-00.txt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+attachment/5329097/+files/lubuntu-2020-02-17-18-40-46-00.txt
--
You received this bug notification because you are a mem
and a file corresponding to the file in comment #2
** Attachment added: "lubuntu-2020-02-17-18-40-46-00_label-writable_works.txt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+attachment/5329099/+files/lubuntu-2020-02-17-18-40-46-00_label-writable_works.txt
--
You received t
Sorry for the misunderstanding alias careless reading of your
instructions. I got it now, and Lubuntu works, when I modified the label
to 'writable' (and kept the boot option persistent). To make things
complete I will give you the log file for this case too.
** Attachment added: "casper.log2"
So it seems to me that the problem for the community flavours is the
label. The are not accepting the old casper-rw. By the way, what about
home-rw. Will it be recognized by this new version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
No I don't know how to make changes to the initramfs in a live system. I
have done it in an installed system long ago, and can follow
instructions, at least when I am not too tired :-P
So that is one possibility.
The other one is that you install and use mkusb-plug according to this
link (either
@C.S.Cameron,
Thanks for testing mkusb including the combo "writable & home-rw" :-)
I will wait a while to see if 'casper-rw' will be revived (alongside
'writable') in Focal, or if I have to make a check for the version of
Ubuntu or casper in my programs to select between 'casper-rw' and
'writabl
I did both testcases. There was no error detected in in testcase #1, and
no error detected in testcase #2, so things seem to work :-)
Details:
- There was a test installation of Ubuntu 18.04.1 LTS in a Toshiba laptop with
an SSD.
- I cloned a Lubuntu 18.10 iso file to a USB pendrive and installe
I installed e2fsprogs 1.44.4-2 via cosmic-proposed, according to the
instructions.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bu
Public bug reported:
This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
days ago (Oct 6).
Now there is a delay of 1 min 30 sec during booting, and I think there
is something wrong with the recognition of the wifi hardware or maybe
matching of driver and hardware. It happens in '
attached what I think are relevant lines from 'syslog'
** Attachment added: "relevant lines from 'syslog'"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+attachment/5297468/+files/temp.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I had also an Ubuntu Eoan iso file from Sept 25 and got a new one now.
Both boot fast, but do not behave in the same way. The current Ubuntu
sends a notify message to the desktop:
"Network service discovery disabled
Your current network has a .local domain, which is not recommen..."
This notice i
attached photo showing the waiting
** Attachment added: "lubuntu-waiting-90s.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848333/+attachment/5297779/+files/lubuntu-waiting-90s.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** This bug is a duplicate of bug 1848404 ***
https://bugs.launchpad.net/bugs/1848404
I can confirm this bug, tested in a Toshiba laptop
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
I booted without 'quiet splash" and noted a delay for 1 min 30 seconds.
Could thi
** Description changed:
This problem is rather new. It did not affect Lubuntu Eoan zsynced 9
days ago (Oct 6).
Now there is a delay of 1 min 30 sec during booting, and I think there
is something wrong with the recognition of the wifi hardware or maybe
matching of driver and hardware.
When booting live, there is a delay of 1 min 30 seconds (tested in
Kubuntu, Lubuntu and Xubuntu, but not in standard Ubuntu. It can be seen
when booted (live) without 'quiet splash'.
I think the delay is caused by the logic concerning wifi, and I suspect
that it is connected to the issue of this b
@adconrad,
The bug is very real, but I can understand, that it is not located in
ubiquity. Please advice which program package to 'blame next', in other
words, where you think that the bug is located.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Maybe this bug is located in casper (like 1848404)
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848333
Title:
wifi problem delays b
This bug is squashed in the current Lubuntu final iso file eoan-desktop-
amd64.iso dated Oct 17 12.51 :-)
So it was another manifestation of the bug
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1848404
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
I hoped that you (the developers) had upgraded casper in 18.04.4 LTS.
But if it is too late for that, I ask you to prepare the the upgrade
well in time for 18.04.5 LTS.
I am willing to test that the iso file works correctly, both 'as usual'
and to create persistent live drives using the new featur
the
content of the files /.disk/info and /.disk/mini-info.
These are present in Ubuntu, Debian and many but not all respins. The
funny thing is that the difference between Debian 10.2 and Kali is a
trailing line feed. I checked with Debian 8.8. It contains a newline and
is accepted by the Star
@ Michael Hudson-Doyle, @ Olivier Robert,
What do you think of the following idea for Ubuntu Focal Fossa?
It is possible to add the boot option
- 'persistent' in order to create a persistent live drive
or
- 'nopersistent' in order to create a live-only drive.
I am looking for a method to edit
@@ Michael Hudson-Doyle, @ Olivier Robert, and everybody else who is
interested,
I suggest a simple method to prepare the iso files for binary editing
without 'sacrificing' anythng.
Since repeated spaces are collapsed into one space by Launchpad's
comment editor, I will provide the man content of
@ Michael Hudson-Doyle, @ Olivier Robert, and @ everybody else who is
interested,
I suggest a simple method to prepare the iso files for binary editing
without 'sacrificing' anythng.
Since repeated spaces are collapsed into one space by Launchpad's
comment editor, I will provide the man content o
You may want to participate in the following thread,
https://discourse.ubuntu.com/t/make-it-easy-to-create-a-persistent-as-
well-as-live-only-usb-live-drive/13671
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Yes, this bug has returned after several years. I suspect that there is
a race condition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/966480
Title:
The prompt asking for media removal is not shown
I can confirm that this bug affects me too (both in UEFI mode and 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/1869928
Title:
Ubuntu Studio 20.04 ISO Boot Issue
To manage notifications
> I noticed that the version of casper has changed from 1.438build1
(when it worked) to 1.439 so I > suspect that this has caused the
failure.
Today I tested the Lubuntu Focal daily iso file with caxper version
1.441. It is still affected by this bug: There is no persistence with
the label 'casper
@Michael Hudson-Doyle,
The bug might not appear in your VM.
I think a very very detailed instruction to do what I did is to
1. Work in *buntu 18.04.x LTS which is updated and full-upgraded to be
up to date
2. Install mkusb-plug according to comment #14
3. zsync any current Ubuntu desktop Focal
typing error in the previous comment:
change 'after re-labeling the drive to 'writable' and reboot'
to 'after re-labeling the partition for persistence to 'writable' and reboot'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
@Michael Hudson-Doyle,
After some more testing I have to add some (maybe confusing, maybe
helpful) information:
A - The bug appears in
1. a Toshiba laptop with an Intel i5 generaton 3 CPU (in BIOS mode and
UEFI mode)
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
This
Quiet is always removed when persistent live by mkusb-plug because
'quiet splash' is replaced by 'persisstent '. Anyway, I ran the same
Xubuntu Focal system, that I tested according to comment #25 in the
Toshiba laptop
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
in U
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+attachment/5332775/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863672
@Michael Hudson-Doyle,
Why have you changed to 'writable' as the primary label of the partition
for persistence?
How committed are you to use 'writable' instead of 'casper-rw'?
By the way, are you aware of the current Debian corresponding label,
'persistence'? Debian uses the boot option 'persis
Public bug reported:
Running the debian installer of Lubuntu Xenial amd64, there was this
information:
Window: Debootstrap warning: Failure while configuring required packages
At screen #4: debootstrap: dpkg: error --install needs at least one
package archive file argument
New window: Failure t
Public bug reported:
While trying to install from the Lubuntu 16.04 LTS alternate amd64 daily
iso file, the target drive is not found when connected via USB 3.
This happens with an SSD connected via USB 3. The corresponding desktop
iso file works, and the released Lubuntu 16.04 LTS alternate amd6
Commands illustrating how the target drive is recognized by the desktop
system.
** Attachment added: "commands.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1596281/+attachment/4690472/+files/commands.txt
--
You received this bug notification because you are a member of Ubuntu
Bu
** Summary changed:
- the target drive is not found when connected via USB 3
+ the target drive is not found when connected via USB 3 while installing
Lubuntu alternate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
I continued testing the problem with
- the released version lubuntu-16.04-alternate-amd64.iso
- another adapter/box to connect the SSD via USB 3.
And this is the result:
This (new) adapter, Deltaco USB 3.0 to SATA II cable fails also with the
released version, so it is an old bug.
An (older) A
I'll try, but I am a total newbie concerning new or non-standard
kernels, so I'm not sure it will work for me :-P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596281
Title:
the target drive is not
@ Joseph Salisbury (jsalisbury),
I have been trying to think.
- I don't think it helps with a new kernel, because Lubuntu desktop of
the corresponding daily-live iso file works (can identify the drive via
that USB 3 adapter). See post #4.
- It would be very hard for me to create an alternate iso
@ Joseph Salisbury (jsalisbury),
I have been trying to think.
- I don't think it helps with a new kernel, because Lubuntu desktop of
the corresponding daily-live iso file works (can identify the drive via
that USB 3 adapter). See post #4.
- It would be very hard for me to create an alternate iso
Both.
I discovered it testing Xenial, but it appears also today, when I'm
testing Yakkety.
You may edit the tags accordingly. (I usually avoid editing tags and
leave it to people more involved in the administration.)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
At least in Swedish, the slideshow states '16.04' instead of '16.10'
This is a cosmetic bug.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.3
ProcVersionSignature: Ubuntu 4.4.0-27.46-generic 4.4.13
Uname: Linux 4.4.0-27-generic i686
ApportVersion: 2.20.
I agree with peerus (comment #139). I suspect that this bug is related
to another program package, but I do not know enough to be able to
suggest which package.
I have problems with graphics with a non-intel graphics chip. It turns
pale (almost completely greyed out), and after switching to anothe
Please fix this bug in Xenial preparing for the first point release,
16.04.1 LTS.
I checked the current daily iso file,
-rw--- 856M2016-06-30 16:42 "xenial-
desktop-i386.iso"
$ md5sum xenial-desktop-i386.iso
43249c865a5e5fb9441e835b76234a0b xenial-desktop-i386.iso
and 'xser
This bug makes it impossible to use
xenial-alternate-i386.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1596279
Title:
failure while configuring required package while installing Lubuntu
alte
I tried to test the corresponding Ubuntu Xenial mini.iso (tried to
update July 1, but still old)
wget
http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-i386/20101020ubuntu451/images/netboot/mini.iso
#perms sizedatetimefile-name
-rw-rw-r-- 48M 2016-
typing error:
wrote: So it seems the bug resides in some Lubuntu package and makes
debootstrap file.
right: So it seems the bug resides in some Lubuntu package and makes
debootstrap fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Public bug reported:
It works in the same computer running in BIOS mode, but failed in UEFI
mode
Running command ['umount', '/target/dev'] with allowed return codes [0]
(capture=False)
finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: FAIL: curtin
command curthooks
Extracting tools can be affected by this "gfxboot.c32: not a COM32R
image" bug. It is a problem of the tool to create the USB boot drive,
and should be fixed by the developer of that particular tool.
-o-
Cloning tools are not affected by this bug. You can use Ubuntu's Startup
Disk Creator alias u
OK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766286
Title:
curtin.util.ProcessExecutionError: Unexpected error while
running command. Command: ['sh', '-c', 'exec "$0" "$@" 2>&
Sorry, it is still failing.
Is the following iso file the correct one to use?
$ md5sum bionic-live-server-amd64.iso
70051f7b2125674f1821e7d7674f1609 bionic-live-server-amd64.iso
$ ls -l bionic-live-server-amd64.iso
-rw--- 1 nio nio 845152256 apr 24 06:57 bionic-live-server-amd64.iso
** At
The install iso does not contain any shim-signed package, and it refers to a
previous candidate. Maybe I should wait for the next iso file?
---
$ apt-cache policy shim-signed
shim-signed:
Installed: (none)
Candidate: 1.34.6+13-0ubuntu2
Version table:
1.34.6+13-0ubuntu2 500
500 c
@Ken T (professorsnapper),
Which version of *ubuntu are you running, when you create your USB boot
drives? Is it a version before 16.04 LTS? In that case I think there is
an old and buggy version of the Startup Disk Creator, that you should
avoid :-)
A new robust *cloning* version of the Startup
The current iso file
$ md5sum bionic-live-server-amd64.iso
88bae72a9047534b129b3d3d0d33 bionic-live-server-amd64.iso
$ ls -l bionic-live-server-amd64.iso
-rw--- 1 nio nio 845152256 apr 25 04:00 bionic-live-server-amd64.iso
is better. The installer finishes and exclaims "Installation comp
Public bug reported:
At LVM with encryption, there is no text telling to enter the passphrase
in the boxes, at least not when using Swedish. This is illustrated with
the attached screenshot.
No showstopper, but I think this makes it hard for a beginner, and I
suggest that it can be fixed before t
** Description changed:
- At LVM with encryption, there is no text telling to enter the passphrase
- in the boxes, at least not when using Swedish. This is illustrated with
- the attached screenshot.
+ Installing Kubuntu Bionic 32bit (i386), at LVM with encryption, there is
+ no text telling to en
** Description changed:
Installing Kubuntu Bionic 32bit (i386), at LVM with encryption, there is
no text telling to enter the passphrase in the boxes, at least not when
- using Swedish. This is illustrated with the attached screenshot.
+ using Swedish. This is illustrated with the attached scr
Public bug reported:
This may or may not be the same bug as #1754174 (but is tested in the
32-bit version (i386) of Lubuntu)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.4
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic i686
ApportV
Testing now in Lubuntu beta 2: this bug is still alive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754646
Title:
Texts in the dialogue in Swedish is faulty in Lubuntu alternate Bionic
beta 1
The bug persists in Ubuntu Server beta 2 tested with bionic-server-
amd64.iso in a Toshiba laptop, http://www.toshiba.se/laptops/satellite-
pro/c850/satellite-pro-c850-19w/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/lubuntu-meta/+bug/1763611/+attachment/5113463/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763611
Titl
Public bug reported:
See this thread at the Ubuntu Forums:
https://ubuntuforums.org/showthread.php?t=2388799
How come the ultra light Lubuntu Bionic needs 40 seconds from the grub
menu to the log in screen, while the corresponding Kubuntu and Xubuntu
Bionic can do it in 10 seconds in my Toshiba
@Steve Langasek (vorlon),
I agree, that there is not enough evidence to be sure. But how come it
makes a difference, when I replace the new SSD with 4096 bytes physical
sectors with an older SSD (same size and brand name) with 512 bytes
physical sectors? If not an SSD issue, could it be a file sys
Correction of the previous post (about hybrid iso files)
This has been a standard for iso files that can be cloned to CDs, DVDs
and USB drives *during several years, at least since Ubuntu 12.04 LTS*.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
The problem is that some tools do not recognize the hybrid iso file's
internal structure when cloned to a USB drive. This has been a standard
for iso files that can be cloned to CDs, DVDs and USB drives (actually
any mass storage drives including memory cards SSDs and HDDs).
The Ubuntu Startup Dis
Public bug reported:
I get 'xterm+thai' via 'ctrl+alt+t' in Lubuntu Bionic. But the good old
LXterminal is available via the menu. And LXterminal works much better
with various languages, for example Swedish.
This bug affects the live session as well as installed systems in
Lubuntu.
ProblemType:
Testing on bare metal in my Toshiba laptop
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
I can install Lubuntu via a USB live system cloned from the current
bionic-desktop-amd64.iso file, if I select 'Try Lubuntu'.
But the installer fails, if I select 'Install Lubuntu'
I can confirm this bug in Lubuntu Bionic installed from the daily iso
file 'bionic-desktop-amd64.iso'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706701
Title:
Default Keyring is not unlocked fo
*** This bug is a duplicate of bug 1712089 ***
https://bugs.launchpad.net/bugs/1712089
@david braun,
1. Please notice that this bug report is a duplicate of bug #1712089.
The developers will probably focus on that bug report, not this one.
2. See this link for more details on how to work aro
mkusb can boot from grub 2.04 when pointing to a partition, into which
you have cloned from the iso file (so with an iso 9660 file system). The
problem is specifically that it does not work in UEFI mode, when grub
points to an iso file.
--
You received this bug notification because you are a memb
You are right (and you were right also in comment #12). I only wanted to
make it clear for the developers what works and what does not work.
--
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
@ C.S.Cameron,
While you are testing, please try with usb-pack-efi too. I think it
should make things work, where there are problems now.
(It is still important to squash this bug, but usb-pack-efi might be a
workaround for people using mkusb as a foundation for iso booting.)
--
You received th
@ C.S.Cameron,
Yes, I think it is enough with a single test. Please tell us the result
of your test when usb-pack-efi is selected in the settings menu of
mkusb. Will it make a difference in order to make it possible to boot
into an iso file?
--
You received this bug notification because you are
This is actually going back to my original usage of usb-pack-efi, that
is described in post #6 and the following posts of this thread at the
Ubuntu Forums,
https://ubuntuforums.org/showthread.php?t=2259682&p=13300523#post13300523
This grub system works in UEFI and BIOS mode. It is developed from
@Michael Hudson-Doyle,
I'm glad that you are reading this :-)
An alternative, that I can see beyond editing the whole iso file:
- Add a menuentry in the iso file. This menuentry should have the boot
option 'persistent' alongside the other boot options. So there would be
two standard boot options
Which virtual keyboard have you been testing, 'onboard' or 'caribou'? Or
both? I do not see information about it, sorry if it written somewhere
and I just did not check well enough.
My experience is that onboard is better.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
I tested to use a ppa because I wanted to test if mkusb will work in
focal. But
add-apt-repository
does not work.
---
lubuntu@lubuntu:~$ sudo add-apt-repository ppa:mkusb/ppa # existing ppa
Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 107,
That was really fast response, or I think a bugfix independent of my bug
report. Anyway, in the recently zsynced new daily iso file
add-apt-repository
works in Lubuntu focal :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Adding some text files
** Attachment added: "ubuntu-focal-live-cloned_before-it-is-used.txt"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5302435/+files/ubuntu-focal-live-cloned_before-it-is-used.txt
--
You received this bug notification because you are a member
Adding screenshot from Focal Fossa
(I had to stop and start the graphical desktop environment from a text
screen to make it responsive, but that is another problem, I think not
related to the bug reported here.)
** Attachment added: "ubuntu-focal-live-cloned_creates-n-mounts-casper-rw.png"
ht
Public bug reported:
It is very good that it is easy to create and use a casper-rw partition
to run Ubuntu persistent live in the versions 19.10 and Focal Fossa, and
that it is even created automatically, when there is unallocated drive
space behind the used part in a live drive.
But I think the
1 - 100 of 1166 matches
Mail list logo
