Hide Forgot
Description of problem: meld tops directly after program start with traceback Version-Release number of selected component (if applicable): meld-1.3.2-1.fc14.noarch How reproducible: Steps to Reproduce: 1. execute meld on a command line 2. 3. Actual results: meld stops with traceback: Traceback (most recent call last): File "/usr/bin/meld", line 91, in <module> missing_reqs("pygtk", pygtkver, e) File "/usr/bin/meld", line 77, in missing_reqs print _("Cannot import: ") + mod + "\n" + e TypeError: cannot concatenate 'str' and 'exceptions.ImportError' objects Expected results: meld shows a window Additional info:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hi Jobst, thanks very much for reporting this issue. Would it be possible for you to update to meld 1.4 and see if the issue is still present with that version? Thanks very much in advance & Regards, Dominic
(In reply to comment #2) Hi Dominic, I've downloaded meld 1.4 and 1.5 from its homepage (http://ftp.gnome.org/pub/gnome/sources/meld/) and installed both versions to /usr/local. Both versions stopped directly after their start with the message Import nicht möglich: pygtk (no import possible) No module named pygtk I've installed according to rpm -qa | grep -i pygtk: pygtk2-libglade-2.17.0-7.fc14.x86_64 pygtksourceview-2.10.1-2.fc14.x86_64 pygtk2-2.17.0-7.fc14.x86_64 I hope this may help, kind regards Jobst
Sorry for the delayed reaction Jobst. If actually have the same installation (Fedora 14 and packages with the exact same version), but cannot reproduce this issue here. I'd like to ask you to try opening a python shell and run following commands: >>> import pygtk >>> pygtk.require("2.0") If there doesn't appear any error message, then everything is fine. If an error message is displayed, please provide. In the latter case it is likely something is wrong with your python or pygtk2 installation.
Hi Dominic, I've did what you proposed and the results were bad. A $ which python showed me, that I'm using unintentionally another python on my box: the one from libreoffice. I've changed the PATH instead of writing a wrapper for libreoffice. Now everything's running fine again after resetting the path, sorry for my mistake and thank you for your help! Kind regards Jobst
Thanks very much for the feedback Jobst. Closing this ticket with this. :)