Version 4.0.3.3 Os x 10.8.3 I upgraded from a previous version and ran the program successful as the administrator. However, any general user account I got the following message: LibreOffice 4.0 - Fatal Error. The application cannot be started. Error while reinstalling all previously deployed packages of context user. I also tried changing the accounts to administrator, but still had the same problem. Is there anyway to log what the program accessing that prevent the program from running? I would be happy to blow away the user account previously deployed packages, if I knew where they are located. The only thing that might be nice to keep would be the recent files. I was able to create a new account and libre office ran without errors.
Created attachment 79318 [details] Log of error
You can rename your LO directory profile by following this link: https://wiki.documentfoundation.org/UserProfile Could you test again afterwards and tell us if it's ok?
Julien, I had success with libreoffice starting normally for all account. Thank you for your support. I am not sure of what LO directory is. I just renamed 4 and 3. I renamed two files in the normal user account. I had both 3 and 4. I renamed old3 and old4 and got the new result 4 after a successful load. /Users/<user name>/Library/Application Support/libreoffice/4 (LibreOffice 4) /Users/<user name>/Library/Application Support/libreoffice/3 (LibreOffice 3) Thank you for your support! On May 17, 2013, at 6:22 PM, bugzilla-daemon@freedesktop.org wrote: > Julien Nabet changed bug 64606 > What Removed Added > Status UNCONFIRMED NEEDINFO > CC serval2412@yahoo.fr > Ever confirmed 1 > > Comment # 2 on bug 64606 from Julien Nabet > You can rename your LO directory profile by following this link: > https://wiki.documentfoundation.org/UserProfile > Could you test again afterwards and tell us if it's ok? > > You are receiving this mail because: > You reported the bug.
Julien, If you need any extra information, I will be glad to send it. Thanks again for your timely support! On May 18, 2013, at 6:29 AM, James Beckert <james_beckert@hotmail.com> wrote: > Julien, > > I had success with libreoffice starting normally for all accounts. Thank you for your support. I am not sure of what LO directory is. > > I renamed two files in the normal user accounts. I had both 3 and 4. I renamed old3 and old4 and got the new result 4 after a successful load. > > /Users/<user name>/Library/Application Support/libreoffice/4 (LibreOffice 4) > /Users/<user name>/Library/Application Support/libreoffice/3 (LibreOffice 3) > > Thank you for your support! > > <PastedGraphic-2.png> > On May 17, 2013, at 6:22 PM, bugzilla-daemon@freedesktop.org wrote: > >> Julien Nabet changed bug 64606 >> What Removed Added >> Status UNCONFIRMED NEEDINFO >> CC serval2412@yahoo.fr >> Ever confirmed 1 >> >> Comment # 2 on bug 64606 from Julien Nabet >> You can rename your LO directory profile by following this link: >> https://wiki.documentfoundation.org/UserProfile >> Could you test again afterwards and tell us if it's ok? >> >> You are receiving this mail because: >> You reported the bug. >
James: great for you! :-) It could be useful you zip the whole directories "old4" and "old3" in 1 zip file and attach the zip file to the bugtracker by using this link: https://bugs.freedesktop.org/attachment.cgi?bugid=64606&action=enter (this link allows to comment your attachment in the same time)
Created attachment 79501 [details] Libreoffice /Users/<user name>/Library/Application Support/libreoffice/4 and 3 Please let me know of what caused the problem. Thank you again for your support.
Julien, Thank you again. Please keep informed about the failure. Have a GRAND Weekend James E. On May 18, 2013, at 7:00 AM, bugzilla-daemon@freedesktop.org wrote: > > Comment # 5 on bug 64606 from Julien Nabet > James: great for you! :-) > > It could be useful you zip the whole directories "old4" and "old3" in 1 zip > file and attach the zip file to the bugtracker by using this link: > https://bugs.freedesktop.org/attachment.cgi?bugid=64606&action=enter > > (this link allows to comment your attachment in the same time) > > You are receiving this mail because: > You reported the bug.
I retrieved the old4 profile but didn't reproduce any problem. Perhaps it's because I use master sources (future 4.1) + I'm on Linux Debian not on Mac I'll give a try on Mac.
I gave a try on MacOs 10.7.5 with old4, I didn't reproduce the problem. Did you install any specific font recently? Thorsten: I know very few about MacOs, for example I don't know if error log may help. Any idea?
Julien, I bought the mac early this year. My daughter had several fonts that she created, but these font were installed when I setup the computer. I haven't added any recently. But here is one of her fonts. That she created. Sorry about the delay. Have a GRAND Weekend! James E. On May 18, 2013, at 5:14 PM, bugzilla-daemon@freedesktop.org wrote: > Julien Nabet changed bug 64606 > What Removed Added > CC tbehrens@suse.com > > Comment # 9 on bug 64606 from Julien Nabet > I gave a try on MacOs 10.7.5 with old4, I didn't reproduce the problem. > Did you install any specific font recently? > > Thorsten: I know very few about MacOs, for example I don't know if error log > may help. Any idea? > > You are receiving this mail because: > You are the assignee for the bug. > You reported the bug.
I'll give a try later about the font but I have been considering this again and think now that if the pb was the font, you would still have it (even after a brand new LO directory profile). Last thing: what's your Java version? (perhaps you've got several one installed?) 1.6, 1.7? 32 or 64 bits Roman: would you have some time to give it a try?
This screen is from safari internet browser. On May 19, 2013, at 6:54 AM, bugzilla-daemon@freedesktop.org wrote: > Julien Nabet changed bug 64606 > What Removed Added > CC bugs@eikota.de > > Comment # 11 on bug 64606 from Julien Nabet > I'll give a try later about the font but I have been considering this again and > think now that if the pb was the font, you would still have it (even after a > brand new LO directory profile). > > Last thing: what's your Java version? (perhaps you've got several one > installed?) > 1.6, 1.7? 32 or 64 bits > > Roman: would you have some time to give it a try? > > You are receiving this mail because: > You are the assignee for the bug. > You reported the bug.
which screenshot? You can use this link to attach your screenshot: https://bugs.freedesktop.org/attachment.cgi?bugid=64606&action=enter (you can also let a comment in the same time if necessary with this link)
Created attachment 79525 [details] Safari Screenshot
Created attachment 79526 [details] Java 7 Update 17
Created attachment 79527 [details] This screen is from safari internet browser.
Created attachment 79528 [details] Here some system Information with application Name and version
James: thank you a lot for all the feedback provided. I put back the status to unconfirmed since you're the only one who had the problem for the moment. Let's wait for the feedback of Roman and Thorsten now. Of course, if you have more info/remark/etc. to provide, don't hesitate ! :-)
James, how is life? Did you update to 10.8.5 or even 10.9? Have you tried LO 4.1.3.2? Does that improve the situation? LO running fine here with the above versions 10.9 and latest Java. Setting to NEEDINFO until more detail is provided. After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :)
I am running OSx 10.8.5 and LO Version: 4.1.2.3, I have no problems since May 18, 2013, at 6:29 AM. I have been upgrading without problems. I have java listed in safari as application/x-java-applet Basic Java Applets javaapplet application/x-java-applet;deploy=10.17.2 Java applet application/x-java-applet;javafx=2.2.7 Java applet application/x-java-applet;jpi-version=1.7.0_17 Java applet Thanks again for all of the help and the quick response.
So, summing up the situation, it looks like James had a problem with user profiles not being taken up correctly upon migration from LO3 to LO4. This was a known problem for a while (especially when switching from 3.6 to 4.0), having experienced it myself. However, from what James states, his problems no longer exist so am closing this bug as worksforme.