Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - NeoOffice 2013 test patches corrupt installation
NeoOffice 2013 test patches corrupt installation
 
   NeoOffice Forum Index -> NeoOffice Testing
View previous topic :: View next topic  
Author Message
amayze
The Merovingian


Joined: Oct 24, 2005
Posts: 561
Location: Edinburgh, Scotland

PostPosted: Thu Aug 22, 2013 2:06 am    Post subject:

I've now installed NeoOffice 2013 Test 3 over my App Store version of NeoOffice. Unfortunately it has brought back the preferences problem with the Open at Launch setting.

Crash log attached.

Andy
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Thu Aug 22, 2013 7:19 am    Post subject:

amayze wrote:
I've now installed NeoOffice 2013 Test 3 over my App Store version of NeoOffice. Unfortunately it has brought back the preferences problem with the Open at Launch setting.


I have a feeling that patching an App Store installation might make Apple's App Sandbox code think the application has been corrupted.

Can you execute the following Terminal command and then relaunch NeoOffice 2013? Does it still crash crash?

Code:
sudo pkgutil --forget org.neooffice.NeoOfficeSecureEdition_patch.pkg


Patrick
Back to top
amayze
The Merovingian


Joined: Oct 24, 2005
Posts: 561
Location: Edinburgh, Scotland

PostPosted: Thu Aug 22, 2013 10:27 am    Post subject:

The forget command didn't work. In the end I had to delete the whole NeoOffice.localized folder again, use the rm command from the other thread and re-install NeoOffice from the App store.

Andy
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Thu Aug 22, 2013 5:38 pm    Post subject:

amayze wrote:
The forget command didn't work. In the end I had to delete the whole NeoOffice.localized folder again, use the rm command from the other thread and re-install NeoOffice from the App store.


I will look at our NeoOffice 2013 patch installer and see if I can identify why you don't have that pkgutil entry and I do.

Worst case is that I have to come up with a substitute for test patches but first I will see if I can figure out why any upgrade or patch corrupts your NeoOffice 2013 installation.

Patrick
Back to top
amayze
The Merovingian


Joined: Oct 24, 2005
Posts: 561
Location: Edinburgh, Scotland

PostPosted: Fri Aug 23, 2013 6:23 am    Post subject:

Just to clarify, the forget command did work in the sense that it ran and reported that the org.neooffice.NeoOfficeSecureEdition_patch.pkg package had been forgotten.

It didn't work in the sense that NeoOffice still crashed on launch after executing it.

Sorry my previous post wasn't very clear.

Andy
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Fri Aug 23, 2013 10:24 pm    Post subject:

amayze wrote:
Just to clarify, the forget command did work in the sense that it ran and reported that the org.neooffice.NeoOfficeSecureEdition_patch.pkg package had been forgotten.


Thank you for the clarification. I am just eliminating possible causes for the installer problems that you see one by one.

Since that command has no effect on your machine, my next theory is that the problem was caused by signing with different types of developer certificates. The Beta releases and the test patch both signed using our Developer ID certificate and the download from the Mac App Store is signed with a our 3rd Party Mac Developer certificate. So, if you are willing to try it, I have uploaded the following test patch that is signed with our 3rd Party Mac Developer certificate.

If you install the following test patch, does the crashing reoccur when launching NeoOffice 2013?:

NeoOffice 2013:
http://juliette.neooffice.org/test/NeoOffice-2013-Test-3-Debug-1-Intel.dmg

Patrick
Back to top
amayze
The Merovingian


Joined: Oct 24, 2005
Posts: 561
Location: Edinburgh, Scotland

PostPosted: Sat Aug 24, 2013 1:53 am    Post subject:

pluby wrote:
If you install the following test patch, does the crashing reoccur when launching NeoOffice 2013?:

NeoOffice 2013:
http://juliette.neooffice.org/test/NeoOffice-2013-Test-3-Debug-1-Intel.dmg

Unfortunately, yes it does.

Andy
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sat Aug 24, 2013 6:14 am    Post subject:

OK. Another question: if you launch the /Applications/Utilities/Console application and then launch NeoOffice 2013, are any new messages added in the Console application? If so, can you post them?

Also, if you run the following command and then try launching NeoOffice 2013, does it still crash?:

Code:
sudo pkgutil --forget org.neooffice.NeoOfficeSecureEdition


Patrick
Back to top
amayze
The Merovingian


Joined: Oct 24, 2005
Posts: 561
Location: Edinburgh, Scotland

PostPosted: Sat Aug 24, 2013 6:43 am    Post subject:

This is what I see on the Console:
Code:
24/08/2013 14:26:18.289 com.apple.launchd.peruser.502[229]: (com.apple.accountsd[3749]) Exited: Killed: 9
24/08/2013 14:26:20.248 com.apple.launchd.peruser.502[229]: (com.apple.tccd[3719]) Exited: Killed: 9
24/08/2013 14:26:38.659 com.apple.launchd.peruser.502[229]: (com.apple.cfprefsd.xpc.agent[3438]) Exited: Killed: 9
24/08/2013 14:27:09.645 com.apple.launchd.peruser.502[229]: (com.apple.cfprefsd.xpc.agent[3782]) Exited: Killed: 9
24/08/2013 14:27:40.364 SubmitDiagInfo[3806]: Launched to submit Diagnostics and Usage
24/08/2013 14:27:47.018 SubmitDiagInfo[3806]: Failed to load serverside whitelist, using cached list: Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “radarsubmissions.apple.com” which could put your confidential information at risk." UserInfo=0x7fbb41061b00 {NSURLErrorFailingURLPeerTrustErrorKey=<SecTrust>, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, NSUnderlyingError=0x7fbb404116b0 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “radarsubmissions.apple.com” which could put your confidential information at risk.", NSErrorPeerCertificateChainKey=(
    "<SecCertificate>",
    "<SecCertificate>",
    "<SecCertificate>"
), NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be “radarsubmissions.apple.com” which could put your confidential information at risk., NSErrorFailingURLKey=https://radarsubmissions.apple.com/macSubmissions/diagnosticwhitelist.jsp?osv=10.8.4, NSErrorFailingURLStringKey=https://radarsubmissions.apple.com/macSubmissions/diagnosticwhitelist.jsp?osv=10.8.4, NSErrorClientCertificateStateKey=0}
24/08/2013 14:27:48.398 SubmitDiagInfo[3806]: CFReadStreamCopyError() returned: The operation couldn’t be completed. (OSStatus error -9807.)
24/08/2013 14:27:48.398 SubmitDiagInfo[3806]: Failed to submit crash report: file://localhost/Users/andrewmay/Library/Logs/DiagnosticReports/soffice.bin_2013-08-24-094059_Andrew-May-New-Office.crash
24/08/2013 14:27:48.836 SubmitDiagInfo[3806]: CFReadStreamCopyError() returned: The operation couldn’t be completed. (OSStatus error -9807.)
24/08/2013 14:27:48.836 SubmitDiagInfo[3806]: Failed to submit crash report: file://localhost/Users/andrewmay/Library/Logs/DiagnosticReports/soffice.bin_2013-08-24-094608_Andrew-May-New-Office.crash
24/08/2013 14:27:48.892 SubmitDiagInfo[3806]: Diagnostic message history store was not writable. Will not submit diagnostic messages.
24/08/2013 14:32:48.236 com.apple.launchd.peruser.502[229]: (com.apple.pbs[3842]) Exited: Killed: 9
24/08/2013 14:33:05.778 SubmitDiagInfo[3896]: Launched to submit Diagnostics and Usage
24/08/2013 14:33:07.922 SubmitDiagInfo[3896]: Failed to load serverside whitelist, using cached list: Error Domain=NSURLErrorDomain Code=-1202 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “radarsubmissions.apple.com” which could put your confidential information at risk." UserInfo=0x7fdd6345ada0 {NSURLErrorFailingURLPeerTrustErrorKey=<SecTrust>, NSLocalizedRecoverySuggestion=Would you like to connect to the server anyway?, NSUnderlyingError=0x7fdd64819d10 "The certificate for this server is invalid. You might be connecting to a server that is pretending to be “radarsubmissions.apple.com” which could put your confidential information at risk.", NSErrorPeerCertificateChainKey=(
    "<SecCertificate>",
    "<SecCertificate>",
    "<SecCertificate>"
), NSLocalizedDescription=The certificate for this server is invalid. You might be connecting to a server that is pretending to be “radarsubmissions.apple.com” which could put your confidential information at risk., NSErrorFailingURLKey=https://radarsubmissions.apple.com/macSubmissions/diagnosticwhitelist.jsp?osv=10.8.4, NSErrorFailingURLStringKey=https://radarsubmissions.apple.com/macSubmissions/diagnosticwhitelist.jsp?osv=10.8.4, NSErrorClientCertificateStateKey=0}
24/08/2013 14:33:08.774 SubmitDiagInfo[3896]: CFReadStreamCopyError() returned: The operation couldn’t be completed. (OSStatus error -9807.)
24/08/2013 14:33:08.774 SubmitDiagInfo[3896]: Failed to submit crash report: file://localhost/Users/andrewmay/Library/Logs/DiagnosticReports/soffice.bin_2013-08-24-094059_Andrew-May-New-Office.crash
24/08/2013 14:33:09.179 SubmitDiagInfo[3896]: CFReadStreamCopyError() returned: The operation couldn’t be completed. (OSStatus error -9807.)
24/08/2013 14:33:09.179 SubmitDiagInfo[3896]: Failed to submit crash report: file://localhost/Users/andrewmay/Library/Logs/DiagnosticReports/soffice.bin_2013-08-24-094608_Andrew-May-New-Office.crash
24/08/2013 14:33:09.200 SubmitDiagInfo[3896]: Diagnostic message history store was not writable. Will not submit diagnostic messages.
24/08/2013 14:33:42.458 com.apple.launchd.peruser.502[229]: ([0x0-0x10f10f].org.neooffice.NeoOfficeSecureEdition[3903]) Job appears to have crashed: Abort trap: 6

I don't know what is producing the first few lines, I see them quite regularly in the Console, so I'm not sure if there is some underlying problem with my machine.

The next lines seem to be the Apple error reporting tool struggling to send reports to Apple. I though at first these signified a crash happening, but I have subsequently seen them written to the Console when no crash took place, it just seems to be trying over and over to submit crash logs to Apple.

The last line is the only one that appears specifically at the time of a crash.

Andy
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sat Aug 24, 2013 7:06 am    Post subject:

amayze wrote:
I don't know what is producing the first few lines, I see them quite regularly in the Console, so I'm not sure if there is some underlying problem with my machine.


Just to be safe, you may want to do the following 2 standard Mac disk maintenance steps:

1. Fix file errors - Reboot while pressing and hold Command-S keys. This will boot your machine into single user mode. When you see a Terminal-like prompt, run the following commands. It will take a few minutes to run but it will fix any fixable disk errors:

Code:
fsck -fy ; reboot


2. Fix permissions errors - After you machine reboots, open the /Applications/Utilities/Disk Utility application, select your machine's main volume, and select the "First Aid" tab. In that tab, press the Repair Disk Permissions button.

amayze wrote:
The next lines seem to be the Apple error reporting tool struggling to send reports to Apple. I though at first these signified a crash happening, but I have subsequently seen them written to the Console when no crash took place, it just seems to be trying over and over to submit crash logs to Apple.


I suspect that Mac OS X is trying to submit the NeoOffice 2013 crash logs but since the digital signing that we used to sign the patch does not match the Mac App Store digital signature, Apple's crash logs processing server is rejecting the crash log submissions.

Can you try the following steps?:

1. Run the following command in a Terminal window:

Code:
sudo pkgutil --forget org.neooffice.NeoOfficeSecureEdition


2. Reinstall the following test patch:

NeoOffice 2013:
http://juliette.neooffice.org/test/NeoOffice-2013-Test-3-Intel.dmg

Does NeoOffice 2013 still crash after the above steps?

Patrick
Back to top
amayze
The Merovingian


Joined: Oct 24, 2005
Posts: 561
Location: Edinburgh, Scotland

PostPosted: Sat Aug 24, 2013 8:21 am    Post subject:

I ran the diagnostics you suggested and didn't see anything untoward, but I did happen to launch NeoOffice 2013 while I was logged in as an admin user, and it worked perfectly.

So I did the following:
1. Log in to my NeoOffice test account (which is non-admin)
2. Launch NeoOffice 2013 and observe no Writer window despite setting of Open on Lauunch menu.
3. Change Open on Launch setting to Calc
4. Quit and re-launch NeoOffice 2013
5. Observe a crash.
6. Change my NeoOffice test account to have admin privileges
7. Reboot and log back in to NeoOffice test account
8. Delete ~/Library/Containers/org.neooffice.NeoOfficeSecureEdition
9. Launch NeoOffice 2013 and observe a Writer window opening
10. Change Open on Launch setting to Calc
11. Quit and re-launch NeoOffice 2013
12. Observe a Calc window opening

So it seems there is some permission issue the only shows up for a non-admin user, which is what my main user account on my mac is.

Hope that helps.

Andy
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sat Aug 24, 2013 8:57 am    Post subject:

amayze wrote:
So it seems there is some permission issue the only shows up for a non-admin user, which is what my main user account on my mac is.


I can now reproduce the crash so it is now clear that the test patch installer corrupts the NeoOffice 2013 installation's permissions but not its files.

I will see if I can figure out what specific permissions are getting corrupted as I really like having test patches available for NeoOffice 2013 testers.

I will post again when I have some news to report.

Note: I split this problem into its own separate topic to make it easier to find for other NeoOffice 2013 testers.

Patrick
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sun Aug 25, 2013 8:45 am    Post subject:

I think that I have fixed this patch installation bug. I found a few files that the NeoOffice 2013 patch installer was removing read permissions for non-admin users. I fixed this bug by adding back some "chmod" Terminal commands that I had removed when I copied the NeoOffice 2013 patch installer scripts from the NeoOffice 3.3 patch installer.

If you install the following test patch on top of your existing, corrupted NeoOffice 2013 installation, does the crashing stop for you?:

NeoOffice 2013:
http://juliette.neooffice.org/test/NeoOffice-2013-Test-4-Intel.dmg

Patrick
Back to top
amayze
The Merovingian


Joined: Oct 24, 2005
Posts: 561
Location: Edinburgh, Scotland

PostPosted: Tue Aug 27, 2013 1:50 am    Post subject:

I've installed NeoOffice 2013 Test 4 over my broken install of NeoOffice 2013.

It now launches correctly and respects the setting of Open at Launch.

Thanks.

Andy
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Testing All times are GMT - 7 Hours
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.