Keepassxc re-installation gives errors

New to Debian (Or Linux in general)? Ask your questions here!
Post Reply
Message
Author
Budgie
Posts: 31
Joined: 2007-06-17 14:50

Keepassxc re-installation gives errors

#1 Post by Budgie »

Running Debian GNU/Linux 10 with KDE Plasma Version 5.14.5, KDE Framework Version 5.54.0, Qt Version 5.11.3 with kernel 4.19.0-14-amd64.

I have been getting notices from my installation of Keepass that it is out of date so first went to check with synaptic. All seemed OK but I thought I would re-install it and this has thrown up errors I was not expecting and do not understand:-

First I had the following error:-

Code: Select all

E: initramfs-tools: installed initramfs-tools package post-installation
script subprocess returned error exit status 1

When I looked at the details I had this:-

Code: Select all

debconf: unable to initialize frontend: Gnome
debconf: (Can't locate Gtk3.pm in @INC (you may need to install the Gtk3
module) (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at
/usr/share/perl5/Debconf/FrontEnd/Gnome.pm line 151, <> line 1.)
debconf: falling back to frontend: Dialog
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
(Reading database ... 247198 files and directories currently installed.)
Preparing to unpack .../keepassxc_2.3.4+dfsg.1-1_amd64.deb ...
Unpacking keepassxc (2.3.4+dfsg.1-1) over (2.3.4+dfsg.1-1) ...
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Setting up keepassxc (2.3.4+dfsg.1-1) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for shared-mime-info (1.10-1) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-14-amd64
pigz: abort: write error on <stdout> (No space left on device)
E: mkinitramfs failure cpio 141 pigz 28
update-initramfs: failed for /boot/initrd.img-4.19.0-14-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up initramfs-tools (0.133+deb10u1) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-14-amd64
pigz: abort: write error on <stdout> (No space left on device)
cpio: write error: Broken pipe
E: mkinitramfs failure cpio 2 pigz 28
update-initramfs: failed for /boot/initrd.img-4.19.0-14-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess
returned error exit status 1
Errors were encountered while processing:
 initramfs-tools

I saw the reference to the Gtk3 module so tried to install it but this resulted in the same errors.
I have checked the efi partition and it is virtually empty.
I seek advice as I am well beyond my own know how.

Dai_trying
Posts: 960
Joined: 2016-01-07 12:25

Re: Keepassxc re-installation gives errors

#2 Post by Dai_trying »

E: mkinitramfs failure cpio 141 pigz 28
update-initramfs: failed for /boot/initrd.img-4.19.0-14-amd64 with 1.
/boot is not (usually) in your efi partition, I would guess that "df -h" might show where your space is lacking (my bet is on /)

Budgie
Posts: 31
Joined: 2007-06-17 14:50

Re: Keepassxc re-installation gives errors

#3 Post by Budgie »

You are correct. This is what I have:-

Code: Select all

alastair@x3400debian:~$ df -h
Filesystem                        Size  Used Avail Use% Mounted on
udev                              7.8G     0  7.8G   0% /dev
tmpfs                             1.6G  9.5M  1.6G   1% /run
/dev/mapper/x3400debian--vg-root   23G  6.9G   15G  32% /
tmpfs                             7.9G   27M  7.9G   1% /dev/shm
tmpfs                             5.0M  4.0K  5.0M   1% /run/lock
tmpfs                             7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda2                         237M  200M   25M  90% /boot
/dev/mapper/x3400debian--vg-var   9.2G  2.9G  5.9G  33% /var
/dev/sda1                         511M  5.2M  506M   1% /boot/efi
/dev/mapper/x3400debian--vg-tmp   1.8G  5.7M  1.7G   1% /tmp
/dev/mapper/x3400debian--vg-home  2.7T   32G  2.5T   2% /home
tmpfs                             1.6G   16K  1.6G   1% /run/user/1000
pCloud.fs                         2.0T  399G  1.7T  20% /home/alastair/pCloudDrive
Looks like I have some housekeeping to do. Any suggestions?

Budgie
Posts: 31
Joined: 2007-06-17 14:50

Re: Keepassxc re-installation gives errors

#4 Post by Budgie »

I am not sure what I am looking at and it seems that from the outset I have made a mistake with my hardware configuration. This is what I have:-

Code: Select all

alastair@x3400debian:~$ sudo sfdisk -l
Disk /dev/sda: 2.7 TiB, 2996997980160 bytes, 5853511680 sectors
Disk model: ServeRAID M5014 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 30CDCA3E-F4CD-4A5D-90C4-1120ABF2E3F8

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    1050623    1048576  512M EFI System
/dev/sda2  1050624    1550335     499712  244M Linux filesystem
/dev/sda3  1550336 5853509631 5851959296  2.7T Linux LVM






Disk /dev/mapper/x3400debian--vg-root: 23.3 GiB, 24998051840 bytes, 48824320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-swap_1: 16 GiB, 17163091968 bytes, 33521664 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-var: 9.3 GiB, 9999220736 bytes, 19529728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-tmp: 1.9 GiB, 1996488704 bytes, 3899392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-home: 2.7 TiB, 2942044209152 bytes, 5746180096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
alastair@x3400debian:~$ 
I thought I had set up a root partition of 40 GB, a swap of 2 GB and /home for "the rest."
This is not what I believe I am looking at it seems my root is only 20GB.

I need a plan to sort this out. I had been thinking of using gparted and expanding the root partition. Is this the way to go and meanwhile what should I delete to make room as I cannot even install gparted yet!!! Grateful for advice please.

User avatar
Head_on_a_Stick
Posts: 13450
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Keepassxc re-installation gives errors

#5 Post by Head_on_a_Stick »

Either move /boot to the root partition or remove some old kernels. Is your root partition encrypted? If so then I think you'll have to reconfigure GRUB to get it working with an encrypted /boot partition. Ask the interweb about that because I have no idea.

Use this to check which kernel ABI versions are installed:

Code: Select all

aptitude search '?narrow(?installed, linux-image)'
If v4.19.0-14 works then you can remove any older version but be sure to keep the linux-image-amd64 metapackage.
Black Lives Matter

Debian buster-backports ISO image: for new hardware support

User avatar
stevepusser
Posts: 12408
Joined: 2009-10-06 05:53
Has thanked: 7 times
Been thanked: 5 times

Re: Keepassxc re-installation gives errors

#6 Post by stevepusser »

If the problem is the old KeepassXC:

The current release is 2.6.4

The current upstream Debian version is 2.6.2.

The current version in buster-backports is 2.5.4.

The current Buster version is 2.3.4.

Why would one think reinstalling 2.3.4 is going to get rid of that update nag doesn't make any sense to me.


Anyway, I do maintain current versions for MX Linux, and also Debian in this OBS repo: https://build.opensuse.org/package/show ... /keepassxc
MX Linux packager and developer

Dai_trying
Posts: 960
Joined: 2016-01-07 12:25

Re: Keepassxc re-installation gives errors

#7 Post by Dai_trying »

Budgie wrote:Looks like I have some housekeeping to do. Any suggestions?
I would first try apt autoremove to see if any kernels can be easily removed, I believe it leaves at least the current and 1st previous ones intact and so should be safe to use, just check what is to be removed first in case anything else will disappear.

Budgie
Posts: 31
Joined: 2007-06-17 14:50

Re: Keepassxc re-installation gives errors

#8 Post by Budgie »

Head_on_a_Stick wrote:Either move /boot to the root partition or remove some old kernels. Is your root partition encrypted? If so then I think you'll have to reconfigure GRUB to get it working with an encrypted /boot partition. Ask the interweb about that because I have no idea.

Use this to check which kernel ABI versions are installed:

Code: Select all

aptitude search '?narrow(?installed, linux-image)'
If v4.19.0-14 works then you can remove any older version but be sure to keep the linux-image-amd64 metapackage.
Hi, here is what I have:-

Code: Select all

alastair@x3400debian:~$ sudo aptitude search '?narrow(?installed, linux-image)'
i A linux-image-4.19.0-13-amd64                     - Linux 4.19 for 64-bit PCs (signed)                       
i A linux-image-4.19.0-14-amd64                     - Linux 4.19 for 64-bit PCs (signed)                       
i A linux-image-4.19.0-9-amd64                      - Linux 4.19 for 64-bit PCs (signed)                       
i   linux-image-amd64                               - Linux for 64-bit PCs (meta-package)                      
alastair@x3400debian:~$ 
I suppose I could remove linux-image-4.19.0-9-amd64 for starters. I checked in grub.cfg and all three are showing so presumable they would presently show as recovery options. Being nervous will try this first and see if a reboot will get system back to enable me to auto remove.

I tried to run apt autoremove but because the system has not completed earlier work it won't find and remove anything.

I like the idea of enlarging the partition. My thinking was to shrink my /home partition, move to create space next to / partition and then expand it.
I have done this a few times but not on Debian or this device. I was trying to use gparted, which is installed, but for some reason it won't allow me to change anything.
Have I missed something please?

Budgie
Posts: 31
Joined: 2007-06-17 14:50

Re: Keepassxc re-installation gives errors

#9 Post by Budgie »

The errors I reported earlier are not actually due to keepassxc installation but an underlying problem in my initial setup for this machine,
Much has been lost in the cloud of my memory but when I set up Debian I used a wizard and it appears the configuration was not what I usually employ of 40GB for / 2GB for swap and the rest (usually) for /home.
The machine has four drives set up as a RAID 5 array and the partition lineup is as follows:-

Code: Select all

alastair@x3400debian:~$ sudo fdisk -l
[sudo] password for alastair: 
Disk /dev/sda: 2.7 TiB, 2996997980160 bytes, 5853511680 sectors
Disk model: ServeRAID M5014 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 30CDCA3E-F4CD-4A5D-90C4-1120ABF2E3F8

Device       Start        End    Sectors  Size Type
/dev/sda1     2048    1050623    1048576  512M EFI System
/dev/sda2  1050624    1550335     499712  244M Linux filesystem
/dev/sda3  1550336 5853509631 5851959296  2.7T Linux LVM


Disk /dev/mapper/x3400debian--vg-root: 23.3 GiB, 24998051840 bytes, 48824320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-swap_1: 16 GiB, 17163091968 bytes, 33521664 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-var: 9.3 GiB, 9999220736 bytes, 19529728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-tmp: 1.9 GiB, 1996488704 bytes, 3899392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/mapper/x3400debian--vg-home: 2.7 TiB, 2942044209152 bytes, 5746180096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
alastair@x3400debian:~$ 
The usage of the disks is as follows:-

Code: Select all

alastair@x3400debian:~$ df -hT
Filesystem                       Type      Size  Used Avail Use% Mounted on
udev                             devtmpfs  7.8G     0  7.8G   0% /dev
tmpfs                            tmpfs     1.6G  9.5M  1.6G   1% /run
/dev/mapper/x3400debian--vg-root ext4       23G  7.0G   15G  32% /
tmpfs                            tmpfs     7.9G  101M  7.8G   2% /dev/shm
tmpfs                            tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs                            tmpfs     7.9G     0  7.9G   0% /sys/fs/cgroup
/dev/sda2                        ext2      237M  139M   86M  62% /boot
/dev/mapper/x3400debian--vg-var  ext4      9.2G  2.9G  5.9G  33% /var
/dev/mapper/x3400debian--vg-tmp  ext4      1.8G  5.8M  1.7G   1% /tmp
/dev/sda1                        vfat      511M  5.2M  506M   1% /boot/efi
/dev/mapper/x3400debian--vg-home ext4      2.7T   32G  2.5T   2% /home
tmpfs                            tmpfs     1.6G   48K  1.6G   1% /run/user/1000
pCloud.fs                        fuse      2.0T  399G  1.7T  20% /home/alastair/pCloudDrive
alastair@x3400debian:~$ 
None of the partitions appears to be too full but the wizard's choice of partition size for root is less than I use normally.

I just do not understand why I received the errors I did which provoked my OP and why there is not sufficient elasticity in the system with the space available.
Others have suggested workarounds to create more space but it appears none is required.
Grateful for further elucidation by those more knowledgeable.

User avatar
stevepusser
Posts: 12408
Joined: 2009-10-06 05:53
Has thanked: 7 times
Been thanked: 5 times

Re: Keepassxc re-installation gives errors

#10 Post by stevepusser »

Did you ever manage to upgrade keepassxc to the current 2.6.4 release?
MX Linux packager and developer

Budgie
Posts: 31
Joined: 2007-06-17 14:50

Re: Keepassxc re-installation gives errors

#11 Post by Budgie »

Hi Steve,
Not had chance as I was also wrestling with a failing drive on another machine. Will look at KeepassXC tomorrow.
Thanks for the heads up.

User avatar
stevepusser
Posts: 12408
Joined: 2009-10-06 05:53
Has thanked: 7 times
Been thanked: 5 times

Re: Keepassxc re-installation gives errors

#12 Post by stevepusser »

I've just updated keepassXC to 2.6.5 in my OBS repo for Buster, Bullseye, and Sid. Armhf architecture builds are still waiting for machines to build upon: https://build.opensuse.org/package/show ... /keepassxc
MX Linux packager and developer

Post Reply