You are not logged in.
Maybe I missed it: Have you tried to uninstall gradle by pacman -R gradle and clean everything left behind? Maybe some earlier update failed and the issue is caused by inconsistencies.
I tried, even remove .gradle folder, even from different user
Offline
I've looked at the pacman -Qkk output and was shocked by the vast number of altered files.
After thinking about possible causes I realised a lot of them are likely caused by the same misconfiguration that may be the cause of the gradle issue.
The filesystem package contains most of the default folders used by archlinux, let's investigate that first.
Please post the output of
# pacman -Qkk filesystem(the # designates the command needs to be run as root)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Or to check for changes to all packages:
# LC_ALL=C pacman -Qkk 2>&1 | grep -v ', 0 altered files' | tee /tmp/broken_packages.txt
cat /tmp/broken_packages.txt | curl -F 'file=@-' 0x0.stOffline
I've looked at the pacman -Qkk output and was shocked by the vast number of altered files.
After thinking about possible causes I realised a lot of them are likely caused by the same misconfiguration that may be the cause of the gradle issue.The filesystem package contains most of the default folders used by archlinux, let's investigate that first.
Please post the output of
# pacman -Qkk filesystem(the # designates the command needs to be run as root)
# sudo pacman -Qkk filesystem
warning: filesystem: /etc/fstab (Permissions mismatch)
backup file: filesystem: /etc/fstab (Modification time mismatch)
backup file: filesystem: /etc/fstab (Size mismatch)
backup file: filesystem: /etc/fstab (SHA256 checksum mismatch)
backup file: filesystem: /etc/group (Modification time mismatch)
backup file: filesystem: /etc/group (Size mismatch)
backup file: filesystem: /etc/group (SHA256 checksum mismatch)
backup file: filesystem: /etc/gshadow (Modification time mismatch)
backup file: filesystem: /etc/gshadow (Size mismatch)
backup file: filesystem: /etc/gshadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/hosts (Modification time mismatch)
backup file: filesystem: /etc/hosts (Size mismatch)
backup file: filesystem: /etc/hosts (SHA256 checksum mismatch)
backup file: filesystem: /etc/nsswitch.conf (Modification time mismatch)
backup file: filesystem: /etc/nsswitch.conf (Size mismatch)
backup file: filesystem: /etc/nsswitch.conf (SHA256 checksum mismatch)
backup file: filesystem: /etc/passwd (Modification time mismatch)
backup file: filesystem: /etc/passwd (Size mismatch)
backup file: filesystem: /etc/passwd (SHA256 checksum mismatch)
backup file: filesystem: /etc/resolv.conf (Modification time mismatch)
backup file: filesystem: /etc/resolv.conf (Size mismatch)
backup file: filesystem: /etc/resolv.conf (SHA256 checksum mismatch)
backup file: filesystem: /etc/shadow (Modification time mismatch)
backup file: filesystem: /etc/shadow (Size mismatch)
backup file: filesystem: /etc/shadow (SHA256 checksum mismatch)
backup file: filesystem: /etc/shells (Modification time mismatch)
backup file: filesystem: /etc/shells (Size mismatch)
backup file: filesystem: /etc/shells (SHA256 checksum mismatch)
backup file: filesystem: /etc/subgid (Modification time mismatch)
backup file: filesystem: /etc/subgid (Size mismatch)
backup file: filesystem: /etc/subgid (SHA256 checksum mismatch)
backup file: filesystem: /etc/subuid (Modification time mismatch)
backup file: filesystem: /etc/subuid (Size mismatch)
backup file: filesystem: /etc/subuid (SHA256 checksum mismatch)
warning: filesystem: /home (UID mismatch)
warning: filesystem: /home (GID mismatch)
warning: filesystem: /usr/bin (Permissions mismatch)
warning: filesystem: /usr/share (UID mismatch)
warning: filesystem: /usr/share/factory (UID mismatch)
warning: filesystem: /usr/share/factory/etc (UID mismatch)
warning: filesystem: /usr/share/man (UID mismatch)
warning: filesystem: /usr/share/man/man2 (UID mismatch)
warning: filesystem: /usr/share/man/man3 (UID mismatch)
warning: filesystem: /usr/share/man/man4 (UID mismatch)
warning: filesystem: /usr/share/man/man5 (UID mismatch)
warning: filesystem: /usr/share/man/man6 (UID mismatch)
warning: filesystem: /usr/share/man/man7 (UID mismatch)
warning: filesystem: /usr/share/man/man8 (UID mismatch)
warning: filesystem: /usr/share/misc (UID mismatch)
warning: filesystem: /usr/share/pixmaps (UID mismatch)
filesystem: 124 total files, 16 altered filesLast edited by ihitmani (2024-06-07 06:24:14)
Offline
Or to check for changes to all packages:
# LC_ALL=C pacman -Qkk 2>&1 | grep -v ', 0 altered files' | tee /tmp/broken_packages.txt cat /tmp/broken_packages.txt | curl -F 'file=@-' 0x0.st
Offline
warning: filesystem: /home (GID mismatch)
warning: filesystem: /usr/bin (Permissions mismatch)
warning: filesystem: /usr/share (UID mismatch)
warning: filesystem: /usr/share/factory (UID mismatch)
warning: filesystem: /usr/share/factory/etc (UID mismatch)
warning: filesystem: /usr/share/man (UID mismatch)
warning: filesystem: /usr/share/man/man2 (UID mismatch)
warning: filesystem: /usr/share/man/man3 (UID mismatch)
warning: filesystem: /usr/share/man/man4 (UID mismatch)
warning: filesystem: /usr/share/man/man5 (UID mismatch)
warning: filesystem: /usr/share/man/man6 (UID mismatch)
warning: filesystem: /usr/share/man/man7 (UID mismatch)
warning: filesystem: /usr/share/man/man8 (UID mismatch)
warning: filesystem: /usr/share/misc (UID mismatch)
warning: filesystem: /usr/share/pixmaps (UID mismatch)Combining those lines from filesystem -Qkk with the lines from the all packages check indicates
- changes to /etc look like normal configuration .
- /usr/bin has wrong permission
- some files/folders under /usr/bin have problems, but they are small in number.
- /usr/share and its subfolders are a huge mess .
- /home has incorrect settings and the folders under it (especially your $HOME folder) need to be checked separately.
Before we go any further, make sure you have backups of everything important to you.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
warning: filesystem: /home (GID mismatch) warning: filesystem: /usr/bin (Permissions mismatch) warning: filesystem: /usr/share (UID mismatch) warning: filesystem: /usr/share/factory (UID mismatch) warning: filesystem: /usr/share/factory/etc (UID mismatch) warning: filesystem: /usr/share/man (UID mismatch) warning: filesystem: /usr/share/man/man2 (UID mismatch) warning: filesystem: /usr/share/man/man3 (UID mismatch) warning: filesystem: /usr/share/man/man4 (UID mismatch) warning: filesystem: /usr/share/man/man5 (UID mismatch) warning: filesystem: /usr/share/man/man6 (UID mismatch) warning: filesystem: /usr/share/man/man7 (UID mismatch) warning: filesystem: /usr/share/man/man8 (UID mismatch) warning: filesystem: /usr/share/misc (UID mismatch) warning: filesystem: /usr/share/pixmaps (UID mismatch)Combining those lines from filesystem -Qkk with the lines from the all packages check indicates
- changes to /etc look like normal configuration .
- /usr/bin has wrong permission
- some files/folders under /usr/bin have problems, but they are small in number.
- /usr/share and its subfolders are a huge mess .
- /home has incorrect settings and the folders under it (especially your $HOME folder) need to be checked separately.Before we go any further, make sure you have backups of everything important to you.
is it possible to fix gradle only ?
Last edited by ihitmani (2024-06-07 12:38:14)
Offline
Your filesystem permissions are fundamentally broken, it borders a miracle that the only fallout you have is gradle not working, you need to fix this properly in general.
Last edited by V1del (2024-06-07 13:23:55)
Offline
I do think it is possible to fix your system by using a combination of chmod commands / removing packages / deleting folders / re-installing packages and other actions.
Practically all those actions will need to be done with root rights and sometimes put your system in an unworkable state requiring to execute the actions from chroots or live environments.
The potential for things getting lost is such that backupping stuff first is necessary .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline