I recently updated my OS to Fedora 10 and the latest Komodo Edit 5.1.0 build 3284 platform linux-libcpp6-x86_64. I never had this problem in the past, but every time I tried to open up a remote file, it refuses and with javascript error message: Error : 'No such component '@activestate.com/koFTPConnection;1''. With that, I could not open any file on my remote server.
Could anybody help me on this issue? I have essentially no knowledge on javascript and eager to make it work.
Looks as if the component registration has not occurred correctly.
Here are some ideas to try:
* did you install a new Komodo extension that may have caused this?
* try disabling an extension and restarting Komodo (this will trigger a component re-registration) - you can enable it again after the test.
* possible installation corruption, try a complete removal and then re-installation:
http://downloads.activestate.com/Komodo/releases/
Cheers,
Todd
Thanks for help and sorry for having misspelled remote as remove.
I did not do any extra except running install.sh.
disabling an extension does not help.
I will try to completely remove it and re-install.
I did re-install, and tried 5.1.1 version. The problem persists.
Check the Komodo log files, to see if there are any errors:
http://community.activestate.com/faq/komodo-file-locations#log_files
Thanks,
Todd
One more thing, it seems scim input (switching between language inputs) is not working. Any clue? Again, it was working before.
I don't think anything changed in regards to input handling in Komodo with the 5.1.0 release... not sure, the error logs may give an indicator here.
It seems the problem is that komodo edit requires libssl.so.0.9.8 importing ssl. However, my fedora 10 only has libssl.so.0.9.8g which may be quite different from the expected one without ending g.
Well, I can always copy the remote file to local, do the editing locally.
Thanks for help.
Hmmm... that seems strange. I had thought that Komodo uses a static Python build that included it's own set of the ssl dependencies, so it should not be relying upon the system ssl libraries.
Is there a specific error in the log file that you can post?
Thanks,
Todd
I've logged a bug on this problem here:
http://bugs.activestate.com/show_bug.cgi?id=82656
Cheers,
Todd