← Back to team overview

openshot.developers team mailing list archive

[Bug 459148] [NEW] OpenShot won't launch - invalid literal for int error

 

Public bug reported:

I'm using Ubuntu 9.04 32-bit. Installation went perfectly with the new
deb installers, and I even opened up the app and edited and exported
without incident. Restarted the system, again opened the app and
edited... and then suddenly saw a crash (unfortunately didn't log
anything)

Now any time I try to launch the app, I see the following:

Traceback (most recent call last):
  File "/usr/local/bin/openshot", line 50, in <module>
    main()
  File "/usr/share/openshot/openshot.py", line 40, in main
  File "/usr/share/openshot/classes/lock.py", line 69, in check_pid
ValueError: invalid literal for int() with base 10: ''

So I removed the packages and tried the build wizard, but I'm getting
the same error. I see some bugs to which this appears similar, but it
appears the specific conditions here are slightly different.

** Affects: openshot
     Importance: Undecided
         Status: New

-- 
OpenShot won't launch - invalid literal for int error
https://bugs.launchpad.net/bugs/459148
You received this bug notification because you are a member of OpenShot
Developers, which is subscribed to OpenShot Video Editor.

Status in OpenShot Video Editor: New

Bug description:
I'm using Ubuntu 9.04 32-bit. Installation went perfectly with the new deb installers, and I even opened up the app and edited and exported without incident. Restarted the system, again opened the app and edited... and then suddenly saw a crash (unfortunately didn't log anything)

Now any time I try to launch the app, I see the following:

Traceback (most recent call last):
  File "/usr/local/bin/openshot", line 50, in <module>
    main()
  File "/usr/share/openshot/openshot.py", line 40, in main
  File "/usr/share/openshot/classes/lock.py", line 69, in check_pid
ValueError: invalid literal for int() with base 10: ''

So I removed the packages and tried the build wizard, but I'm getting the same error. I see some bugs to which this appears similar, but it appears the specific conditions here are slightly different.



Follow ups

References