ubuntustudio-bugs team mailing list archive

[sudodus <2059907@xxxxxxxxxxxxxxxxxx>]

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 old HDD
or SSD.


This is not bug #1824021, because there is only zram swap.

lubuntu@lubuntu:~$ swapon
NAME       TYPE      SIZE USED PRIO
/dev/zram0 partition 5,8G   0B    5
lubuntu@lubuntu:~$ 

Here I interrupt when Calamares is at the partitioning page in order to
collect the current status of the live system and Calamares.

-o-

This is a repetition of what I did yesterday, when I exited from
Calamares and wiped the first mibibyte on the target drive. Yesterday,
after wiping I started Calamares again, and it could use the whole drive
and create an installed system.

So there is a workaround, but I think it would be better, if the user
would be offered to use the whole drive (and not only manual
partitioning). It can be implemented by wiping the first mibibyte, after
the user has selected the option to use the whole drive and confirmed an
extra question at a final checkpoint.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.4-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/calamares/modules/networkcfg/main.py]
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
 ---
 dontChroot: false
 timeout: 120
 firmwareType:
     "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.etc.calamares.modules.shellprocess_logs.conf:
 ---
 dontChroot: true
 timeout: 30
 script:
     - calamares-logs-helper ${ROOT}
.etc.calamares.modules.unpackfs.conf:
 ---
 unpack:
     -   source: "/cdrom/casper/filesystem.squashfs"
         sourcefs: "squashfs"
         destination: ""
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.494
CurrentDesktop: LXQt
Date: Mon Apr  1 13:13:01 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240328)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.16
 calamares-settings-lubuntu       1:24.04.16
 xfsprogs                         6.6.0-1ubuntu1
 btrfs-progs                      6.6.3-1.1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: calamares (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug noble

-- 
You received this bug notification because you are a member of Ubuntu
Studio Bugs, which is subscribed to calamares in Ubuntu.
https://bugs.launchpad.net/bugs/2059907

Title:
  missing option to erase and use the whole drive

Status in calamares package in Ubuntu:
  New

Bug description:
  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 old HDD
  or SSD.

  
  This is not bug #1824021, because there is only zram swap.

  lubuntu@lubuntu:~$ swapon
  NAME       TYPE      SIZE USED PRIO
  /dev/zram0 partition 5,8G   0B    5
  lubuntu@lubuntu:~$ 

  Here I interrupt when Calamares is at the partitioning page in order
  to collect the current status of the live system and Calamares.

  -o-

  This is a repetition of what I did yesterday, when I exited from
  Calamares and wiped the first mibibyte on the target drive. Yesterday,
  after wiping I started Calamares again, and it could use the whole
  drive and create an installed system.

  So there is a workaround, but I think it would be better, if the user
  would be offered to use the whole drive (and not only manual
  partitioning). It can be implemented by wiping the first mibibyte,
  after the user has selected the option to use the whole drive and
  confirmed an extra question at a final checkpoint.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: calamares 3.3.4-0ubuntu1 [modified: usr/lib/x86_64-linux-gnu/calamares/modules/networkcfg/main.py]
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  .etc.calamares.modules.after_bootloader_context.conf:
   ---
   dontChroot: false
   timeout: 120
   firmwareType:
       "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.fstab.conf:
   crypttabOptions: luks,keyscript=/bin/cat
   efiMountOptions: umask=0077
  .etc.calamares.modules.shellprocess_logs.conf:
   ---
   dontChroot: true
   timeout: 30
   script:
       - calamares-logs-helper ${ROOT}
  .etc.calamares.modules.unpackfs.conf:
   ---
   unpack:
       -   source: "/cdrom/casper/filesystem.squashfs"
           sourcefs: "squashfs"
           destination: ""
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.494
  CurrentDesktop: LXQt
  Date: Mon Apr  1 13:13:01 2024
  LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240328)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:24.04.16
   calamares-settings-lubuntu       1:24.04.16
   xfsprogs                         6.6.0-1ubuntu1
   btrfs-progs                      6.6.3-1.1
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

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