[SOLVED] Utilities install FAIL / dependency problems prevent configuration

SYSTEM: Linux Mint20 Cinnamon, version 4.6.7., intel processor, 15GB Ram, 1 TB hard drive
I can not get epson utilities ( epson-printer-utility_1.1.1-1lsb3.2_i386.deb) to install, though Epson said my XP-7100 printer is on the list of acceptable printers; that’s
why I got the printer I did.

TERMINAL READ-OUT:
Selecting previously unselected package epson-printer-utility:i386.
(Reading database …
(Reading database … 5%%
(Reading database … 100%%
(Reading database … 352460 files and directories currently installed.)
Preparing to unpack …/epson-printer-utility_1.1.1-1lsb3.2_i386.deb …
Unpacking epson-printer-utility:i386 (1.1.1-1lsb3.2) …
dpkg: dependency problems prevent configuration of epson-printer-utility:i386:
epson-printer-utility:i386 depends on lsb (>= 3.2).

CLEARLY NOT MAKING ANY PROGRESS

jennifer@jennifer-ThinkCentre-M91p:~$ sudo dpkg --configure -a
[sudo] password for jennifer:
dpkg: dependency problems prevent configuration of epson-printer-utility:i386:
epson-printer-utility:i386 depends on lsb (>= 3.2).

dpkg: error processing package epson-printer-utility:i386 (–configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
epson-printer-utility:i386
jennifer@jennifer-ThinkCentre-M91p:~$ sudo apt-get install -f
Reading package lists… Done
Building dependency tree
Reading state information… Done
Correcting dependencies… Done
The following packages will be REMOVED:
epson-printer-utility:i386
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 3,142 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database … 352523 files and directories currently installed.)
Removing epson-printer-utility:i386 (1.1.1-1lsb3.2) …
Processing triggers for libc-bin (2.31-0ubuntu9) …
jennifer@jennifer-ThinkCentre-M91p:~$

dpkg: error processing package epson-printer-utility:i386 (–install):
dependency problems - leaving unconfigured
Errors were encountered while processing:
epson-printer-utility:i386

WHAT CAN I DO?

can you post the output of inxi -Fxz so we can get a little more info about your system?

jennifer@jennifer-ThinkCentre-M91p:~$ inxi
CPU: Quad Core Intel Core i5-2400 (-MCP-) speed/min/max: 1777/1600/3400 MHz
Kernel: 5.4.0-42-generic x86_64 Up: 6h 23m Mem: 1827.7/15840.0 MiB (11.5%)
Storage: 931.51 GiB (3.9% used) Procs: 209 Shell: bash 5.0.17 inxi: 3.0.38

it looks like your system is 64-bit:

and you are trying to install the 32-bit printer utility:

can you try installing the 64-bit utility (labeled epson-printer-utility_1.1.1-1lsb3.2_amd64.deb) instead?

https://download.ebz.epson.net/dsc/du/02/DriverDownloadInfo.do?LG2=EN&CN2=&DSCMI=115645&DSCCHK=ace531dfa297077266b666555c3be05ccfb91808

1 Like

i just saw this info below the downloads on the page linked above:

[Notice]
In order to install these drivers, you need to install LSB package (version 3.2 or later) beforehand.

Ubuntu:
sudo apt-get install lsb

1 Like

BUT synaptic package manager said lsb is already installed, though this will be the 3rd package I have tried and always the same result. I just tried the " epson-printer-utility_1.1.1-1lsb3.2_ amd64 .deb " again and the result is the same.

jennifer@jennifer-ThinkCentre-M91p:~$ sudo apt-get -f install lsb
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)
N: Be aware that removing the lock file is not a solution and may break your system.
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

jennifer@jennifer-ThinkCentre-M91p:~$ sudo apt-get install epson-printer-utility
[sudo] password for jennifer:
Sorry, try again.
[sudo] password for jennifer:
Reading package lists… Done
Building dependency tree
Reading state information… Done
epson-printer-utility:i386 is already the newest version (1.1.1-1lsb3.2).
You might want to run ‘apt --fix-broken install’ to correct these.
The following packages have unmet dependencies:
epson-printer-utility:i386 : Depends: lsb:i386 (>= 3.2) but it is not installable
E: Unmet dependencies. Try ‘apt --fix-broken install’ with no packages (or specify a solution).

which version of lsb?

it may help to remove the i386 version completely with synaptic package manager, before trying to install the amd64 version.

I did not know how to see see it directly in Synaptic but I assume it is the lsb shown in the properties box.

are you referring to the text that reads

Installed Version
Version: 1.1.1-1lsb3.2

?

Yes, version 1.1.1-lsb3.2
How do I use synaptic package manager to remove all the previous attempts etc.

in synaptic package manager you would right-click on the name of the epson printer utility package like you did to get the properties info above. to remove it, you would choose “remove completely” (or something similar) from the right-click context menu.

when attempting to install the amd64 package, it might be helpful to let gdebi do so to try and take care of any dependency issues that arise.

Is that the auto package installer? If so, I always try that first.

i believe that is it.

Tried to remove:
jennifer@jennifer-ThinkCentre-M91p:~$ sudo apt autoremove --purge epson=printer-utility
[sudo] password for jennifer:
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is heWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontendWaiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 2Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 2Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 2Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 3Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 3Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 3Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 3Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 3Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 3Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic)… 3Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 12437 (synaptic).

if you are going to attempt to purge the package from a terminal (i would suggest using synaptic instead), you have to close synaptic package manager to remove that dpkg lock.

The result when I tried to use Synaptic PM:

Can't Remove

regarding “unable to lock the download directory”, do you still have the terminal open that you tried to use to purge the utility package? either way, can you close both synaptic package manager and all terminals then reopen synaptic and try again?

1 Like

I did it! It was removed by FIX Broken…
Nothing happened when I applied “marked changes”.

Here is What is shown now, no more “Broken Package”:


also removed image scan. I installed the image scan bundle but after install it failed to work.