Notices

I'm running out of ideas here. From the icon, MediaBox won't start. From xTerm, I get the following:
Traceback (most recent call last):
File "/usr/bin/MediaBox", line 3, in <module>
from com import Container
File "/home/builder1/maemo-diablo-armel-extras-devel/work/mediabox-0.96.5/debian/mediabox/usr/lib/mediabox/com/__init__.py", line 11, in <module>
File "/home/builder1/maemo-diablo-armel-extras-devel/work/mediabox-0.96.5/debian/mediabox/usr/lib/mediabox/com/Component.py", line 5, in <module>
File "/home/builder1/maemo-diablo-armel-extras-devel/work/mediabox-0.96.5/debian/mediabox/usr/lib/mediabox/com/Mediator.py", line 5, in <module>
File "/home/builder1/maemo-diablo-armel-extras-devel/work/mediabox-0.96.5/debian/mediabox/usr/lib/mediabox/com/MessageBus.py", line 7, in <module>
File "/home/builder1/maemo-diablo-armel-extras-devel/work/mediabox-0.96.5/debian/mediabox/usr/lib/mediabox/utils/logging.py", line 6, in <module>
ImportError: No module named traceback

Jim

This looks a lot like your python-runtime installation is broken and missing a few things. Try reinstalling it.

That's exactly the conclusion I came up with. Unfortunately, I haven't been able to get it reinstalled correctly. I read one suggestion for upgrading to python2.5 by first uninstalling python2.4, but first removing all applications that use python first. But how do you know all the applications that depend on it? I tried it anyway and removed all that I could guess might depend on it and installed 2.5, but still no luck.
Thanks for you help.

OK - I bit the bullet and reflashed, and restored the backup. That appears to have fixed the problem.
Jim