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

Encountered a bad program behavior #563

Closed
username00011 opened this issue Sep 16, 2017 · 3 comments
Closed

Encountered a bad program behavior #563

username00011 opened this issue Sep 16, 2017 · 3 comments

Comments

@username00011
Copy link

username00011 commented Sep 16, 2017

I was following the official kivy website tutorial to use buildozer to develop android apps. I was running in a conda environment with python 3 on ubuntu linux and ran setup. Without prompting for my approval or creating a log or providing any way I can see to reverse the changes, the program installed python 2.7 unto /usr making OS level changes.

This is 99999% bad program behavior and I can't tell now if this software is actually a virus which just injected code. Help. Please advise

@inclement
Copy link
Member

buildozer is not a virus. I don't know what you ran, and I'm not really clear what you believe it to have done. How did you install buildozer, what commands did you use, and what files exist now that apparently did not exist before?

@KeyWeeUsr KeyWeeUsr changed the title Kivy buildozer is possibly (likely) a virus Encountered a bad program behavior Sep 19, 2017
@KeyWeeUsr
Copy link
Contributor

Please do not mark our repository with keywords such as "virus" if you have no evidence and/or no steps to reproduce such an issue that could at least approach this behavior. It's not nice, nor reasonable thing to do.

@kivybot
Copy link

kivybot commented Oct 4, 2017

Hey there!

We're automatically closing this issue since the original poster (or another commenter) hasn't yet responded to the question or request made to them 14 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.

Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

(Please note that this is an automated comment.)

@kivybot kivybot closed this as completed Oct 4, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants