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

bug: eperm: Operation not permitted #240

Open
GeckoEidechse opened this issue Jul 10, 2024 · 7 comments · May be fixed by #249
Open

bug: eperm: Operation not permitted #240

GeckoEidechse opened this issue Jul 10, 2024 · 7 comments · May be fixed by #249
Labels
bug Something isn't working

Comments

@GeckoEidechse
Copy link
Contributor

GeckoEidechse commented Jul 10, 2024

Describe the bug
From a ticket on the Northstar Discord. See screenshot below

i keep on having a error trying to press the install button on viper i cant find the location of the titanfall2 app on my files either

Screenshots
image

Version:
Not known yet

Additional Info
Any extra info should go here!

@GeckoEidechse GeckoEidechse added the bug Something isn't working label Jul 10, 2024
@GeckoEidechse
Copy link
Contributor Author

They are using EA App, my assumption is cause of the general perms issue around EA App / Program Files dir

@0neGal
Copy link
Owner

0neGal commented Jul 10, 2024

Does the EA App only remove the write permission on the files inside it? Or is the folder itself also missing it? For the prior, I guess the files inside it should also be checked, for the latter, I wonder if the permission checking just flat out doesn't work on Windows. I've never actually tested it, so that's not entirely improbable, given that this should technically be dealt with by the permission checks that's done...

@GeckoEidechse
Copy link
Contributor Author

Not too sure tbh. For FlightCore I just do a check for the default path and then show a corresponding warning message. Seems to work well enough where any tickets surrounding it are just about how to move the files, not the error message itself.
Don't think I even check perms lol.

@0neGal
Copy link
Owner

0neGal commented Jul 10, 2024

�Ah I see fair, I was considering doing that, however if the permission checking overall is just broken then there's still a bug present :p

Would you be able to check the permissions, or just create your own gamepath create a Titanfall2.exe in it, remove permissions from it, then try to get Viper to use it as the gamepath, and see if it shows a proper error or not?

@GeckoEidechse
Copy link
Contributor Author

Would you be able to check the permissions, or just create your own gamepath create a Titanfall2.exe in it, remove permissions from it, then try to get Viper to use it as the gamepath, and see if it shows a proper error or not?

Sadly I don't have time (or access to a Windows machine) to test atm :/

@0neGal
Copy link
Owner

0neGal commented Jul 10, 2024

That's fine, no worries :)
I'll likely be able to get around to it, at some point™

@Jan200101 Jan200101 linked a pull request Aug 4, 2024 that will close this issue
@GeckoEidechse
Copy link
Contributor Author

Another case reported just now

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants