Linux Mint 21.1 “Vera” Xfce apt corrupt after fresh install

Questions about virtualization software
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Locked
joergent
Level 1
Level 1
Posts: 2
Joined: Mon Mar 27, 2023 5:33 pm

Linux Mint 21.1 “Vera” Xfce apt corrupt after fresh install

Post by joergent »

linuxmint-21.1-xfce-64bit.iso, Windows 11, VMware Workstation 16 Player 16.2.5 build-20904516

Now twice after a fresh install (encrypted ZFS) in a VMware 16 virtual box I get the message in update manager after it has been updated before any other user actions:
Please switch to another Linux Mint error. Your APT configuration is corrupt
Could not refresh the list of updates.
APT error:
E:flAbsPath on /var/lib/dpkg/status failed - realpath(2: No such file or directory)
E:could not open file open (2: No such file or directory)
E: Problem opening
E: The package lists or status file could not be parsed or opened

Could not refresh the list of updates
apt.jpg
After clicking OK and selecting local repositories I just ended up in this without any end.
apt1.jpg
After cancelling and a click on the Refresh button in update manager it produced
E: Could not open file - open (2: No such file or directory)
E: Problem opening
E: The package lists or status file could not be parsed or opened.
E: _cache->open() failed, please report.
and went back to "Please switch to another Linux Mint ..."

After a restart I got this error message in Update Manager
: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
E: _cache->open() failed, please report.
The dpkg command produced
Setting up mintupdate (5.9.7) ...
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.

Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26+mint2+vera) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for libglib2.0-0:amd64 (2.72.1-1) ...
Processing triggers for man-db (2.10.2-1) ...
After this the Update Manager seemed to be working.

This bug must be fixed.
Last edited by LockBot on Thu Sep 28, 2023 10:00 pm, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Locked

Return to “Virtual Machines”