In Linux i have as many files.
( /opt/Komodo/bin → 1 file (komodo), /opt/Komodo/lib → 4 folders (mozilla, python, sdk, support), /opt/Komodo/share → 1 folder with icons and “doc” file). In Windows a lot more files and folders?
Because file “pystderr.log” located in C:/Users/{Profile}/AppData/(?)/Komodoedit(ide)/8.5". (wrong, @nathanr says correct path below) OR “~/.komodoedit/8.5/” (Linux).
And you can use “Search” in Windows to find pystderr.log.
I am having the same problem on Windows 7 64-bit. It installed. It crashes when tried to run. I have python 2.7 and python 3.4 installed on my computer however shouldn’t it be looking for python 2.7 under ~\Komodo\lib\python? There are the four directories under lib that you have been talking about: mozilla, python, sdk, and support. There are plenty of files under those sub-directories under the sub-directory lib. By the way, I do not get any errors. It never gets going.
Thank You,
Micah
This is marked as “resolved” but I’m not seeing the resolution? I also have this problem – Windows 7 (64 bit), Komodo Edit crashes almost immediately, no splash screen or program window ever appears.
I actually had this problem before and found a work-around, but apparently didn’t document that. After wiping out my system and reinstalling everything, I’m back to not being able to use Komodo Edit.
Today I tried uninstalling, deleting all relevant folders in AppData, downloading a fresh install file, and reinstalling, but it still fails. The pystderr.log file is empty (0 bytes), as is pystdout.log. There is a startup-env.tmp file, though, that is not empty. I found it interesting that there is a reference to my VirtualBox installation location in that file…?
Finally had a chance to try it. No go, but different results. It crashes during launch, no program window or splash screen, but instead of the ActiveState crash reporter I just get the standard Windows dialog, telling me “ActiveState Komodo has stopped working” and giving me the option to check online for a solution or just close. The “problem details” – in case that info is helpful, even if not relevant to the problem discussed in this thread – are shown below.
Problem signature:
Problem Event Name: APPCRASH
Application Name: komodo.exe
Application Version: 9.0.0.0
Application Timestamp: 549a17d5
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18247
Fault Module Timestamp: 521ea8e7
Exception Code: c0000005
Exception Offset: 00038e19
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
I forgot to mention that the way I found (again) the thread that helped me with the work-around the first time was by doing some Web searches on the info in the Details dialog of the ActiveState crash reporter when Komodo Edit crashed. Those took me to discussions about Mozilla, and that triggered my memory of the work-around. I don’t know if that helps confirm the Mozilla connection, but I figured I’d mention it.
I finally had time to try again to get Komodo Edit working on my system, now using the lasted version 9 release (downloaded today, but I can’t get to any kind of a help menu* to check the actual version number). I removed everything I could find on disk and in the registry related to Komodo Edit, and then did a fresh install. Trying to run it caused it to crash before the program window displayed. I then returned to this thread for reference and followed the steps outlined above, and once again this worked to get to a point where the program launches successfully.
Curiously, when I was running it with --raw -safe-mode all of the toolbar icons were emoticons, which made it interesting to find my way to the “preview” option. Luckily that problem went away when I restarted without those command line options.
Anyway, whatever was going on in Komodo Edit 8 regarding graphics acceleration and/or the Mozilla version seems to still be in effect in version 9.
*Regarding the help menu, clicking the three-stacked-bars icon in the upper-right will show a partial effect as if it’s trying to open the menu but what should be the menu is only about 10 pixels high despite being what looks to be a correct width. I assume this is a separate issue entirely, so I only mention this here to explain my earlier comment.
Updated to add: Found that I could enable the menu bar, giving access to Help | About, thus: version 9.1.0, build 15798, platform win32-x86