Cannot access archive linux

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

EmpireProject / Empire Public archive

dpkg: error: cannot access archive ‘libssl1.0.0_1.0.1t-1+deb8u7_amd64.deb’: No such file or directory #1359

dpkg: error: cannot access archive ‘libssl1.0.0_1.0.1t-1+deb8u7_amd64.deb’: No such file or directory #1359

Comments

Empire Version

OS Information (Linux flavor, Python version)

Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.

Expected successful installation. Error: dpkg: error: cannot access archive ‘libssl1.0.0_1.0.1t-1+deb8u7_amd64.deb’: No such file or directory

1. git clone [URL link from main page]
2. Navigated to setup folder, and ./install.sh
3. Received error message: dpkg: error: cannot access archive ‘libssl1.0.0_1.0.1t-1+deb8u7_amd64.deb’: No such file or directory
4. pip install —force-reinstall pip==18.1
5. edited /setup/install.sh. Commented out all lines of pip install —upgrade pip
6. Tried to reinstall with ./install.sh . Same error message
7. sudo rm -rf Empire in opt folder where Empire was installed.
8. Migrated over to dev branch, git clone [URL link from dev branch]
9. Navigated to setup folder, and ./install.sh
10. Received error message again.

So whether I install from the master or dev branches, I get the same error message.

Screenshot of error, embedded text output, or Pastebin link to the error

dpkg: error: cannot access archive ‘libssl1.0.0_1.0.1t-1+deb8u7_amd64.deb’: No such file or directory

Any additional information

I saw another question related to this error here, but was unable to get it resolved using the suggestions there.

Also, this is my very first time on github, so I apologize in advance for misinformation, etc.

The text was updated successfully, but these errors were encountered:

Источник

dpkg: error porccessing archive (—unpack) [closed]

I got this error message when trying to run sudo apt -f install .

dpkg: error proccessing archive /var/cache/apt/archives/kali-themes_2020.3.2_all.deb(--unpack) errors were encountered while proccessing: /var/cache/apt/archives/kali-defaults_2020.3.4_all.deb /var/cache/apt/archives/kali-themes_2020.3.2_all.deb sub-proccess /usr/bin/dpkg returned an error code (1) 

Sounds like a bug in a kali package. What happens if you sudo dpkg -i /var/cache/apt/archives/kali-theme_2020.3.2_all.deb or sudo dpkg -i /var/cache/apt/archives/kali-defaults_2020.3.2_all.deb ? I’m curious which package has the bug.

i wrote this in terminal sudo dpkg -i /var/cache/apt/archives/kali-theme_2020.3.2_all.deb dpkg : error: cannot access archive /var/cache/apt/archives/kali-theme_2020.3.2_all.deb : no such file or directory. I added this photo

Welcome to the site. Please, don’t post screenshots of console output; instead, copy-and-paste it into your question using proper formatting.

1 Answer 1

Run the following commands.

sudo dpkg -i --force-overwrite kali-themes tilix-common libgtkd-3-0 libphobos2-ldc-shared91 libvted-3-0 sudo apt -f install sudo apt install tilix 

Related

Hot Network Questions

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.7.12.43529

Linux is a registered trademark of Linus Torvalds. UNIX is a registered trademark of The Open Group.
This site is not affiliated with Linus Torvalds or The Open Group in any way.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Thread: dpkg: error: cannot access archive

First Cup of Ubuntu

dpkg: error: cannot access archive

I am running Ubuntu 22.04.2 LTS

When I update and upgrade, I get the following error:

dpkg: unrecoverable fatal error, aborting: loading files list file for package 'fonts-tibetan-machine': cannot read /var/lib/dpkg/info/fonts-tibetan-machine.list (Input/output error) E: Sub-process /usr/bin/dpkg returned an error code (2)

eat, ride, sleep, repeat

Join Date Aug 2016 Location Wandering Beans 6,395 —> Beans Hidden! Distro Xubuntu Development Release

Re: dpkg: error: cannot access archive

ls /var/lib/dpkg/info/ | grep fonts

With realization of one’s own potential and self-confidence in one’s ability, one can build a better world.
Dalai Lama>>
Code Tags Arch Linux, openSuse Tumbleweed, Debian Unstable

Ubuntu addict and loving it

Join Date Aug 2011 Location 51.8� N 5.8� E Beans 6,757 —> Beans 6,757 Distro Xubuntu 22.04 Jammy Jellyfish

Re: dpkg: error: cannot access archive

Multiple errors that have nothing directly to do with each other, at least one give an I/O error on file access. That smells like a damaged filesystem, possibly a broken harddrive.

Can you test smart status of your hard drive? BTW, best to monitor that over time.

Modules & Layers

Re: dpkg: error: cannot access archive

[QUOTE=ttgteacher;14139676]I am running Ubuntu 22.04.2 LTS

When I update and upgrade, I get the following error:

. cannot read /var/lib/dpkg/info/fonts-tibetan-machine.list (Input/output error)

When I saw this in the first post, the first thing I thought of was;

Reboot the machine and at the Grub2 menu, use Advance Options > Rescue > fsck. If it is just an EXT filesystem error, it will attempt to repair it. If it is a bad part of the disk, it will attempt to move it to a good part of the disk and mark that sector as bad. The same with ZFS ZPool scrub for filesystems on ZFS.

If it says that it had to repair the filesystem and there is still a problem with reading that file, then reinstall the package via

sudo apt install --reinstall fonts-tibetan-machine

I recognize that as a font package for Tibetan, Dzongkha and Ladakhi.

I may be confused, but. Everyone lately seems to jump directly to smartmontools first for reading errors (which I use), but seem to forget that there are other tools to use first. That, and smartmontools is not a default installed application and so it would need to be installed by a User before using it.

I love smartmontools and it is invaluable for what it does, and what it can report. now, along with nvme-cli for NVMe drives. I use both a lot.

Last edited by MAFoElffen; April 20th, 2023 at 12:01 AM . Reason: Because after I post something, I wonder how I spelled things so badly. Am I becomeing dislexic? LOL

Источник

Thread: dpkg: error: cannot access archive

First Cup of Ubuntu

dpkg: error: cannot access archive

I am running Ubuntu 22.04.2 LTS

When I update and upgrade, I get the following error:

dpkg: unrecoverable fatal error, aborting: loading files list file for package 'fonts-tibetan-machine': cannot read /var/lib/dpkg/info/fonts-tibetan-machine.list (Input/output error) E: Sub-process /usr/bin/dpkg returned an error code (2)

eat, ride, sleep, repeat

Join Date Aug 2016 Location Wandering Beans 6,395 —> Beans Hidden! Distro Xubuntu Development Release

Re: dpkg: error: cannot access archive

ls /var/lib/dpkg/info/ | grep fonts

With realization of one’s own potential and self-confidence in one’s ability, one can build a better world.
Dalai Lama>>
Code Tags Arch Linux, openSuse Tumbleweed, Debian Unstable

Ubuntu addict and loving it

Join Date Aug 2011 Location 51.8� N 5.8� E Beans 6,757 —> Beans 6,757 Distro Xubuntu 22.04 Jammy Jellyfish

Re: dpkg: error: cannot access archive

Multiple errors that have nothing directly to do with each other, at least one give an I/O error on file access. That smells like a damaged filesystem, possibly a broken harddrive.

Can you test smart status of your hard drive? BTW, best to monitor that over time.

Modules & Layers

Re: dpkg: error: cannot access archive

[QUOTE=ttgteacher;14139676]I am running Ubuntu 22.04.2 LTS

When I update and upgrade, I get the following error:

. cannot read /var/lib/dpkg/info/fonts-tibetan-machine.list (Input/output error)

When I saw this in the first post, the first thing I thought of was;

Reboot the machine and at the Grub2 menu, use Advance Options > Rescue > fsck. If it is just an EXT filesystem error, it will attempt to repair it. If it is a bad part of the disk, it will attempt to move it to a good part of the disk and mark that sector as bad. The same with ZFS ZPool scrub for filesystems on ZFS.

If it says that it had to repair the filesystem and there is still a problem with reading that file, then reinstall the package via

sudo apt install --reinstall fonts-tibetan-machine

I recognize that as a font package for Tibetan, Dzongkha and Ladakhi.

I may be confused, but. Everyone lately seems to jump directly to smartmontools first for reading errors (which I use), but seem to forget that there are other tools to use first. That, and smartmontools is not a default installed application and so it would need to be installed by a User before using it.

I love smartmontools and it is invaluable for what it does, and what it can report. now, along with nvme-cli for NVMe drives. I use both a lot.

Last edited by MAFoElffen; April 20th, 2023 at 12:01 AM . Reason: Because after I post something, I wonder how I spelled things so badly. Am I becomeing dislexic? LOL

Источник