Bugzilla – Bug 9265
Codeina fails to start
Last modified: 2009-06-02 14:37:04 UTC
You need to log in before you can comment on or make changes to this bug.
With /usr/bin/python -> /usr/bin/python2.5 or /usr/bin/python2.6 I get the following: ~ >codeina Traceback (most recent call last): File "/usr/bin/codeina.bin", line 115, in <module> add_codeina_path() File "/usr/bin/codeina.bin", line 64, in add_codeina_path from codeina.configure import LIBDIR, LOCALEDIR ImportError: No module named codeina.configure With /usr/bin/python -> /usr/bin/python2.4, the system hard-crashed the first time I ran codeina. Now, it will simply seg fault (python 2.5 and python2.6 cases are as above). I verified that the codeina libraries are only installed for python 2.4. This was after having updated from an up-to-date 2008.11a system to 2008.11b. I had not previously tried codeina, and I have not had it run from the browser.
Hi, Brandon, for 2008.11 in your description, I assume it is 2009.06, right?
move to gnome
(In reply to comment #1) > Hi, Brandon, for 2008.11 in your description, I assume it is 2009.06, right? Hi harry, Yes, I just updated to 2009.06 using package manager. The original installation was 2008.11. When I performed the latest update today, I believe /usr/bin/python was point to /usr/bin/python2.5. I doubt that made any difference. If you need me to collect any debug/trace information let me know what to do.
codeina should use python2.4, reporter, you can use totem/rhythmbox to play a mp3 file, codeina should be poped up automatically.
In my OpenSolaris 111b, python is pointing to python2.4. If I run it from terminal, I can see the following warning messages: Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/codeina/providers.py", line 126, in get_all_product_lists File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 49, in parse File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 69, in _parse_products File "/usr/lib/python2.4/site-packages/codeina/fxml.py", line 177, in parseFromTable File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 95, in _parse_product File "/usr/lib/python2.4/site-packages/codeina/fxml.py", line 177, in parseFromTable File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 171, in _parse_flavor File "/usr/lib/python2.4/site-packages/codeina/check.py", line 62, in __init__ ValueError: empty version string Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/codeina/providers.py", line 126, in get_all_product_lists File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 49, in parse File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 69, in _parse_products File "/usr/lib/python2.4/site-packages/codeina/fxml.py", line 177, in parseFromTable File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 95, in _parse_product File "/usr/lib/python2.4/site-packages/codeina/fxml.py", line 177, in parseFromTable File "/usr/lib/python2.4/site-packages/codeina/productlistparser.py", line 171, in _parse_flavor File "/usr/lib/python2.4/site-packages/codeina/check.py", line 62, in __init__ ValueError: empty version string But codeina window could show up successfully and allow me to login. What is your error when python->python2.4 and running codeina in a terminal?
(In reply to comment #4) > codeina should use python2.4, > > reporter, you can use totem/rhythmbox to play a mp3 file, > codeina should be poped up automatically. If I try to play an .mp3 file from totem, I get: The playback of this movie requires a MPEG-1 Layer 3 (MP3) decoder plugin which is not installed. If I try to play an .avi file from totem, I get the following: The playback of this movie requires the following decoders which are not installed: MPEG-1 Layer 3 (MP3) decoder ITU H.264 decoder From Rhythmbox, I get the following for mp3: The GStreamer plugins to decode "MP3" files cannot be found. Searching for "gstreamer" in package manager shows "clutter-gst - gstreamer integration library for clutter", and "Python bindings for the GStreamer streaming media framework". I only had the Python bindings installed. After installing the clutter integration library, the situation didn't improve.
When you say "With /usr/bin/python -> /usr/bin/python2.5 or /usr/bin/python2.6 I get the following", do you mean that you are modifying the /usr/bin/python symlink to point to a different python than 2.4? If so, then I would expect codeina and a lot of other desktop programs to not work properly. Does it work okay if /usr/bin/python is pointing to Python 2.4? To fix codeina so it is immune to this sort of change, it would be good to fix codeina so it uses a specific version of python rather than the /usr/bin/python symlink. However, I'd expect you would have problems with other programs changing the symlink like that. The traceback you describe is a known issue. Refer to codeina bug #208. This is not a serious problem. Codeina works fine even with this traceback. Ignore it while we fix the issue. https://core.fluendo.com/gstreamer/trac/ticket/208 I also think you are also running into codina bug #210. https://core.fluendo.com/gstreamer/trac/ticket/210 Run codeina by hand from a terminal window and you can download the MP3 plugin for free, and consider purchasing the other plugins you need to play media. I suspect the problem with codeina not autolaunching and presending these choices to you automatically are due to a bug in the Fluendo server. Note that the revision 8 of the codecs were just released last week, and I suspect some error on the server is causing GStreamer-based programs to not properly launch codeina when you try to play a media file that would work if you got a plugin from Fluendo.
Note that the problem was upstream in the codeina server as I guessed. This has now been fixed. They fixed both bug #208 and #210. Both issues were in the server. So now the traceback you reported when you run codiena should go away as well. However, users who tried running codeina before this server issue was fixed will have corrupted their codeina configuration. To fix this, you need to remove the following file before re-running codeina (or any program which tries to launch codeina). rm ~/.local/share/codeina/providers/fluendo.xml This is documented in codeina bug #210 if you want more information. When we update to codeina 0.10.5, then the need to remove this file will go away since codeina will take care of the problem automatically at that point. However, it will take some time to make the new codeina 0.10.5 available. So, for now I would remove that file, and try again, and it should now work.