- #Openshot software how to
- #Openshot software windows 10
- #Openshot software code
- #Openshot software windows
I mention in #2976 (comment) and its followup that there are Qt variables ( QStandardPaths) for those things that, I agree, we should be using instead. I have noticed that running OpenShot from a MinGW shell will cause OpenShot to use the MinGW home directory instead of C:\Users\ username\, which may be due to MinGW setting $HOME. ~ is a Unix shortcut for $HOME, so it is possible that it's unexpectedly influenced by the existence of a HOME environment variable. OpenShot finds the path to your user directory with the Python command os.path.expanduser("~").
#Openshot software code
OpenShot doesn't actually use the environment variable HOME, at least not directly, and I certainly can't find any code that would create that variable. I wouldn't imagine so, but when dealing with issues like this I find it's best to be extra-careful.īy the way, another bug I found in OpenShot was its undocumented use of the HOME environment variable, which overrides C:\users\USER and thus creates confusion by creating. openshot_qt from the C:\users\USER directory, using the Shift key to delete it permanently (which can't make a difference, by the way).
#Openshot software how to
(We just have to figure out how to do it without creating the same problem, since the installer runs as Administrator.)ĭid you try manually creating a C:\Users\USER\.openshot_qt folder, as a regular user, before running OpenShot (as a regular user)?Ģ.
#Openshot software windows
That should fix the permissions issue starting OpenShot as a regular user, and if it does maybe we can add some tools to the Windows installer to optionally reset permissions. (You may want to use the Task Manager to make sure, or restart the computer first.) openshot_qt folder in your home directory, empty the trashcan to make sure it's been removed, and then CREATE that folder - right in your C:\Users\username\ folder and with the exact same name - before running OpenShot? All of this needs to be done from your regular account, WITHOUT admin privileges, and OpenShot needs to be completely stopped before you do it. If you could try one thing for me, it might help us get a better handle on this problem: Could you completely delete the. openshot_qt folder that's owned by Administrator, which will definitely prevent it from writing to that folder as a regular user. The fact that running it as an admin succeeds would seem to confirm that, but it also may be making the problem worse: when run like that, OpenShot will create an.
The only way that would fail is if your user account doesn't have permission to create folders in your own home dir. openshot_qt folder in your home directory should fix it, because OpenShot will automatically re-create that folder on startup.
#Openshot software windows 10
Some of the other developers may have better testing resources, but since I don't have access to a Windows 10 system, I rely on affected users to provide information that might help us solve it.įrom #1319 (comment) The problem is that it's a permission problem on your local computer, which is not something we can easily fix. Clearly that's not sufficient in some cases.) We believed that removing the settings directory should fix it, which is why that previous bug was closed. (It's not something that most Windows users experience at all, which is why we still haven't ascertained the exact cause of the issue. Which means that a bug in OpenShot could cause you to lose important data, or even prevent Windows from working at all.įor the security of your own system, please uncheck that box.Īnd if you're willing to work with us to find the problem, we can hopefully fix this properly. When started like that, OpenShot has access to modify every file on the system, even protected system files.
It's also a configuration we can't support, as OpenShot was not meant to be run with admin privileges. but first, on the issue of running OpenShot as an administrator: That may succeed in getting OpenShot to run, but it is a dangerous workaround that I would urge anyone to avoid trying. I'll copy my comment from #1319 here, since that is a closed issue.