https://bugs.freedesktop.org/show_bug.cgi?id=78477
Marcello Magnifico <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from Marcello Magnifico <[email protected]> --- (In reply to comment #1) > Is this bug still valid / reproducible with the latest LO release? > Currently 4.2.4: http://www.libreoffice.org/download/libreoffice-fresh/ Yes. That took more than expected, sorry for the delay. Debian 7 apparently does not allow to remove Libreoffice packages coming from their repository without taking down GNOME3 itself. I had no time to test a mixed setup on that same workstation. The tests continued within a lower priority x86_64 machine, a PearOS6.1 (Ubuntu 12.04 derivative) which was born with an old LO3 so seldom used I couldn't tell when the last time was. A freshly downloaded LO4.2.4.2 (thanks for the direct link) was put in place even before thinking to test LO3 itself. The problem turned to be reproduceable with no differences at all. Analysis details follow. The splash screen with the progress bar will just disappear while the progress bar is still incomplete and nothing more will happen. The segfault is silent, so difficult to detect that one could doubt that an error of such magnitude actually took place. If you launch LO from a terminal window, you will get nothing on stdout nor stderr. Check the dmesg command for the latest system events, and it's there. The output from 'strace -f loffice' will report the open system call for the offending font (the one provided or, supposedly, any other one causing the same effect) just a few lines before the segfault. That was the only hint suggesting to remove the last font accessed by the application. > Please also try resetting your user profile and let us know if that helps: > https://wiki.documentfoundation.org/UserProfile That was not needed, as the old and new version of LO on the test system are different by major release. Removing the two offending fonts (which were already on place, as I periodically rsynced some data from a network share) was sufficient. > Should this be still reproducible for you with the latest LO release please > set this bug back to UNCONFIRMED. Now. Thanks for your attention. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
