You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. Download ALmoviesRenamer-4-Linux.tar.gz
2. Unpack it
3. Simply launch ./ALmoviesRenamer (under Gentoo x86_64)
What is the expected output? What do you see instead?
The expected output is the program running. What I get is just this error.
What version of the product are you using? On what operating system?
ALmoviesRenamer-4-Linux under Gentoo x86_64. ALmoviesRenamer-3.1-Linux worked
fine (except for the issue inside the IMDbPY library -
http://code.google.com/p/almoviesrenamer/issues/detail?id=2&can=1)
Please provide any additional information below.
This is the call trace:
./ALmoviesRenamer: /usr/lib32/libcrypto.so.1.0.0: no version information
available (required by /tmp/al-4-linux/libpython2.7.so.1.0)
./ALmoviesRenamer: /usr/lib32/libssl.so.1.0.0: no version information available
(required by /tmp/al-4-linux/libpython2.7.so.1.0)
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/cx_Freeze/initscripts/Console.py", line 27, in <module>
File "src/main.py", line 32, in <module>
File "src/exceptionhandler.py", line 5, in <module>
File "ExtensionLoader_PyQt4_QtCore.py", line 12, in <module>
ImportError: /tmp/al-4-linux/PyQt4.QtCore.so: undefined symbol:
_ZN7QLocale14scriptToStringENS_6ScriptE
I tried to google for the error to no avail. I also tried to replace some file
in the 3.1 version with the matching file inside the 4.0 version (e.g
library.zip, PyQt4.Qt*.so) without luck. I noticed that there are much more
files in the 3.1 version than in the 4.0 one. It seems that some kind of
reorganization happened, maybe this is the source of this weird error. Please,
provide a bugfix, I'm tired to reboot into Windows to rename my movies! :P
Original issue reported on code.google.com by [email protected] on 26 Jul 2012 at 8:13
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 26 Jul 2012 at 8:13The text was updated successfully, but these errors were encountered: