KomodoIDE Update 8.5.3 -> 8.5.4 Error on Mint Cinnamon

Support Resolved
1

KomodoIDE update 8.5.3 -> 8.5.4 on current Mint Cinnamon failed with the error message:

“The update could not be installed. Please make sure there are no other copies of Komodo IDE running on your computer, and then restart Komodo IDE to try again.”

No other Komodo processes are running.

Rebooting the system caused no change, Failure repeated.

?

Dave

2

Attach your log :smile:
~/.komodoide/8.5/pystderr.log

3

Another possibility is permissions, i.e. if you installed a root user, you’ll need to update as root user, or your Komodo installation is somehow read only?

4

Somehow I seem to have got it sorted - not quite sure how. It was owned & accessible to my user account & group. Just some bit of thickness on my part, I guess. I’ll send the log just in case.

Thanks,

Dave

[2014-09-09 18:27:10,281] [WARNING] koXMLPrefs: dePickleCache: Can’t open file u’/opt/Komodo-IDE-8/lib/support/prefs.xmlc’
[2014-09-09 18:27:10,281] [WARNING] koXMLPrefs: the dePickledCache object was None
[2014-09-09 18:27:10,312] [WARNING] koXMLPrefs: dePickleCache: Can’t open file u’/home/wittend/.komodoide/8.5/prefs.xmlc’
[2014-09-09 18:27:10,312] [WARNING] koXMLPrefs: the dePickledCache object was None
[2014-09-09 18:27:10,354] [WARNING] koXMLPrefs: dePickleCache: Can’t open file u’/home/wittend/.komodoide/8.5/view-state.xmlc’
[2014-09-09 18:27:10,355] [WARNING] koXMLPrefs: the dePickledCache object was None
[2014-09-09 18:27:10,355] [WARNING] koXMLPrefs: dePickleCache: Can’t open file u’/home/wittend/.komodoide/8.5/doc-state.xmlc’
[2014-09-09 18:27:10,355] [WARNING] koXMLPrefs: the dePickledCache object was None
[2014-09-09 18:27:10,631] [WARNING] koSkin: Detected GTK theme via libgtk: Mint-X
[2014-09-09 18:27:11,937] [WARNING] koDocument: For file test_pager_01.html, favoring contents language HTML5 over filename language HTML
[2014-09-09 18:27:12,489] [DEBUG] places_js: waiting for document complete
[2014-09-09 18:27:12,514] [WARNING] root: ko.findresults was already loaded, re-creating it.

5

This is full log?

6

Can you elaborate on how you fixed the issue for future users that might hit the same issue? That is if you know what you did to fix it…:wink:

  • Carey