Hello,
After installing the latest security update on macOS 10.13 I no longer seem to be able to launch TextMate.
When I try to open it, a number of windows get opened in the launchpad (those that were "hidden"), but before opening all other windows finishes, the program crashes (crash log is in attachment).
Does anyone have any idea how I could do any of the following: - find the contents of unsaved snippets - potentially "purge" the open windows and at least try to see if I can start TM in a clean fashion.
The only "useful" information I see in the crash log is:
Application Specific Information: old selected document ‘nil’, new selected document ‘Portfile’
I most definitely had a lot of files called "Portfile" opened when TextMate still worked, but I don't know where 'nil' comes into play. The rest looks the same as the garbage I get when mixing libc++ and libstdc++, but it's probably completely unrelated anyway.
Thank you very much, Mojca
PS: A bit of background information, in case it is relevant in any way (probably not).
I usually had quite some windows open, very often using TextMate as a "random notes, TODO lists, temporary copy-and-paste snippets which I get from somewhere and plan to use later, ...", a bunch of documents I had opened might no longer exist after the system reboot (I put a lot of stuff under /tmp/), a lot of them were never saved, but were automatically reopened every time when I rebooted the system (which has worked very reliably ever since Lion), ...
Mac has been nagging me to install security updates for quite a while, and I kept pushing "remind me again tomorrow", until I finally did it, but ever since I wasn't able to fire up TextMate again, and this is one of my top programs I use. I'm still on 10.13, I did download both 10.14 and 10.15, but never decided to actually upgrade. Curious enough, during the last security update the computer suddenly notified me that it failed to upgrade the OS (gosh, I never asked my mac to do even do that, but at least I'm happy that it didn't do an automatic upgrade). I don't know if any of that has anything to do with TextMate, but I would be grateful for any advice or hint about proceeding.
Install 10.15.1
el
— Sent from Dr Lisse’s iPhone Xs On 31 Oct 2019, 14:29 +0200, Mojca Miklavec mojca@macports.org, wrote:
Hello,
After installing the latest security update on macOS 10.13 I no longer seem to be able to launch TextMate.
When I try to open it, a number of windows get opened in the launchpad (those that were "hidden"), but before opening all other windows finishes, the program crashes (crash log is in attachment).
Does anyone have any idea how I could do any of the following:
- find the contents of unsaved snippets
- potentially "purge" the open windows and at least try to see if I
can start TM in a clean fashion.
The only "useful" information I see in the crash log is:
Application Specific Information: old selected document ‘nil’, new selected document ‘Portfile’
I most definitely had a lot of files called "Portfile" opened when TextMate still worked, but I don't know where 'nil' comes into play. The rest looks the same as the garbage I get when mixing libc++ and libstdc++, but it's probably completely unrelated anyway.
Thank you very much, Mojca
PS: A bit of background information, in case it is relevant in any way (probably not).
I usually had quite some windows open, very often using TextMate as a "random notes, TODO lists, temporary copy-and-paste snippets which I get from somewhere and plan to use later, ...", a bunch of documents I had opened might no longer exist after the system reboot (I put a lot of stuff under /tmp/), a lot of them were never saved, but were automatically reopened every time when I rebooted the system (which has worked very reliably ever since Lion), ...
Mac has been nagging me to install security updates for quite a while, and I kept pushing "remind me again tomorrow", until I finally did it, but ever since I wasn't able to fire up TextMate again, and this is one of my top programs I use. I'm still on 10.13, I did download both 10.14 and 10.15, but never decided to actually upgrade. Curious enough, during the last security update the computer suddenly notified me that it failed to upgrade the OS (gosh, I never asked my mac to do even do that, but at least I'm happy that it didn't do an automatic upgrade). I don't know if any of that has anything to do with TextMate, but I would be grateful for any advice or hint about proceeding.
TextMate mailing list TextMate@lists.macromates.com https://lists.macromates.com/listinfo/textmate
On 31 Oct 2019, at 13:28, Mojca Miklavec wrote:
[…] the program crashes (crash log is in attachment).
Nothing was attached. It might not have submitted your crash report given that it crashes during launch, but you can check what has been submitted for your IP here https://api.textmate.org/crashes/myip will appreciate if you can link me to one of these.
Does anyone have any idea how I could do any of the following:
- find the contents of unsaved snippets
- potentially "purge" the open windows and at least try to see if I
can start TM in a clean fashion.
Hold down shift (⇧) when launching TextMate, and it will skip session restore.
The files will remain in this location, should there be unsaved changes you want to recover: ~/Library/Application Support/TextMate/Session
This might be irrelevant, but it sounds like TextMate is trying to reopen windows that it previously had open. To prevent that, go to ~/Library/Saved Application State and throw away the saved state for TextMate. Maybe it won't solve the issue but at least it will take the windows out of the equation. :) m.
On Oct 31, 2019, at 5:28 AM, Mojca Miklavec mojca@macports.org wrote:
After installing the latest security update on macOS 10.13 I no longer seem to be able to launch TextMate.
-- matt neuburg, phd = http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 13! http://shop.oreilly.com/product/0636920310075.do iOS 13 Fundamentals! http://shop.oreilly.com/product/0636920310068.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
Dear Allan,
On Thu, 31 Oct 2019 at 14:11, Allan Odgaard wrote:
On 31 Oct 2019, at 13:28, Mojca Miklavec wrote:
[…] the program crashes (crash log is in attachment).
Nothing was attached.
I'm trying again. Maybe I forgot to actually add the attachment last time, I'm sorry for that.
It might not have submitted your crash report given that it crashes during launch, but you can check what has been submitted for your IP here https://api.textmate.org/crashes/myip will appreciate if you can link me to one of these.
It wants to have my password. If I click cancel, there's an empty list.
The crash report wants to go to Apple though, I doubt that it would reach you (= that this is the type of report that would reach you).
Does anyone have any idea how I could do any of the following:
- find the contents of unsaved snippets
- potentially "purge" the open windows and at least try to see if I
can start TM in a clean fashion.
Hold down shift (⇧) when launching TextMate, and it will skip session restore.
The files will remain in this location, should there be unsaved changes you want to recover: ~/Library/Application Support/TextMate/Session
Awesome, thank you.
I first made a copy of all the files inside the session, which was one of the more important parts :)
After holding the shift key, TextMate launched without any problem and told me that it sent the crash reports. I guess that's the one that eventually went to you rather than Apple :)
And indeed ... now I see some 15 crash reports listed on the page that you pointed me to.
Thank you very much, Mojca
-
Allan Odgaard -
Eberhard W Lisse -
Matt Neuburg -
Mojca Miklavec