Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prefscleaner.sh cannot start #1770

Closed
nsoci opened this issue Nov 23, 2023 · 11 comments
Closed

prefscleaner.sh cannot start #1770

nsoci opened this issue Nov 23, 2023 · 11 comments

Comments

@nsoci
Copy link

nsoci commented Nov 23, 2023

`prefsCleaner.sh canot start:
./prefsCleaner.sh
It looks like this script was previously run with elevated privileges,
you will need to change ownership of the following files to your user:
./user.js

Update work to version 119.
If I run updater.sh again it doesn't work and I got the same msg as I wrote above.`

Thank you.

@iam-py-test
Copy link

Just a thought, but can you run sudo chown [your username] user.js and see what happens?
Thanks

@nsoci
Copy link
Author

nsoci commented Nov 23, 2023

authentication failed
The user is owner of the file and I put write also for group wheel and I have options now to change the file.
Again edit: doas chow 'my user' user.js it happened nothing

@nsoci
Copy link
Author

nsoci commented Nov 23, 2023

The first time when I ru updater.sh and prefsCleaner.sh both works but lthe next time the problem.
I use clone github and download zip file and it is the same.

@iam-py-test
Copy link

Can you run ls -l user.js prefs.js updater.sh prefsCleaner.sh and see what it returns?
Thanks

@nsoci
Copy link
Author

nsoci commented Nov 23, 2023

Can you run ls -l user.js prefs.js updater.sh prefsCleaner.sh and see what it returns? Thanks

ls -l user.js prefs.js updater.sh prefsCleaner.sh
-rw------- 1 aj aj 27680 Nov 23 15:35 prefs.js
-rwxr-xr-x 1 aj aj 6167 Nov 23 12:52 prefsCleaner.sh
-rwxr-xr-x 1 aj aj 13953 Nov 23 12:52 updater.sh
-rw-r--r-- 1 aj aj 74634 Nov 23 12:52 user.js

@iam-py-test
Copy link

Thanks. That's bizarre. If I read that correctly, you should be able to modify those files.
Maybe someone smarter has an answer.

@element-wise
Copy link

element-wise commented Nov 23, 2023

The first time when I ru updater.sh and prefsCleaner.sh both works but lthe next time the problem.
I use clone github and download zip file and it is the same.

Can you please run ls -l user.js prefs.js updater.sh prefsCleaner.sh before and after running updater.sh and prefsCleaner.sh?

`prefsCleaner.sh canot start:
./prefsCleaner.sh
It looks like this script was previously run with elevated privileges,
you will need to change ownership of the following files to your user:
./user.js

Please also show us the command you're using to run these scripts. Are you running them as root or user aj?

@nsoci
Copy link
Author

nsoci commented Nov 24, 2023

I am running as user aj.
Before:
-rw------- 1 aj aj 27845 Nov 24 05:19 prefs.js
-rwxr-xr-x 1 aj aj 6167 Nov 23 12:52 prefsCleaner.sh
-rwxr-xr-x 1 aj aj 13953 Nov 23 12:52 updater.sh
-rw-r--r-- 1 aj aj 74634 Nov 23 12:52 user.js

After I run ./updater.sh which works now:
-rw------- 1 aj aj 27845 Nov 24 05:19 prefs.js
-rwxr-xr-x 1 aj aj 6167 Nov 23 12:52 prefsCleaner.sh
-rwxr-xr-x 1 aj aj 13953 Nov 23 12:52 updater.sh
-rw------- 1 aj wheel 75403 Nov 24 05:31 user.js

and now i the problem:
./prefsCleaner.sh
It looks like this script was previously run with elevated privileges,
you will need to change ownership of the following files to your user:
./user.js

I do not know why changing user.js aj to wheel?

Thank you for your time.

@rusty-snake
Copy link
Contributor

rusty-snake commented Nov 24, 2023

Did you changed your primary group to wheel rather than adding wheel as supplementary group?

What does id show?

@earthlng
Copy link
Contributor

Hi,

I removed the check for "is group == root/wheel" in both scripts, because it's probably enough to check the user only.
I don't think Firefox will mind either, as long as the user has read permissions on these files.

If you have auto-update enabled, both scripts should update themselves and the problem should be fixed.
Otherwise just update both scripts manually.

@Thorin-Oakenpants
Copy link
Contributor

I assume this worked? closing - feel free to ping me if it doesn't work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

6 participants