Bug 56991

Summary: [CRASH] Library not loaded: /usr/local/lib/liblcms2.2.dylib
Product: LibreOffice Reporter: Jorendc <jorendc>
Component: InstallationAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED DUPLICATE    
Severity: blocker CC: bugs, nthiebaud
Priority: medium    
Version: 4.0.0.0.alpha0+ Master   
Hardware: Other   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: crash report

Description Jorendc 2012-11-11 19:30:29 UTC
Created attachment 69909 [details]
crash report

Problem: LibreOffice 3.7.0.0 Alpha doesn't boot. When I click on the program, immediately there is an crash report/error message.

Expected behavior: LibreOffice green load screen pops up and load to the general splash screen where you can select the program (writer, calc, ...).

The following versions give this error and DON'T LOAD properly: 
master~2012-11-11_01.30.55_LibO-Dev_3.7.0.0.alpha0_MacOS_x86_install_en-US.dmg 
master~2012-11-09_23.52.28_LibO-Dev_3.7.0.0.alpha0_MacOS_x86_install_en-US.dmg 

This LO version doesn't load, but has another kind of error... 'No activable file system': master~2012-11-09_00.53.28_LibO-Dev_3.7.0.0.alpha0_MacOS_x86_install_en-US.dmg

The last WORKING version is:
master~2012-11-08_09.37.13_LibO-Dev_3.7.0.0.alpha0_MacOS_x86_install_en-US.dmg
Comment 1 Jorendc 2012-11-12 16:53:27 UTC
@Norbert Thiebaud: You solved the previous problem with the dylib... I assumed you'll be interested in this bug. (If not: I'm sorry to add you :-) )
Comment 2 Roman Eisele 2012-11-13 08:38:17 UTC
Oops -- somehow I must have missed this report, and therefore I have reported the same issue again: as bug 57051. Congratulations to you, Joren, for finding this bug first! ;-)

However, now I must mark one of the two bugs as a duplicate of the other one. Well... Normally, I should mark my (newer) bug as a dup of this (older) report, but IMHO my little report does contain more details, and is already added to the 3.7/4.0 MAB list. So, to avoid the bugzilla traffic of removing my bug from and adding this one instead to the MAB list, and of copying more details from my bug report back to this one, I suggest to do it the other way around this time and to mark this bug report as a duplicate of my one.

@ Joren De Cuyper:
No offence! Is it OK for you if I do mark your report as a dup of my one? I don’t want to rob you of the glory of having reported the bug first; I just want to keep things simple ... ;-)

*** This bug has been marked as a duplicate of bug 57051 ***
Comment 3 Jorendc 2012-11-13 11:48:11 UTC
@Roman Eisele: I completely understand. No hard feelings ;-). I'm hunting bugs, not fame :D. Lets continue on your bugreport.