| 2019-11-03 11:44:12 |
sudodus |
bug |
|
|
added bug |
| 2019-11-03 11:49:06 |
sudodus |
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 |
|
| 2019-11-03 11:50:46 |
sudodus |
attachment added |
|
output of text mode commands via 'script' (file typescript) https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5302436/+files/typescript.txt |
|
| 2019-11-03 11:52:17 |
sudodus |
attachment added |
|
ubuntu-19.10-live-cloned_creates-n-mounts-casper-rw.png https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5302437/+files/ubuntu-19.10-live-cloned_creates-n-mounts-casper-rw.png |
|
| 2019-11-03 11:54:49 |
sudodus |
attachment added |
|
ubuntu-focal-live-cloned_creates-n-mounts-casper-rw.png https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5302438/+files/ubuntu-focal-live-cloned_creates-n-mounts-casper-rw.png |
|
| 2019-11-03 11:58:58 |
sudodus |
description |
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 system for doing that is 'too eager'. Maybe it is a feature that is left from the development and debugging phase.
- It would be enough (best), if the casper-rw partition is created only when it is needed, that is when the live system is booted with the boot option 'persistent'.
- We (I am talking for users who like persistent live drives) can accept that the casper-rw partition is created even when the drive is booted live only (without the boot option 'persistent').
- But we think it is a bug, that the live-only system is also mounting the casper-rw partition on the mount point /var/log and keeps it busy so that it cannot be unmounted.
This way the drive is not really live-only, and it is not possible to manage the drive space behind the system in an independent way. For example, it is not possible to detach the drive by using the boot option 'toram', and it is not possible to repair the casper-rw partition when running live in the same drive. It will be necessary to have two linux systems to do such tasks.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: casper 1.428
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
CasperVersion: 1.428
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 3 11:15:29 2019
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191103)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=sv_SE.UTF-8
SHELL=/bin/bash
SourcePackage: casper
UpgradeStatus: No upgrade log present (probably fresh install) |
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 system for doing that is 'too eager'. Maybe it is a feature that is left from the development and debugging phase.
- It would be enough (best), if the casper-rw partition is created only when it is needed, that is when the live system is booted with the boot option 'persistent'.
- We (I am talking for users who like persistent live drives) can accept that the casper-rw partition is created even when the drive is booted live only (without the boot option 'persistent').
- But we think it is a bug, that the live-only system is also mounting the casper-rw partition on the mount point /var/log and/or /var/crash and keeps it busy so that it cannot be unmounted.
This way the drive is not really live-only, and it is not possible to manage the drive space behind the system in an independent way. For example, it is not possible to detach the drive by using the boot option 'toram', and it is not possible to repair the casper-rw partition when running live in the same drive. It will be necessary to have two linux systems to do such tasks.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: casper 1.428
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
CasperVersion: 1.428
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 3 11:15:29 2019
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191103)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=sv_SE.UTF-8
SHELL=/bin/bash
SourcePackage: casper
UpgradeStatus: No upgrade log present (probably fresh install) |
|
| 2019-11-03 13:00:05 |
Ubuntu QA Website |
tags |
amd64 apport-bug focal |
amd64 apport-bug focal iso-testing |
|
| 2019-11-05 06:35:17 |
Launchpad Janitor |
casper (Ubuntu): status |
New |
Confirmed |
|
| 2019-11-05 07:20:05 |
sudodus |
bug |
|
|
added subscriber Chris Guiver |
| 2019-11-05 07:20:48 |
sudodus |
bug |
|
|
added subscriber C.S.Cameron |
| 2019-11-13 08:28:24 |
Launchpad Janitor |
casper (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2019-11-14 08:32:24 |
sudodus |
attachment added |
|
casper_1.432_fixes_bug_1851123_in_focal_daily_iso_file.png https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5305326/+files/casper_1.432_fixes_bug_1851123_in_focal_daily_iso_file.png |
|
| 2019-12-16 09:22:09 |
sudodus |
attachment added |
|
simple-method-to-prepare-iso-file-for-binary-edit.txt https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5312870/+files/simple-method-to-prepare-iso-file-for-binary-edit.txt |
|
| 2019-12-16 11:07:04 |
sudodus |
attachment added |
|
simple-method-to-prepare-iso-file-for-binary-edit.txt https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+attachment/5312897/+files/simple-method-to-prepare-iso-file-for-binary-edit.txt |
|
