Kaisen-skeleton error?

Bugs report Tools
1

I am getting the following error during the latest kaisen-update:

fatal: destination path ‘/etc/skel/.oh-my-zsh’ already exists and is not an empty directory.
dpkg: error processing package kaisen-skeleton (–configure):
installed kaisen-skeleton package post-installation script subprocess returned error exit status 128
Errors were encountered while processing:
kaisen-skeleton
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have tried to fix it by deleting the directory mentioned, and by running dpkg as follow (dry-run only to make sure :slight_smile: )

sudo dpkg --remove --force-remove-reinstreq --dry-run kaisen-skeleton
dpkg: dependency problems prevent removal of kaisen-skeleton:
kaisen-interfaces-common depends on kaisen-skeleton.

dpkg: error processing package kaisen-skeleton (–remove):
dependency problems - not removing
Errors were encountered while processing:
kaisen-skeleton

Any clue at what the problem might be and what the effect might be?
It does not seem to create any issues.

2

Hello @MidGe, can you try the following command : sudo apt reinstall kaisen-skeleton ?

3

Here is the result:
❯ sudo apt reinstall kaisen-skeleton
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for kaisen-skeleton:amd64

4

Hello,

This message is not normal and cannot be related to the updates. It may be a system misconfiguration or a handling error.
If you have installed Kaisen with BTRFS, maybe try to restore an APT snapshot. Be careful though, the data saved after this snapshot will be lost.

5

Unfortunately I have the same issue as well Kevin :frowning: @Kaisen
kaisen-skeleton issue will appear after doing kaisen-update

This is my apt source list for , only 2

image
image614×126 18.4 KB

And the error appears after doing sudo kaisen-update

image
image608×186 23.4 KB

My college with kaisen distro has the same kaisen-skeleton issue as well, same steps like mine, any idea on how to fix this ?

6

Hello,

Why did you add the Debian sid repositories?
You might break some of the stuff provided on Kaisen by doing so, or install unwanted versions of tools
Kaisen Linux repositories provide the entire Debian repository in its testing branch, you don’t need to add the official Debian repositories.

Regarding the kaisen-skeleton package, I’ll look at what the problem is.

Thanks for your feedback.

7

If you try the sudo apt reinstall kaisen-skeleton command, what do you get?

8

@MidGe and @catinabox, I pushed a update of the kaisen-skeleton. Your problem is resolved ?
Try updating Kaisen again with the command sudo kaisen-update

9

Hello Kevin,

No, that did not seem to fix the problem for me.

Note, that the issue does not seem to affect the overall system. I have not noticed any other issues with my system and have updated once a day, seemingly successfully.

Thanks for your attention to this, but I hope it does not take precedence over your exams. :slight_smile:

Here is the output:
❯ sudo kaisen-update
[sudo] password for michel:
Hit:1 https://brave-browser-apt-release.s3.brave.com stable InRelease
Ign:2 Index of /stable/deb/ stable InRelease
Hit:3 Index of /stable/deb/ stable Release
Get:5 https://deb.kaisenlinux.org kaisen-rolling InRelease [19.7 kB]
Fetched 19.7 kB in 2s (10.2 kB/s)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
All packages are up to date.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
The following packages were automatically installed and are no longer required:
libgovirt-common libgovirt2 libphodav-2.0-0 libphodav-2.0-common librest-0.7-0 libsoup-gnome2.4-1
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Supported
Create a snapshot of ‘/tmp/apt-btrfs-snapshot-mp-hk146eyf/@’ in ‘/tmp/apt-btrfs-snapshot-mp-hk146eyf/@apt-snapshot-2022-08-09_03:19:46’
Setting up kaisen-skeleton (2.1+kaisen2) …
fatal: destination path ‘/etc/skel/.oh-my-zsh’ already exists and is not an empty directory.
dpkg: error processing package kaisen-skeleton (–configure):
installed kaisen-skeleton package post-installation script subprocess returned error exit status 128
Errors were encountered while processing:
kaisen-skeleton
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages were automatically installed and are no longer required:
libgovirt-common libgovirt2 libphodav-2.0-0 libphodav-2.0-common librest-0.7-0 libsoup-gnome2.4-1
Use ‘sudo apt autoremove’ to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Supported
Create a snapshot of ‘/tmp/apt-btrfs-snapshot-mp-8ewmzvxb/@’ in ‘/tmp/apt-btrfs-snapshot-mp-8ewmzvxb/@apt-snapshot-2022-08-09_03:19:50’
Setting up kaisen-skeleton (2.1+kaisen2) …
fatal: destination path ‘/etc/skel/.oh-my-zsh’ already exists and is not an empty directory.
dpkg: error processing package kaisen-skeleton (–configure):
installed kaisen-skeleton package post-installation script subprocess returned error exit status 128
Errors were encountered while processing:
kaisen-skeleton
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following packages will be REMOVED:
libgovirt-common* libgovirt2* libphodav-2.0-0* libphodav-2.0-common* librest-0.7-0* libsoup-gnome2.4-1*
0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 691 kB disk space will be freed.
Supported
Create a snapshot of ‘/tmp/apt-btrfs-snapshot-mp-ka3ltr5q/@’ in ‘/tmp/apt-btrfs-snapshot-mp-ka3ltr5q/@apt-snapshot-2022-08-09_03:19:56’
(Reading database … 605746 files and directories currently installed.)
Removing libgovirt2:amd64 (0.3.8-1) …
Removing libgovirt-common (0.3.8-1) …
Removing libphodav-2.0-0:amd64 (2.5-1) …
Removing libphodav-2.0-common (2.5-1) …
Removing librest-0.7-0:amd64 (0.8.1-1.1) …
Removing libsoup-gnome2.4-1:amd64 (2.74.2-3) …
Setting up kaisen-skeleton (2.1+kaisen2) …
fatal: destination path ‘/etc/skel/.oh-my-zsh’ already exists and is not an empty directory.
dpkg: error processing package kaisen-skeleton (–configure):
installed kaisen-skeleton package post-installation script subprocess returned error exit status 128
Processing triggers for kaisen-menu (2.1+kaisen6) …
Processing triggers for libc-bin (2.33-8) …
Errors were encountered while processing:
kaisen-skeleton
E: Sub-process /usr/bin/dpkg returned an error code (1)

10

I just did a new install and ran kaisen-update after installation. I’m getting this exact same error. reinstalling kaisen-skeleton reports that it does not exist.

11

Thank you for your replies @MidGe and @rkyrk. I not understand the problem, because the package is developped to delete the ohmyzsh folder when the package is removed or updated before the download of the repository from github.

I will fix this problem, and I will ask you if the problem has been solved for you.

Thank you for your feedback !

1 Like
12

@MidGe, no problem for my exams, they are finished since the last week :wink:

13

As always Kevin, thanks for your help and attention to this. Sometimes things just happen to make your life more fun.

14

@MidGe, @rkyrk and @catinabox can you retry to launch an update of Kaisen ?
The problem with kaisen-skeleton has been resolved normally.

15

It’s a pleasure for me !
Aha, it’s true :wink:
But I not understand the origin of this bug :sweat_smile:
But it happens sometimes…

16

I just did retry but the issue is still there.

I have a suspicion that the issue may be related to either:

  1. a oh-my-zsh plugin
  2. an install of wine

It was the first time I had to install win for years (it has now been deleted from my system, but it did bring in all the extra architecture stuff for 32 bits system.

The plugins installed for oh-my-zsh are: colored-man-pages colorize command-not-found git history-substring-search sudo vagrant z zsh-autosuggestions zsh-syntax-highlighting

Hope this may help.

17

Thank you for your feedback!
What is the output after the launch of the kaisen-update command?
I don’t think it’s from your ZSH plugins or wine if the message is the same as before.

18

To remove the 32-bit archirecture, try run this command: sudo dpkg --remove-architecture i386

19
  1. I re-ran kaisen-update again as I had closed the terminal, with same results:

❯ sudo kaisen-update
[sudo] password for michel:
Hit:1 https://brave-browser-apt-release.s3.brave.com stable InRelease
Ign:2 Index of /stable/deb/ stable InRelease
Hit:3 Index of /stable/deb/ stable Release
Hit:5 https://deb.kaisenlinux.org kaisen-rolling InRelease
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
All packages are up to date.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Supported
Create a snapshot of ‘/tmp/apt-btrfs-snapshot-mp-3h_15inh/@’ in ‘/tmp/apt-btrfs-snapshot-mp-3h_15inh/@apt-snapshot-2022-08-09_05:27:53’
Setting up kaisen-skeleton (2.1+kaisen3) …
/var/lib/dpkg/info/kaisen-skeleton.postinst: line 6: dconf: command not found
dpkg: error processing package kaisen-skeleton (–configure):
installed kaisen-skeleton package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
kaisen-skeleton
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Supported
Create a snapshot of ‘/tmp/apt-btrfs-snapshot-mp-8mr4yhsm/@’ in ‘/tmp/apt-btrfs-snapshot-mp-8mr4yhsm/@apt-snapshot-2022-08-09_05:27:55’
Setting up kaisen-skeleton (2.1+kaisen3) …
/var/lib/dpkg/info/kaisen-skeleton.postinst: line 6: dconf: command not found
dpkg: error processing package kaisen-skeleton (–configure):
installed kaisen-skeleton package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
kaisen-skeleton
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Supported
Create a snapshot of ‘/tmp/apt-btrfs-snapshot-mp-poxu0322/@’ in ‘/tmp/apt-btrfs-snapshot-mp-poxu0322/@apt-snapshot-2022-08-09_05:28:00’
Setting up kaisen-skeleton (2.1+kaisen3) …
/var/lib/dpkg/info/kaisen-skeleton.postinst: line 6: dconf: command not found
dpkg: error processing package kaisen-skeleton (–configure):
installed kaisen-skeleton package post-installation script subprocess returned error exit status 127
Errors were encountered while processing:
kaisen-skeleton
needrestart is being skipped since dpkg has failed

2)❯ sudo dpkg --remove-architecture i386

dpkg: error: cannot remove architecture ‘i386’ currently in use by the database

I am not sure about what might be using i386 stuff now!?

20

Okay, thank you for your feedback!
I will add an if statement for the execution of this command.

For the i386 architecture, it’s because you have still few i386 packages installed on your system.