not sure if that’s an issue of the Sway edition… just checked my local installation and those permissions and user/group relations are looking good for everything within the /usr folder… might be caused by some software that you have installed later on eventually…
Nope, no issue here… might be related to other parts of your system…
Well if this is the case then I would agree with @0n0w1c and recursively change the owner of the system directories/files back to root where they belong before future installs might snowball on him. You agree @appelgriebsch?
sudo chown -R root:root /usr
Japp… sounds like a good strategy.
Btw: also checked the latest image of Sway placed onto microSD card two days ago… (basically a fresh install), also not an issue there. So we should be safe (by default).
The issue that ufw gives the warning? Yes, I have experienced that in other Manjaro Editions too, xfce and kde ones.
It is interesting you have the file permissions set up to root; which brings up the question on what makes the permissions on my pbp sway to change…
For the records, I mainly use official repositories. Only software that I use outside of the official are a few from aur and obviously the chromium widevine installer script, which I issued from the comman line (wofi shortcut is directing me to commandline).
should I issue the command to take back the ownership of the /usr?
I was thinking about making it to / systemwide followed by my own user recursively. I was not sure if it would break anything so I decided not to…
Something changed /usr/local/bin /usr/local/share ownership recursively from root to uid 1001. It does not appear to change anything else under /. So just do /usr and if something else pops up later on then deal with it.
Ok, I set the ownership of /usr director to root. All directories seem to be owned by the root.
However, I am having another issue now. When I try:
sudo ufw status verbose
I have the message below:
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
I do not understand how come @appelgriebsch or you do not have these issues, maybe you don’t have the firewall or maybe you have customized the install.
What to do with sudo now? It seems to be broken…
Nope, sudo is broken.
I am on Manjaro Sway testing that I installed just three weeks ago. It is good to know that this issue is fixed within three weeks time. I am impressed…
Try uninstalling and installing sudo as root.
Interesting.
I try removing sudo via pamac; which is freezing as of now.
I try opening a bash shell and trying to login as root via
su -
I receive the error below:
su: Authentication service cannot retrieve authentication info
Not being able to login as root seems to be a show stopper. Hope I am wrong.
Any ideas?
Try exiting out of the DE and log back in as root.
Yes, I rebooted. Tried login as “root” in the greeterd. It is giving error. I believe root account is disabled in favor of sudo; I am unsure though.
When I open a shell and su again I receive the same error.
I believe something you installed has messed things up but I guess it could have been something amiss with the image you installed. Either way something is amiss with the ownership change of system files/directories from root to 1001.
I had a kind of similar issue exacting a tarball that was really meant for a ubuntu/debian os one time and it messed up my file system because of some symbolic links in / arch uses. I messed around with it for days to get it back what it was supposed to be but things was not completely right so I did a complete reinstall on my desktop.
Ok, I assume this is a screw up. I guess useless to think about what I did at this stage.
I have a backup armbian system based on Ubuntu/Debian. I will be using it for a while.
I have ufw there already installed too so I will check it up to see anything wrong there. If anything is wrong, I will post it here.
I prefer to wait for the Manjaro stable release (either June or September) to make sure this issue is fixed. I guess when I come back hopefully in late June, I will be keeping an eye on the issue.
I am just updating everyone with my firewall adventure.
I got a bit curious and I decided to make a fresh manjaro install. I have two tries:
Manjaro Mate Edition from Manjaro - Downloads - This, I tried as a first experiment. After updatess and such I installed ufw. Checked out the status with ufw status verbose. All fine, so mate is working normal.
Manjaro XFCE Edition: The reason I try this is because of XFCE is my favorite de. Odd things happened here:
ufw status verbose
I obtain
WARN: uid is 0 but ‘/usr’ is owned by 1001
which brings me to square one. I remember installing the Manjaro Sway Edition from the same posting at Manjaro ARM 21.04 released! so I suspect the images uploaded there are problematic.
Lessons learned:
Please upload the Manjaro XFCE image at the official website and check out the images available at the 21.04 website. They seem to be badly produced or unmaintained.
For those of us who downloaded Manjaro images from the 21.04 posting; please be alert and make sure that your filesystem is setup appropriately.
I was going to abandon Manjaro completely; however, I changed my mind. I will switch to Manjaro Mate Edition. It is not my favorite de and buggy. Nevertheless armbian has its own bugs too.
Wanted to warn people who use Manjaro particularly from the 21.04 forum.
Seems like you have an old cache of that webpage, because it links fine to 21.04 for me.
Those images are official and produced by the Manjaro ARM team. But browser cache can make it seem like it’s out of date sometimes.
There is nothing in the profiles for MATE and XFCE that would make them get different permissions.
Actually. I did find one file with wrong permissions. It’s the manjaro-icon.svg in /usr/share/icons/.
Fixed it here now.
I checked out the links yesterday from the official website of Manjaro at Manjaro - Downloads ; XFCE was at 20.12 whereas Mate was 21.04. To ensure, I cleaned my webbrowser history (everything including cache, offsite data etc.). I have checked right now again; I can confirm the image for XFCE is at 21.04. Yet, I do not want to make another try to see if the file permissions of XFCE image are correct.
No, I didn’t check the Mate image from your announcement post for 21.04. I downloaded it from the official website. Mate has everything normal, firewall is working without any warnings. Yet, it is not my persoanal preference.
The images I tried from your 21.04 post were XFCE (because 21.04 version was not available in the official website) and Sway (it is the development version). Both of them have file permission problems with uid 1001 on /usr directory as already discussed in this thread. In both images, the firewall correctly warned against the situation.
Is there anyway to include MD5 checksums with Manjaro Arm images?
There are sha1 checksums for all image files in the download location: Release Pinebook Pro 21.04 · manjaro-arm/pbpro-images · GitHub
