Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E: Sub-process /usr/bin/dpkg exited unexpectedly #3

Open
finlandhl opened this issue Feb 15, 2024 · 9 comments
Open

E: Sub-process /usr/bin/dpkg exited unexpectedly #3

finlandhl opened this issue Feb 15, 2024 · 9 comments

Comments

@finlandhl
Copy link
Owner

Installation and removal of packages and dependencies with apt (apt-get) fails.

Error message:

E: Sub-process /usr/bin/dpkg exited unexpectedly

Anyone who knows how to fix this is invited to share here please
IMG_4187

@lonelypositron
Copy link

same problem as you but when upgrading the full installation and so when installing the base files package from 2024 since the one available from the google drive is from 2019....

there is also an error but maybe it is just secondary
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or directory)

@lonelypositron
Copy link

lonelypositron commented Mar 6, 2024

the official minirootfs from kali itself does not work (after xz decompress and rezip with gzip of course) does not work. error /2
It would have been simpler @finlandhl if you would have publish the patchs you would have applied to the original rootfs since you are calling it custom??? So where did you find it?
in dpkg.log it is status half-installed base-files:i386

@ShadowFlareon
Copy link

Didn't you create this? So why are you asking us when you know more about this than we do

@finlandhl
Copy link
Owner Author

It's an open source project and everyone who can bring his background to help make kali-ios bug free is welcome. I don't know all about linux

@K3kl10
Copy link

K3kl10 commented Mar 16, 2024

Hello. I have same error when I try upgrade kali Linux. The error is:
E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or directory)

but the directory exist with rights root.
ev/pts# cd
root@localhost:# ls -lisa /dev/pts
total 0
1798903 0 drwxr-xr-x 2 root root 64 Feb 28 2019 .
1798900 0 drwxr-xr-x 4 root root 512 Mar 16 19:20 ..
root@localhost:
# ls -lisa /dev
total 16
1798900 0 drwxr-xr-x 4 root root 512 Mar 16 19:20 .
1606944 0 drwxrwxrwx 21 root root 832 Mar 16 19:20 ..
1798901 0 crw-rw-rw- 1 root root 5, 1 Feb 28 2019 console
1798911 4 lrwxrwxrwx 1 root root 13 Feb 28 2019 fd -> /proc/self/fd
1798902 0 crw-rw-rw- 1 root root 1, 7 Feb 28 2019 full
1798909 0 crw-rw-rw- 1 root root 1, 3 Mar 16 20:16 null
1798908 0 crw-rw-rw- 1 root root 5, 2 Feb 28 2019 ptmx
1798903 0 drwxr-xr-x 2 root root 64 Feb 28 2019 pts
1798905 0 crw-rw-rw- 1 root root 1, 8 Feb 28 2019 random
1798910 0 drwxr-xr-x 2 root root 64 Feb 28 2019 shm
1798912 4 lrwxrwxrwx 1 root root 15 Feb 28 2019 stderr -> /proc/self/fd/2
1798913 4 lrwxrwxrwx 1 root root 15 Feb 28 2019 stdin -> /proc/self/fd/0
1798914 4 lrwxrwxrwx 1 root root 15 Feb 28 2019 stdout -> /pro

@finlandhl
Copy link
Owner Author

finlandhl commented Mar 16, 2024

Do NOT upgrade as it will break the whole system. Instead, install your packages manually using the scripts I have provided at /home/tools You can simply download any i386 .deb packages that you want to use alongside its respective dependencies from 2018-2019 releases at Debian Package or Snapshot Debian, extract and copy to the system using the script debinst You can also download and compile source files from the above websites, and install.

These methods are a workaround before I figure out how to make apt-get and/or aptitude to work as expected.

As to fix the

E: Can not write log (Is /dev/pts mounted?) - posix_openpt (2: No such file or directory) run the script bugfix located at /home/tools or find its location with this:

find / -name bugfix

This kali is from 2019. So you must actually run package versions around that year. If you want to run a newer version, the good thing to do is to compile and install.

NEVER OVERWRITE FILES RELATED TO LIBC6 UNLESS YOU KNOW WHAT YOU'RE DOING

New releases coming soon with python3 and pip3 fully working + Links browser ...

I’m also working on the latest kalifs release to make it work in our environment. Still fails to chroot because of compatibility issues with the different shell programs I tried even the latest ones (bash, zsh, dash, etc). I will upload it as sun as it can run successfully

thanks

@K3kl10
Copy link

K3kl10 commented Mar 17, 2024

Thank you for your respond. I never don't upgrade now.

Good job I love it.

@lonelypositron
Copy link

@finlandhl okey good copy on all that but that does not answer my primary question which is, in the end, the root of all the problems… where did you find the custom version of the rootfs version of kali?
Did you compile it yourself ? With what as base material ? And why specifically 2019 ? It’s not like you’ve opened your repo 5 years ago but only a few weeks ago.
i can’t help on the patches if I don’t know where I coming from… do you understand what I mean?

@finlandhl
Copy link
Owner Author

finlandhl commented Apr 5, 2024

Got it from official kali's nethunter rootfs archive:

https://build.nethunter.com/kalifs/kalifs-20190228/kalifs-i386-full.tar.xz

Tried most recent ones but all showing libtinfo6 and libc6 issues. If anyone can manage to get recent rootfs to work, would be great to share with the community

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants