(Solved) usrmerge converson

[SMG]

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.

You selected to ignore the message you were getting. Ignoring the message does not mean the problem was fixed. It just means the message will no longer show.

[nonno13]

So was it solved or ignored?

[SMG]

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) ...

was there anything else after this before the command prompt was returned?

[nonno13]

No, I do not think so. I will run it again and let you know

[nonno13]

As I thought, there was nothing after the "Setting up usrmerge (23) ..." line.
----------------------------------------------------------------------------------------------------
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) ...
robert@robert-400-434:~$

[Jo-con-Ël]

Also check if something has change on directory structure .i.e. running ls -ld /{,usr/}{bin,sbin,lib,libx32,lib64,lib32} again.

As per previous result usrmerge was not complete .:

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

Maybe /usr/libx32 and /usr/lib32 are not created as there is nothing to link (there is no /lib32 and libx32 directories) but I wonder what´s the problem why /bin,/lib,...,were not merged. It looks like even didn't try it.

If nothing has change, run sudo dpkg-reconfigure usrmerge and see result.

[nonno13]

┌──────────────────┤ Automatic conversion to merged /usr ├──────────────────┐
│ When running the command "sudo dpkg-reconfigure usrmerge" I received the following message. Is it safe to proceed?
---------------------------------------------------------------------------------------------------------------------------------------------------------------------- Package configuration


│
│ The usrmerge package will automatically convert the system to the merged │
│ /usr directory scheme, in which the /{bin,sbin,lib}/ directories are │
│ symlinked to their counterparts in /usr/. │
│ │
│ There is no automatic method to restore the precedent configuration, so │
│ there is no going back once the conversion has been started. │
│ │
│ Do you want to convert this system to the merged /usr directories │
│ scheme? │
│ │
│ <Yes> <No> │
│ │
└───────────────────────────────────────────────────────────────────────────┘

[rene]

It's safe to go ahead -- although it seems the suggested reinstall of usrmerge should've also already done this; it's the very reason said reinstall was suggested even.

If it gives any error messages when running and if after mintreport still reports the issue please show us those error messages -- but I'll readily admit that I'm then running out of ideas. Did notice a disk-space check in the postinst script; could you if it still didn't do anything after you went ahead report the above ls -ld /{,usr/}{bin,sbin,lib,libx32,lib64,lib32} output again and also the output of df?

[nonno13]

Below are the results of running the commands suggest by Rene.


robert@robert-400-434:~$ sudo dpkg-reconfigure usrmerge
[sudo] password for robert:
The system has been successfully converted.
robert@robert-400-434:~$ ls -ld /{,usr/}{bin,sbin,lib,libx32,lib64,lib32}
lrwxrwxrwx 1 root root 7 May 21 09:17 /bin -> usr/bin
lrwxrwxrwx 1 root root 7 May 21 09:17 /lib -> usr/lib
lrwxrwxrwx 1 root root 9 May 21 09:17 /lib32 -> usr/lib32
lrwxrwxrwx 1 root root 9 May 21 09:17 /lib64 -> usr/lib64
lrwxrwxrwx 1 root root 10 May 21 09:17 /libx32 -> usr/libx32
lrwxrwxrwx 1 root root 8 May 21 09:17 /sbin -> usr/sbin
drwxr-xr-x 2 root root 69632 May 21 09:17 /usr/bin
drwxr-xr-x 144 root root 12288 May 21 09:17 /usr/lib
drwxr-xr-x 2 root root 4096 May 21 09:17 /usr/lib32
drwxr-xr-x 2 root root 4096 May 21 09:17 /usr/lib64
drwxr-xr-x 2 root root 4096 May 21 09:17 /usr/libx32
drwxr-xr-x 2 root root 20480 May 21 09:17 /usr/sbin
robert@robert-400-434:~$ df
df: /run/user/1000/doc: Operation not permitted
Filesystem 1K-blocks Used Available Use% Mounted on
udev 3966420 0 3966420 0% /dev
tmpfs 802636 1548 801088 1% /run
/dev/sda7 233938952 29529400 192456400 14% /
tmpfs 4013176 628 4012548 1% /dev/shm
tmpfs 5120 4 5116 1% /run/lock
tmpfs 4013176 0 4013176 0% /sys/fs/cgroup
/dev/sda2 364544 82284 282260 23% /boot/efi
tmpfs 802632 108 802524 1% /run/user/1000
/dev/sdb2 957435524 401159236 507618268 45% /run/timeshift/backup
/dev/sdb1 980646908 292138844 688508064 30% /media/robert/WD-1TB
pCloud.fs 6291456 780476 5510980 13% /home/robert/pCloudDrive
/dev/sda10 487052608 303053204 159235456 66% /media/robert/Jersey
tmpfs 802632 12 802620 1% /run/user/1001
robert@robert-400-434:~$

[rene]

That's to say then that everything is now definitively fine thanks to Jo-Con-Ël thinking of the explicit dpkg-reconfigure -- although I'm still unsure why the reinstall didn't do that automatically as well.

In the mintreport thingy you can from the "File" menu "Restore ignored reports" and it should/will no longer complain.

[nonno13]

Problem solved. Although I have no idea how. Thank you everyone.