package usrmerge 24ubuntu3 failed to install/upgrade: installed usrmerge package post-installation script subprocess returned error exit status 1

[Colin GILLE]

I ran "sudo mv /bin/usb_printerid /tmp" to continue with the install

ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: usrmerge 24ubuntu3
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sat Apr 17 14:32:26 2021
ErrorMessage: installed usrmerge package post-installation script subprocess returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.7.1ubuntu4
 apt 2.2.3
SourcePackage: usrmerge
Title: package usrmerge 24ubuntu3 failed to install/upgrade: installed usrmerge package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to hirsute on 2021-04-17 (0 days ago)

[Carlos A. (cif2cif)]

I have the same problem after updating to 21.04. The error is:

usrmerge (24ubuntu3)...

FATAL ERROR:
Both /bin/ksh and /usr/bin/ksh exist.
Sub-process /usr/bin/dpkg returned an error code (1)

$ sudo /usr/lib/usrmerge/convert-usrmerge

FATAL ERROR:
Both /bin/ksh and /usr/bin/ksh exist.

You can try correcting the errors reported and running again
/usr/lib/usrmerge/convert-usrmerge until it will complete without errors.
Do not install or update other Debian packages until the program
has been run successfully.

[Mathieu Austruy (maustruy)]

I filled another bug that maybe related https://bugs.launchpad.net/ubuntu/+bug/1930573

[Randy Ransier (oliver27b)]

my usrmerge FATAL ERROR is similar

Both /bin/fgrep and /usr/bin/fgrep exist.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[abdullahc (sneetsher)]

@Randy, Those `fgrep` are identical files, so just `sudo rm /bin/fgrep`

@Carlos, Those also identical but symbolic link to alternatives, so just `sudo rm /bin/ksh`

I believe that `usrmerge` should check for identical files and symlinks, and make auto solution by deleting one of conflicting files.

[Marcelo Tenório (marcelllo-martin)]

My usrmerge fatal error after upgrading to 21.04:

FATAL ERROR:
Both /bin/journalctl and /usr/bin/journalctl exist.

[Dimitri John Ledkov (xnox)]

@everyone

Can each one of you please open a new bug reports, using `ubuntu-bug` tool with full apt output logs. Each error that happens may need unique solutions.

Also I really need to know where from you are upgrading, and when/how the system was last installed. As that matters a lot for usrmerge to work correctly.

[Dimitri John Ledkov (xnox)]

`Unpack base-files (11ubuntu18) on (11ubuntu14) ..`

Looks very odd, because it is an upgrade between groovy-release and development version of hirsute, not the one we released.

[Dimitri John Ledkov (xnox)]

Also it is brand new installation of usrmerge package, and yet the system looks like usrmerged already, i think.

[Dimitri John Ledkov (xnox)]

@everyone

Can you please also specify when and how you installed your systems? i.e. attach your /var/log/installer

[Andrew (ajmetz82)]

For me it was:
"Both /sbin/grub-install and /usr/sbin/grub-install exist"

[Andrew (ajmetz82)]

I'm so confused. My 21.04 installation aborted over this, and I was warned my system may be in an unuseable state, except when I login via ssh it says it is 21.04 and apt doesn't seem to detect anything to update...so...how do I know if there is any work unfinished, and how can I check my system has updated properly, or if there are outstanding upgrade tasks to be performed?

I was going to attached my var/log/installer - except I saw every file is empty / zero bytes, so it's pointless!? Am using a CloudVPS via Onapp via Neostrada.

After the errors, I moved sbin/grub-install to opt/mytemp/grub-install and then ran
/usr/lib/usrmerge/convert-usrmerge
which gave the same complaint again this time about update-grub
so I moved sbin/update-grub to opt/mytemp/update-grub and then ran
/usr/lib/usrmerge/convert-usrmerge
again - and this time it gave no further errors.
Instead saying:
The system has been successfully converted
So then I tried:
dpkg --configure -a
which said:
Setting up usrmerge (24ubuntu3) ...
and then went quiet, returning me to the prompt.
I tried it again:
dpkg --configure -a
and got nothing on screen, just a new command prompt line - I assume it ran successfully or something.

So was this just a bumpy upgrade and all is good,
or is something now wrong with my system, and I need to do something to finish the installation process?

[Marcelo Tenório (marcelllo-martin)]

I noticed that, apparently, directory "/bin" ( and maybe /sbin ) are supposed not to have actual binaries, but symlinks to, respectively, binaries in /usr/bin and /usr/sbin.

Having binaries with same name (not necessarily same size) in both directories may be causing this problem?

[Marcelo Tenório (marcelllo-martin)]

@xnox

The new bug report:

https://bugs.launchpad.net/ubuntu/+source/usrmerge/+bug/1942462

[Marcelo Tenório (marcelllo-martin)]

Hi. I was able to fix following this solution: https://askubuntu.com/a/1334400