ubuntustudio-bugs team mailing list archive

[Aaron Rainbolt <1973469@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Test hardware is on an HP Elitebook 8570p, 16 GB RAM, 120 GB SSD.

My Elitebook has a hardware problem that requires that I detach the CMOS
battery and leave it that way in order for the system to function.
Additionally, if I shut the system down, I have to leave it unplugged
and with the battery removed, otherwise it won't boot when I go to turn
it on next. (I think a thunderstorm fried a capacitor that had something
to do with the CMOS, but anyway, weird as it may sound, that's the
problem with my computer.)

As a result, when I power my Elitebook on, it thinks that it's some time
in the year 2000, which is about 22 years off.

In addition, my Elitebook uses a Broadcom wireless chip, meaning that I
have to connect to the Internet via Ethernet in order to install the
driver for it. Since getting an Ethernet connection in my house is not
so easy, I chose to simply perform the installation offline.

At the very end of the installation, the installation failed, and I
received the following error message:

    External command finished with errors.

    Command apt-get update finished with exit code 100.
    Output:
    Ign:1 cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514) kinetic InRelease
    Hit:2 cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514) kinetic Release
    /bin/tar: libreoffice-calc_libreoffice-calc.png: time stamp 2022-05-03 18:02:43 is 1075359.205693822 s in the future
    /bin/tar: libreoffice-draw_libreoffice-draw.png: time stamp 2022-05-03 18:02:44 is 1075360.20555066 s in the future
    Reading package lists...
    E: Release file for cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514)/dists/kinetic/Release is not valid yet (invalid for another 18d 6h 51min 33s). Updates for this repository will not be applied.

The tar errors lead me to believe that this is a result of the out-of-
date clock on my system. Furthermore, after connecting to the Internet
to install the Broadcom drivers in the live environment and make the bug
report, my clock is up-to-date, and I was able to install the system
thereafter.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: calamares 3.2.41.1-0ubuntu5
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: wl
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.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.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.470
CurrentDesktop: LXQt
Date: Sun May 15 11:26:02 2022
LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:22.10.1
 calamares-settings-lubuntu       1:22.10.1
 xfsprogs                         5.13.0-1ubuntu3
 btrfs-progs                      5.16.2-1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug kinetic

-- 
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/1973469

Title:
  Lubuntu Kinetic installation crashes near the end on a system with a
  badly outdated clock

Status in calamares package in Ubuntu:
  New

Bug description:
  Test hardware is on an HP Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  My Elitebook has a hardware problem that requires that I detach the
  CMOS battery and leave it that way in order for the system to
  function. Additionally, if I shut the system down, I have to leave it
  unplugged and with the battery removed, otherwise it won't boot when I
  go to turn it on next. (I think a thunderstorm fried a capacitor that
  had something to do with the CMOS, but anyway, weird as it may sound,
  that's the problem with my computer.)

  As a result, when I power my Elitebook on, it thinks that it's some
  time in the year 2000, which is about 22 years off.

  In addition, my Elitebook uses a Broadcom wireless chip, meaning that
  I have to connect to the Internet via Ethernet in order to install the
  driver for it. Since getting an Ethernet connection in my house is not
  so easy, I chose to simply perform the installation offline.

  At the very end of the installation, the installation failed, and I
  received the following error message:

      External command finished with errors.

      Command apt-get update finished with exit code 100.
      Output:
      Ign:1 cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514) kinetic InRelease
      Hit:2 cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514) kinetic Release
      /bin/tar: libreoffice-calc_libreoffice-calc.png: time stamp 2022-05-03 18:02:43 is 1075359.205693822 s in the future
      /bin/tar: libreoffice-draw_libreoffice-draw.png: time stamp 2022-05-03 18:02:44 is 1075360.20555066 s in the future
      Reading package lists...
      E: Release file for cdrom://Lubuntu 22.10 _Kinetic Kudu_ - Alpha amd64 (20220514)/dists/kinetic/Release is not valid yet (invalid for another 18d 6h 51min 33s). Updates for this repository will not be applied.

  The tar errors lead me to believe that this is a result of the out-of-
  date clock on my system. Furthermore, after connecting to the Internet
  to install the Broadcom drivers in the live environment and make the
  bug report, my clock is up-to-date, and I was able to install the
  system thereafter.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: calamares 3.2.41.1-0ubuntu5
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .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.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:26:02 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:22.10.1
   calamares-settings-lubuntu       1:22.10.1
   xfsprogs                         5.13.0-1ubuntu3
   btrfs-progs                      5.16.2-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/1973469/+subscriptions