OpenShot / openshot-qt

OpenShot Video Editor is an award-winning free and open-source video editor for Linux, Mac, and Windows, and is dedicated to delivering high quality video editing and animation solutions to the world.
http://www.openshot.org
Other
4.25k stars 531 forks source link

OpenShot does not start #5288

Open MarcusNessensohn opened 1 year ago

MarcusNessensohn commented 1 year ago

I am getting an error message at start: openshot_error

I testet the versions: OpenShot-v3.1.1-x86_64 (64-Bit) OpenShot-v3.1.1-x86 (32-Bit) OpenShot-v3.1.1-daily-11529-95eccafc-08c2cdd1-x86_64

I need to mention that the folder /user/.openshot_qt was not created and I therefore do not have any logs.

Colorjet3 commented 1 year ago

Hello @mjn86. What operating system and version are you running? It looks like you are running into a permissions issue if the /home/username/.openshot_qt folder is not getting created.

It can also be that you need to enable the "Show Hidden Files" option.

Try performing a clean installation of Python: https://www.reddit.com/r/learnpython/comments/d5unwv/clean_python_installation/

MarcusNessensohn commented 1 year ago

Hi @Colorjet3 ,

My Windows version is: Microsoft Windows 10 Pro 10.0.19045 N/A Build 19045,

and my Python version: Python 3.11.4 Fresh installation of Python did not solve the issue.

Installing and/or running Openshot as admin did not solve the issue.

"Show hidden files" is on in my user directory. But isn't the /.openshot_qt folder supposed to be created during start, not during installation? It does get created if I just run "launch.py" in my Python IDE (but of course Openshot cannot properly start like that).

Colorjet3 commented 1 year ago

Hello @mjn86. Thank you for the information you provided.

  1. I am running Windows 10 Pro. I tried to check the version I am running and I noticed that Python is not even installed in my Windows 10 environment. I also do not see an application entry for Python in Add or Remove Programs.

  2. The c:\users\username.openshot_qt folder is supposed to get created when OpenShot starts for the 1st time. After that only certain files get updated.

I know that OpenShot requires Python (I don't know all the dependecies) so I am wondering if you can try this:

  1. Uninstall Python from Windows 10 via the Add or Remove Programs.
  2. Ensure that there is no entry in the Path environment.
  3. Ensure that if you see any entries for OpenShot in Add or Remove Programs that you uninstall those also.
  4. Now install the latest daily build #11529.
  5. Did this work?

If it did, then most likely there is a conflict with Python (What OpenShot expects vs. what you have installed). If this is the case, then I will need to escalate this to one of the two main technical leads.

By the way, do you get this error during installation or during the startup of OpenShot? Just confirming.

MarcusNessensohn commented 1 year ago

Thanks for taking the time @Colorjet3.

The error occurs at startup.

I did all the points you listed. Purging my system of Python and installing the latest daily build had no effect.

I'm now digging through the source code hoping to find which module it is missing exactly.

sewbacca commented 1 month ago

I have the exact same issue with 3.2.1 as well as the daily version. The .openshot directory also doesn't get created. It's probably worth noting that I have msys2 installed. According to strace no library is loaded which should interfere with with anything though:

$ strace ./openshot-qt | grep msys
--- Process 16988 loaded C:\msys64\ucrt64\bin\zlib1.dll at 00007ff9d62f0000
--- Process 16988 loaded C:\msys64\ucrt64\bin\libbz2-1.dll at 00007ff9b7ab0000
--- Process 16988 loaded C:\msys64\ucrt64\bin\liblzma-5.dll at 00007ff9b5a40000
--- Process 16988 loaded C:\msys64\ucrt64\bin\libgcc_s_seh-1.dll at 00007ff9ac330000
--- Process 16988 loaded C:\msys64\ucrt64\bin\libstdc++-6.dll at 00007ff927da0000
--- Process 16988 loaded C:\msys64\ucrt64\bin\libstdc++-6.dll at 00007ff927d90000
--- Process 16988 loaded C:\msys64\ucrt64\bin\libgcc_s_seh-1.dll at 00007ff9ac330000
Colorjet3 commented 1 month ago

Hello @sewbacca What operating system/version are your running?

sewbacca commented 1 month ago

Windows 10 Pro, 64bit.

I can give more details tomorrow if that would be helpful

Colorjet3 commented 1 month ago

Thank you @sewbacca.

I have a Windows 10 Pro environment as well and never had this issue. I also don't have msys64 installed. Let's try a few things:

  1. Go to Add or Remove programs and uninstall OpenShot. Pay attention for possibly having 2 entries for OpenShot if you had installed v2.5.x or v2.6.x previously. Uninstall any OpenShot installations.
  2. Go to c:\program files folder and look for Openshot Video Editor folder. If one exists, delete it manually.
  3. Go to c:\users\username\ and look for .openshot_qt folder. Delete the folder if one exists. Make sure that you have "show hidden files" option enabled.
  4. Uninstall msys64 or any flavor of it that is installed.
  5. Create a test folder in c:\users\username\ folder to ensure that you have full permissions to your user folder. Delete the test folder once confirmed.
  6. Make sure your Windows 10 has all the Microsoft updates.
  7. Make sure your computer has all the hardware drivers updated. Firmware included.
  8. Install v3.2.1 and give it a try.
  9. If step 8 fails let's run a health check in Windows environment by running these commands: a. Open an administrative command prompt. b. Run this: DISM.exe /online /cleanup-image /restorehealth <---this can take some time. c. Now run this: sfc /scannow d. Restart Windows. e. Re-install Openshot v3.2.1 and try again.

We will further troubleshoot based on your results.

sewbacca commented 1 month ago

I've done all these steps and I still get an error message, with still the exact same wording as OPs. I did Windows Update, hiding msys from PATH, firmware/driver update, windows health check, clean reinstallation of OpenShot. strace also confirmed that no msys64 dlls are being loaded, so it can't have interfered with anything.

Colorjet3 commented 1 month ago

Thank you @sewbacca for the FYI. I really don't know what else to try.

@jonoomph Any ideas on this?