(Solved) usrmerge converson

[nonno13]

Just updated from Linux mint 20.2 to 20.3 within system reports. After the update I get the message in system reports to run usrmerge conversion using the command "apt install usrmerge". I then get the message usrmerge is already the newest version. Finally, after reboot I receive the same notification is system reports. How do I fix this?

[SMG]

How do I fix this?

Check to see if something in this topic Usrmerge - reporter says needed, already done? helps you.

[nonno13]

I am an amateur linux mint user and I really do not understand what they did in the link you provided.

[Termy]

If it's already installed, then it's probably benign. The reporting tool likely has a bug. Unless you find out otherwise, or something more pressing is broken, I'd ignore it for now; it might soon get a fix in an update.

[SMG]

I am an amateur linux mint user and I really do not understand what they did in the link you provided.

You could see if just reinstalling it clears the messages. Open a terminal window and run the following:

Code: Select all

sudo apt-get install --reinstall usrmerge

To prevent typing mistakes:

• You can click "SELECT ALL" to the right of CODE: in order to select everything.
• Then do Control-C (hold the Control key and, while holding it, press the C key) to copy what you selected.
• Then in the terminal window select Edit > Paste.
• Press the Enter key to run the command.

[nonno13]

SMG,

It was worth a try. However, the reinstall did not solve the problem. I still get the notice in System Reports for usrmerge conversion (see Attachement)

[SMG]

SMG,

It was worth a try. However, the reinstall did not solve the problem.

If there were no error messages when you re-installed and it appears it did complete, then I would suggest clicking one of the two buttons in the image you posted.

If clicking "More Information" does not provide useful information, then click the "Ignore this report" button. That would fit with the advice Termy already provided.

[AndyMH]

Personally, I would just ignore it. All usrmerge does is move the contents of /bin to /usr/bin and recreate /bin as a symlink to /usr/bin (and the same for /sbin). Why?
https://www.freedesktop.org/wiki/Softwa ... eUsrMerge/

[nonno13]

I have chosen to ignore it. I don't know if this would be considered as a problem solved so I have not labeled it as solved.

[Termy]

To reiterate: I wouldn't worry about it. It's likely a bug in the reporting tool. It'll probably (hopefully) get fixed in a future version. You may wish to report it on GitHub or something.

[rene]

In the by SMG linked thread the issue was an empty (but still existing) /usr/lib32. Try just

Code: Select all

sudo rmdir /usr/lib32 && sudo rm /lib32

and

Code: Select all

sudo rmdir /usr/libx32 && sudo rm /libx32

Don't worry; the rmdirs will just fail if the directories do not exist or are not empty. You will need to restart the mintreport thingy to check if it helped.

[nonno13]

I looked in my "File System" folder and there is no /lib32, /usr/lib32, /libx32 or /usr/libx32 folders.

[rene]

Odd. It is indeed the case that you can simply ignore it, but if you want to get to the bottom...

If you can read Python, the source of this mintreport module is /usr/share/linuxmint/mintreport/reports/100_usrmerge-not-done/MintReportInfo.py. It's a trivial script and other than for my above suggestion no issue would be expected. You can run and/or share output of lsb_release -a and

Code: Select all

ls -ld /{,usr/}{bin,sbin,lib,libx32,lib64,lib32}

to have us see what's going on. Results for me:

Code: Select all

rene@hp8k:~$ LC_ALL=C lsb_release -a
No LSB modules are available.
Distributor ID:	Linuxmint
Description:	Linux Mint 20.3
Release:	20.3
Codename:	una
rene@hp8k:~$ LC_ALL=C ls -ld /{,usr/}{bin,sbin,lib,libx32,lib64,lib32}
ls: cannot access '/libx32': No such file or directory
ls: cannot access '/lib32': No such file or directory
ls: cannot access '/usr/libx32': No such file or directory
ls: cannot access '/usr/lib32': No such file or directory
drwxr-xr-x   2 root root 69632 May 14 16:41 /usr/bin
drwxr-xr-x 147 root root 12288 May 14 16:41 /usr/lib
drwxr-xr-x   2 root root  4096 May 14 16:40 /usr/lib64
drwxr-xr-x   2 root root 20480 May 14 16:41 /usr/sbin
lrwxrwxrwx   1 root root     7 May 15  2021 /bin -> usr/bin
lrwxrwxrwx   1 root root     7 May 15  2021 /lib -> usr/lib
lrwxrwxrwx   1 root root     9 May 15  2021 /lib64 -> usr/lib64
lrwxrwxrwx   1 root root     8 May 15  2021 /sbin -> usr/sbin

[rickNS]

I quite dislike that mintreport tool, and disabled it in startup applications.
For one, I don't need to see the same useless message every boot, and two, I don't want to see it's icon on my panel either.

[rene]

When running Linux Mint over a more minimalist system in the first place the definition of "useless" becomes I'd say a bit fluid anyway; to seemingly largely coincide with "things introduced after I first found Mint". For me that first-use version was already loaded with useless crap -- and I'm even after 5+ years now still not ready to again give a hoot...

[rickNS]

seemingly largely coincide with "things introduced after I first found Mint". For me that first-use version was already loaded with useless crap -- and I'm even after 5+ years now still not ready to again give a hoot...

WOW, lot of truth in that statement.

[nonno13]

Below is the result of running the commands suggested by rene.

robert@robert-400-434:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Linuxmint
Description: Linux Mint 20.3
Release: 20.3
Codename: una
robert@robert-400-434:~$ ls -ld /{,usr/}{bin,sbin,lib,libx32,lib64,lib32}
ls: cannot access '/libx32': No such file or directory
ls: cannot access '/lib32': No such file or directory
ls: cannot access '/usr/libx32': No such file or directory
ls: cannot access '/usr/lib64': No such file or directory
ls: cannot access '/usr/lib32': No such file or directory
drwxr-xr-x 2 root root 4096 May 18 11:41 /bin
drwxr-xr-x 23 root root 4096 May 7 19:11 /lib
drwxr-xr-x 2 root root 4096 May 11 08:29 /lib64
drwxr-xr-x 2 root root 12288 May 18 11:41 /sbin
drwxr-xr-x 2 root root 69632 May 18 11:41 /usr/bin
drwxr-xr-x 125 root root 12288 May 18 11:38 /usr/lib
drwxr-xr-x 2 root root 12288 May 18 11:41 /usr/sbin

[rene]

Your system has indeed and in fact not been converted. Did the reinstall of usrmerge show an error? I.e., what does

Code: Select all

sudo apt-get install --reinstall usrmerge

say?

[nonno13]

This is the result after reinstalling usrmerge. However, after the reinstall I just ran as shown below I reran system reports and now it indicates that "no problems were detected". It seems to have been taken care of a few days ago when I chose to "ignore this report." So it now appears that the problem is fixed and I have no idea how it was solved.

robert@robert-400-434:~$ sudo apt-get install --reinstall usrmerge
[sudo] password for robert:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/11.8 kB of archives.
After this operation, 0 B of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 399782 files and directories currently installed.)
Preparing to unpack .../archives/usrmerge_23_all.deb ...
Unpacking usrmerge (23) over (23) ...
Setting up usrmerge (23) ...

[rene]

Well, if you chose to "ignore the report" the fact that's it's not reported on anymore wouldn't necessarily be to say that anything was taken care of; it's after all in any case ignored...

But okay; am not here at the moment...