Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
I use Print Live all the time. Tried to open the app this morning and the 'unexpectedly quit' notice. Couldn't get it to open. Used an app cleaner to completely remove all the files and app and downloaded and installed again. Still crashes. Deleted again and rebooted. Installed again and more crashes.
I've made no changes/additions to my system in quite a while so have no idea what's causing the crashing.
Below is the crash report. Can anyone decipher what the problem is? Thanks in advance.
Process: PrintLife [518] Path: /Applications/PrintLife.app/Contents/MacOS/PrintLife Identifier: com.chronos.PrintLife Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: PrintLife [518] User ID: 503
Date/Time: 2018-03-18 12:04:40.723 -0700 OS Version: Mac OS X 10.12.6 (16G1212) Report Version: 12 Anonymous UUID: 74C13EAF-4F27-2D61-B8C2-2C493797506C
Time Awake Since Boot: 160 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1
kernel messages:
VM Regions Near 0 (cr2): --> __TEXT 00000001001c1000-0000000100378000 [ 1756K] r-x/rwx SM=COW
Thread 0 Crashed: 0 ??? 0x0000000102e6e000 _dyld_start + 0
Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff5fa3ec20 r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000 r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 rip: 0x0000000102e6e000 rfl: 0x0000000000000200 cr2: 0x0000000000000000 Logical CPU: 0 Error Code: 0x00000000 Trap Number: 0
Binary Images: 0x1001c1000 - 0x100377ff7 +??? (0) <D7ABE602-3F2A-37C4-8197-86C01D5CF88A> (null) 0x102e6d000 - 0x102eaadc7 +??? (433.5) <93EA668C-4BB2-3646-96E9-B406B81308D6> (null)
External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 95 thread_create: 0 thread_set_state: 0
VM Region Summary: ReadOnly portion of Libraries: Total=2172K resident=0K(0%) swapped_out_or_unallocated=2172K(100%) Writable regions: Total=8400K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8400K(100%) VIRTUAL REGION REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= STACK GUARD 56.0M 2 Stack 8192K 2 __DATA 540K 4 __LINKEDIT 168K 3 __TEXT 2004K 3 shared memory 8K 3 =========== ======= ======= TOTAL 66.7M 11
Model: Macmini6,2, BootROM MM61.010B.B00, 4 processors, Intel Core i7, 2.3 GHz, 8 GB, SMC 2.8f1 Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x859B, 0x435435313236344246313630422E43313646 Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x859B, 0x435435313236344246313630422E43313646 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (7.21.171.133.1a2) Bluetooth: Version 5.0.5f1, 3 services, 27 devices, 1 incoming serial ports Network Service: Ethernet, Ethernet, en0 Serial ATA Device: APPLE HDD HTS541010A9E662, 1 TB USB Device: USB 2.0 Bus USB Device: Hub USB Device: Keyboard Hub USB Device: Apple Keyboard USB Device: USB 2.0 Bus USB Device: Hub USB Device: Hub USB Device: IR Receiver USB Device: BRCM20702 Hub USB Device: Bluetooth USB Host Controller USB Device: USB 3.0 Bus USB Device: Apple USB SuperDrive USB Device: MX880 series Thunderbolt Bus: Mac mini, Apple Inc., 23.4
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1 To my inexpert eye, that looks like your culprit, but I can't begin to guess why it's reared its ugly head out of the blue. I suspect that PrintLife's developer will be best able to figure out what's going on. (Are all the crash reports the same?)
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
Yes all the crash reports the same.
I also tried a newer version of Printlife. Installed and I get the same crash report for the new version as well. Very weird. Unfortunately, Printlife provides virtually zero tech support.
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
I wonder if your setting in System Prefs > Security & Privacy > General > Allow apps downloaded from: has anything to do with your problem?
Maybe change it to "Anywhere" if it's not that already?
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
I've had this set to anywhere a very long time.
Is the 'code signing' you mentioned something within the App itself? I've had/used this app for a long time and it just stopped working in the past week.
I was poking around google and saw something about trust certificates is that the same as code signing? I have no idea what any of this is.
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 16
Moderator
|
Moderator
Joined: Aug 2009
Likes: 16 |
I have no way to verify the accuracy of my analysis but, add this, Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace CODESIGNING, Code 0x1 and this Unfortunately, Printlife provides virtually zero tech support. to this MacRumors article and it is a reasonable bet the developer either... - ...failed to renew the developer certificate or...
- ...the developer certificate was revoked by Apple
IF either is the case, the solution is for the developer to renew/re-provision his developer certificate or the user to find an alternate app.
If we knew what it was we were doing, it wouldn't be called research, would it?
— Albert Einstein
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
I purchased this app directly from the developer website not via App Store.
Does that change your analysis?
The newest version of PrintLife is available in the App Store. If I delete my current version and purchase from App Store would that eliminate this issue? In other words would the AppStore sell me an App with a bad code signature?
Last edited by Douglas; 03/18/18 11:18 PM. Reason: Add Question
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
...it is a reasonable bet the developer either... - ...failed to renew the developer certificate or...
- ...the developer certificate was revoked by Apple
IF either is the case, the solution is for the developer to renew/re-provision his developer certificate or the user to find an alternate app. Would you please explain why that isn't a Gatekeeper issue? Thanks.
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
I don't know what a Gatekeeper issue is?
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
I don't know what a Gatekeeper issue is? My question was directed at joemike, but Gatekeeper is the Apple functionality you overrode with System Prefs > Security & Privacy > General > Allow apps downloaded from: Anywhere.
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 16
Moderator
|
Moderator
Joined: Aug 2009
Likes: 16 |
If it were a gatekeeper issue the warning would be issued on installation or in some cases an option would be offered to override gatekeeper protection on execution, but no such option is offered in this case. The application is refusing to run because of an invalid code signature with no gatekeeper override offered.
If we knew what it was we were doing, it wouldn't be called research, would it?
— Albert Einstein
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
The application is refusing to run because of an invalid code signature with no gatekeeper override offered. Sorry, but my question missed the point. I thought the "Anywhere" setting overrode Gatekeeper's insistence on a signature. Is this an unusual occurrence or my failure to correctly comprehend Gatekeeper?
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
There was no kind of warning when I deleted the app and all of the files with APP CLEANER and then reinstalled using a newly downloaded DMG file.
The process was delete the app and files. Reboot. Download the app and install. No issues with this process but still won't open.
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 16
Moderator
|
Moderator
Joined: Aug 2009
Likes: 16 |
Is this an unusual occurrence or my failure to correctly comprehend Gatekeeper? Perhaps these Apple Support and MacRumors articles will clear up your understanding...
Last edited by joemikeb; 03/19/18 10:24 PM. Reason: add new material
If we knew what it was we were doing, it wouldn't be called research, would it?
— Albert Einstein
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
I just read the MacRumors article and that sounds exactly what happened here. I have not heard of other Chronos users reporting similar but they have almost zero tech support so it would be difficult to find out if other users are experiencing this.
I did download a newer test version, from their website, and experienced the same 'unexpectantly quit' problem as well, which seems to confirm this.
I also agree that once I have fully purchased an app, Apple should not be messing with it regardless of what the developer may have done after the fact.
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 16
Moderator
|
Moderator
Joined: Aug 2009
Likes: 16 |
I also agree that once I have fully purchased an app, Apple should not be messing with it regardless of what the developer may have done after the fact. Apple isn't "messing with the app" they have simply flagged the developers certificate as expired or invalid. In most cases once an app is installed, it is supposed to continue working, even if the developer's certificate subsequently expires or is revoked. The cause of this anomalous behavior will have to be worked out between the developer and Apple.
If we knew what it was we were doing, it wouldn't be called research, would it?
— Albert Einstein
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
I am thinking about purchasing the newer version from the App Store and if it doesn't work I'll just dispute the charge and be done with it.
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
I am thinking about purchasing the newer version from the App Store and if it doesn't work I'll just dispute the charge and be done with it. That's a solution, but I'd find it awfully unpalatable. Isn't there an alternative app? More: As per my next post, I'd give Chronos some time to get their act together before getting involved in a credit card dispute.
Last edited by artie505; 03/21/18 11:17 AM.
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
Is this an unusual occurrence or my failure to correctly comprehend Gatekeeper? Perhaps these Apple Support and MacRumors articles will clear up your understanding... Thanks for the links; they do, indeed, clarify things. The issue that Douglas has run into is clearly NOT a bug in macOS, but it sure isn't an easily comprehensible non-bug; beyond its seemingly making no sense, it seems like Apple has snuck it into its documentation without giving developers an adequate heads-up. At any rate, though, it's something that Chronos should and will fix promptly if they expect to continue selling $50 apps...unless their certificate has been revoked, that is. All considered, it doesn't seem the least bit likely that PrintLife d/l'ed from the App Store will work for Douglas, as it's the same version as the one on Chronos's website.
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
Chronos has essentially zero support. I've had a support request open for well over a year as has another poster. If you look at remarks on MacUpDate you will see what I mean. I even sent a certified letter to and that got a response and a promise of better support that never happened.
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 16
Moderator
|
Moderator
Joined: Aug 2009
Likes: 16 |
All considered, it doesn't seem the least bit likely that PrintLife d/l'ed from the App Store will work for Douglas, as it's the same version as the one on Chronos's website. It will be interesting to see whether it works or not. Version numbers are NOT a good indicator of differences between App Store and non-App Store versions of the same app. Apple's insistence on App Store versions being fully sand boxed often means the non-App Store version may have features that cannot be implemented if the app is sand boxed. I have encountered situations where... - the App Store version was not be able to fully implement some features due to App Store sand boxing requirements. (the database function in NeoOffice is a good example of that).
- there was a problem in the App Store version and the developer had me download the non App Store version until a sand boxed work around could be found and implemented
- there was a problem in the App Store version and the developer allowed me download the non App Store version until the sand boxed version could make its way through the App Store approve process (which was delayed because the developer elected to make the "fix" in a completely reworked upgrade.
- A feature in the app uses a function provided by importing code that is not App Store approved and Apple would not allow the non approved code embedded in it. The work around involves releasing the app in the App Store and giving the user a link to download the non-approved app so the approved app can import its functions — all with appropriate warnings of course.
In all of these cases the version number is the same inside and outside of the App Store. In at least one case there is a parenthetic "App Store" appended to the version number but that did not show up until the app was installed. If you run into missing features or reduced functionality in App Store versions, many developers will allow you to switch to the non App Store version at no charge since you already paid in the App Store. All it takes is an email or phone call to their tech support.
If we knew what it was we were doing, it wouldn't be called research, would it?
— Albert Einstein
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
Chronos has essentially zero support. I've had a support request open for well over a year as has another poster. If you look at remarks on MacUpDate you will see what I mean. I even sent a certified letter to and that got a response and a promise of better support that never happened. Yep, I've seen the posts at MacUpdate, but Chronos seems to be a reputable company, and they've got a nice portfolio of apps, others of which may have the same problem that PrintLife has got, so I'd expect that their failure to have responded to the problem immediately should NOT be taken as an indication that their apps won't be updated to overcome it, particularly if they're interested in remaining in business. This problem has only been sprung on them for only a few days, several of their apps may have to be updated, and I've got no idea how long the certificate/update process takes once it's actually begun.
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 2
|
OP
Joined: Aug 2009
Likes: 2 |
I downloaded the most current trial version of PrintLife from their website and I get the same 'Invalid Code Signature' error on this version as well. However, I downloaded the trail version of another Chronos app and that installed and worked fine.
Chronos does seem to be a legit company, I've used a number of their apps, and like them, but they have essentially zero tech support for any of their apps. I've searched for a telephone number but to no avail.
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
All considered, it doesn't seem the least bit likely that PrintLife d/l'ed from the App Store will work for Douglas, as it's the same version as the one on Chronos's website. It will be interesting to see whether it works or not. Version numbers are NOT a good indicator of differences between App Store and non-App Store versions of the same app. Apple's insistence on App Store versions being fully sand boxed often means the non-App Store version may have features that cannot be implemented if the app is sand boxed. I have encountered situations where... <snip> . Oops, I had forgotten about that ( for a rare change ), but lack of full functionality seems like something that ought to be prominently mentioned on Chronos's PrintLife page, and I didn't see any such.
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
Re: Read Crash Log?
|
Joined: Aug 2009
Likes: 15
|
Joined: Aug 2009
Likes: 15 |
I downloaded the most current trial version of PrintLife from their website and I get the same 'Invalid Code Signature' error on this version as well. However, I downloaded the trail version of another Chronos app and that installed and worked fine.
Chronos does seem to be a legit company, I've used a number of their apps, and like them, but they have essentially zero tech support for any of their apps. I've searched for a telephone number but to no avail. I also d/l'ed the latest version of PrintLife from Chronos's website with the same results you got, but I'd be inclined to give them some time, and I'd check their website, not MacUpdate, because v 4.0.1 was posted to the App Store on May 5, 2017, whereas it wasn't posted to MU until June 21, 2017. I note that Chronos's tech support policy is " Chronos aims to offer its customers a first-class support experience. Please visit our Support web site to get answers to any questions or problems you may have or to contact one of our support technicians." (Where did you find a street address to which to send snail mail?)
Last edited by artie505; 03/21/18 05:10 PM. Reason: More
The new Great Equalizer is the SEND button.
In Memory of Harv: Those who can make you believe absurdities can make you commit atrocities. ~Voltaire
|
|
|
|