- This topic has 43 replies, 6 voices, and was last updated May 13-7:05 am by zeh.
-
Posts
-
wildstar84
Did you do “ls -l /usr/bin/sudo”?
Mine shows: “-rwsr-xr-x 1 root root 157192 Jan 12 12:10 /usr/bin/sudo”
Make sure it’s set with that “s” in the root permissins!
Also, could your /etc/sudoers file be corrupted? Might want to grab the one off the original. There are warnings a/b needing to use a special version of vi to edit it (called “visudo”) as one can corrupt it using just “vi” somehow, though I’ve never mucked mine up with vi. It should be “-r–r—– 1 root root…”.Regards,
Jim
zeh
Hi Jim,
Did you do “ls -l /usr/bin/sudo”?
Mine shows: “-rwsr-xr-x 1 root root 157192 Jan 12 12:10 /usr/bin/sudo”Following the previous posts I’ve searched a bit more and I’ve found that one, yes.
“ls -l /usr/bin/sudo” showed the version with incorrect permissions
I then did “chmod u+s /bin/sudo” (as per the instructions)
and “ls -l /usr/bin/sudo” again – it now showed the correct permissions (it looks like yours)After this su is working fine (sudo was corrected before and also works fine) – no more “authentication failure”.
However, I still get a blank sreen at boot.
At the blank screen, Ctrl+Alt-F1 gives me the CLI with the boot info.Visible part of the boot info:
[....] Starting session management daemon: elogind [ 22.991661] cgroup:Cgroup2: unknown option "nsdelegate" [ 23.106731] elogind-daemon [1983]: New seat seat0. . [OK] Starting mouse interface server: gpm. [OK] Starting SMO IRQ Balancer: irqbalance. [OK] Loading cpufreq kernel modules... done (acpi-cpureq). [OK] CPUFreq Utilities: Setting ondemand CPUFreq governor... CPU0... CPU1... done. [OK] Starting SANE Network scanner server: saned. Starting X display manager: slim. [OK] Starting OpenBSD Secure Shell server: sshd. Applying Power save settings... done. Setting battery charge thresholds... done. [warn] VirtualBox Additions disabled, not in Virtual Machine... (warning). [OK] Starting Network connection manager: wicd. Debian GNU/Linux buster/sid Sat2aX2 tty1 Sat2aX2 login: axTest Password: Last login: Sun Apr 20 21:28:22 BST 2019 on tty1 No mail. [84.482465] elogind-daemon[1983]: New session 2 of user axTest. axTest@Sat2aX2:~When I try “startx” I get:
startx xauth: timeout in locking authority file /home/axTest/.Xauthority xauth: timeout in locking authority file /home/axTest/.Xauthority [EE] Fatal server error: [EE] Cannot open log file: "/home(axTest/.local/share/xorg/X.org.1.log" [EE] [EE] Please consult the The X.org Foundation .... [EE] xinit: unable to connect to X server: Connection refused xinit: server error xauth: timeout in locking authority file: /home/axTest/Xauthority axTest@Sat2aX2:~When I do “sudo startx” I get a IceWM root session without the wallpaper. And when I try to log in into this forum I’m not able to enter my username or password. I just can’t type anything in the two boxes.
When I try to change to one of the other Desktops (rox-fluxbox, space-icewm, etc) the system just logs me out of the session and gives me the CLI back
When I update the system everything seems to go as usual except for some problem with /usr/bin/mandb
root@Sat2aX2:~ # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: antix-libs bash packageinstaller-pkglist 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1,508 kB of archives. After this operation, 1,024 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://ftp.gr.debian.org/debian testing/main amd64 bash amd64 5.0-4 [1,378 kB] Get:2 http://repo.antixlinux.com/testing testing/main amd64 antix-libs all 0.6.15 [85.3 kB] Get:3 http://repo.antixlinux.com/testing testing/main amd64 packageinstaller-pkglist all 0.2.17 [45.0 kB] Fetched 1,508 kB in 14s (104 kB/s) (Reading database ... 274011 files and directories currently installed.) Preparing to unpack .../archives/bash_5.0-4_amd64.deb ... Unpacking bash (5.0-4) over (5.0-3) ... Setting up bash (5.0-4) ... update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide /usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode (Reading database ... 274011 files and directories currently installed.) Preparing to unpack .../antix-libs_0.6.15_all.deb ... Unpacking antix-libs (0.6.15) over (0.6.13) ... Preparing to unpack .../packageinstaller-pkglist_0.2.17_all.deb ... Unpacking packageinstaller-pkglist (0.2.17) over (0.2.16) ... Setting up packageinstaller-pkglist (0.2.17) ... Setting up antix-libs (0.6.15) ... Installing new version of config file /etc/sudoers.d/antixers ... Processing triggers for man-db (2.8.5-2) ... /usr/bin/mandb: can't chmod /var/cache/man/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/vi/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/vi/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/vi/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/cs/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/cs/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/cs/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/sr/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/sr/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/sr/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/sv/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/sv/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/sv/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/ru/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/ru/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/ru/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/zh_TW/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/zh_TW/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/zh_TW/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/fr.ISO8859-1/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/fr.ISO8859-1/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/pt/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/pt/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/pt/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/fr/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/fr/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/fr/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/hr/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/hr/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/hr/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/fr.UTF-8/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/fr.UTF-8/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/fr.UTF-8/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/id/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/id/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/id/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/fi/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/fi/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/fi/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/pl/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/pl/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/pl/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/es/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/es/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/es/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/pt_BR/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/pt_BR/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/pt_BR/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/da/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/da/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/da/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/tr/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/tr/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/tr/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/nl/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/nl/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/nl/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/ko/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/ko/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/ko/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/ja/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/ja/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/ja/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/de/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/de/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/de/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/it/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/it/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/it/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/zh_CN/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/zh_CN/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/zh_CN/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/hu/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/hu/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/hu/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/sl/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/sl/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/sl/4658: Permission denied /usr/bin/mandb: can't chmod /var/cache/man/oldlocal/CACHEDIR.TAG: Operation not permitted /usr/bin/mandb: can't remove /var/cache/man/oldlocal/CACHEDIR.TAG: Permission denied /usr/bin/mandb: fopen /var/cache/man/oldlocal/4658: Permission denied Processing triggers for menu (2.1.47+b1) ... root@Sat2aX2:~ # apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. root@Sat2aX2:~ #Trying to find something out of normal related to xauth, the only thing I could notice is the difference in size between the files .Xauthority of my Testing install (104 B) and of my Stable install (53 B). My blind guess is that there may be a problem with my /home/axTest/.Xauthority file. Its permissions are “r–- r– –– —”.
Thanks for trying to help,
ZehAnonymous
Hi zeh,
my Xauthority has the first one rw and the rest empty. “rw-,—,—/—”
That’s on my stable install. and is 54b in size.Hi zeh,
my Xauthority has the first one rw and the rest empty. “rw-,—,—/—”
That’s on my stable install. and is 54b in size.To my surprise, my Testing .Xauthority file is now 52b in size and its permissions are “rw-,—,—/—” just like yours, which means that either I made some mistake when I saw 104b or for some reason strange to me something made the info in the file to be doubled at a certain moment. My Stable .Xauthority file is 53b as said and its permissions are also “rw-,—,—/—”.
The facts that startx only works as root and “/usr/bin/mandb: can’t chmod /var/cache/man/CACHEDIR.TAG: Operation not permitted” tell me that there still must be permissions problems I’ve not been able to identify.
- This reply was modified 4 years ago by zeh.
- This reply was modified 4 years ago by zeh.
- This reply was modified 4 years ago by zeh.
Dave
How much space do you have free in your partition / drive? Seems to be full…
df -h /
and
df -h /homeIf your home is on another partition.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
No, it seems to have plenty of space…
root@Sat2aX2:/home/axTest# df -h / Filesystem Size Used Avail Use% Mounted on /dev/sda9 19G 8.2G 9.8G 46% / root@Sat2aX2:/home/axTest# df -h /home Filesystem Size Used Avail Use% Mounted on /dev/sda7 50G 26G 22G 54% /home root@Sat2aX2:/home/axTest#Dave
Hmm, interesting the way the files were producing errors is quite common when the drive is full. Maybe an update is incomplete and needs a dpkg-configure -a but still shows as up to date when running apt again?
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
I’d found the dpkg-configure -a in my ddg searches and I’ve already done it. And I update the system every time I log into it without any noticeable issues.
Dave
Ok, what is your partition layout? Is /usr on a separate partition same as /home and being mounted incorrectly/with incorrect permissions?
Maybe check with “mount”.
Also with the upgrade maybe systemd was installed and it running… IIRC systemd would ignore a setting in fstab in favour of its own unit file.- This reply was modified 4 years ago by Dave.
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
My only separate partition is /home. systemd is not installed. Installed are libsystemd0, elogind and consolekit (just telling since I don’t know whether these are relevant or not).
Dave
Hmm ok, I am out of immediate ideas as to how file permissions could be messed up; especially when files are owned by root but not are not valid to uid=0.
Perhaps you could check/post your /var/log/apt/history.log and output of dpkg -l to see if something was removed that may be required.Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
sudo: /usr/bin/sudo must be owned by uid0 and have the set uid bit set
Yes, reinstall. Can’t guess how the system wound up in that state, or what else (whatall else) has become corrupted at this point.
Careful, Dave, we only have 3 guesses remaining… then we will be eaten by a grue
Dave
sudo: /usr/bin/sudo must be owned by uid0 and have the set uid bit set
Yes, reinstall. Can’t guess how the system wound up in that state, or what else (whatall else) has become corrupted at this point.
Careful, Dave, we only have 3 guesses remaining… then we will be eaten by a grue
Yes I agree, chances are low for finding a resolution.
Thought a few suggestions could be made and used / checked for this situation as well as others. If the problem is found; excellent. If not hopefully some knowledge is gained by someone, somewhere, at sometime.I know I have been caught more than once with altered fstab configs and filled partitions that make the system appear totally corrupt yet it is an easy fix. Having watched people update the system, power off in the middle and rerun with a report that it is all up to date… thought it might be worth mentioning the dpkg-configure -a as at least a few people have missed this when apt-get fails (uhrm falsely succeeds???).
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
… hopefully some knowledge is gained by someone, somewhere, at sometime.
As said before, this was my idea from the beginning. And at this time I find it very unlikely that it will be me learning anything else from this case. I just took the opportunity to try to scratch a little bit on the inners of the system, but things seem to be too messy (as skidoo pointed out before) for me to be able to take anything from it. Anyway, of course it’d be cool and maybe useful to somebody if someone would eventually understand what happened and how to recover the system to its normal state. If not, no problem at all. I’m not loosing any information and I’ll just reinstall as said before as well.
The history.log file is attached, but I couldn’t find a way of copying from the terminal the huge list resulting from dpkg -l. I can just copy what’s visible on the terminal window. If you’d still like to have a look at it, please give me a hint on how to get the entire list into a file so that I can attach it to a subsequent post.Edit: the system returned a message telling that the file is not permitted for security reasons. It’s a very long file so I’m not posting its contents in a post.
- This reply was modified 4 years ago by zeh.
Dave
You can use
> file.txt
After the command to place the command output in a file. (and here you say that there is not much to learn 😉 )If you wanted to put a second command output to the same file you would use
>> file.txtAlso I think the forum will let you upload a zip/tar file. For a tar file:
tar -cf tar-file.tar file1.txt file2.txt
gzip tar-file.tarCannot at the moment recall how a zip file is made ( I use only tar really ). Can be found out by
man gzip
IircComputers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown
- You must be logged in to reply to this topic.
