** Tags added: lubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959724
Title:
upgrading lubuntu groovy -> impish by reinstalling on existing LUKS
partition fails
To manage notifications
I considered, but did not attempt, these work-arounds:
1) Remove LuksBootKeyFileJob from calamares settings
2) temporarily move /boot to an unencrypted partition so that
LuksBootKeyFileJob would not proceed
3) temporarily move /home to another partition and let calamares reformat the
LUKS
Public bug reported:
The existing partition with LUKS / ext4 was created by installer during
installation of groovy from lubuntu live usb.
Last night, I attempted to upgrade by reinstalling to same partition,
hoping to preserve & update /home. /boot/efi is on a separate device,
not encrypted.
After reading a bunch of stuff on
https://github.com/fcitx/fcitx/issues/321, I deleted my HUGE (12GB)
history.dat file and restarted without the memory problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There is some terse fsck info being logged on my 14.04 Trusty desktop in
/var/log/upstart/mountall.log. Usually, it says something like this:
fsck from util-linux 2.20.1
grubboot: clean, 520/51200 files, 98181/204800 blocks
When I force checking by setting Maximum mount count to 1, it looks
