LO 7.5.3.2 crashes after displaying the splash screen, saying "Unspecified Application Error" on the console. strace ends in 1617626 22:17:32.326964 openat(AT_FDCWD, "/home/bero/.config/libreoffice/4/user/bsMSIv", O_RDWR|O_CREAT|O_EXCL, 0600) = 19 1617626 22:17:32.327023 newfstatat(19, "", {st_mode=S_IFREG|0600, st_size=0, ...}, AT_EMPTY_PATH) = 0 1617626 22:17:32.327053 fcntl(19, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0 1617626 22:17:32.327498 pread64(19, "", 4096, 0) = 0 1617626 22:17:32.327523 pwrite64(19, "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<oor:items xmlns:oor=\"http://openoffice.org/2001/registry\" xmlns:xs=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\">\n<item oor:path=\"/org.openoffice.Office.Common/Misc\"><prop o"..., 1421, 0) = 1421 1617626 22:17:32.327557 close(19) = 0 1617626 22:17:32.327586 newfstatat(AT_FDCWD, "/home/bero/.config/libreoffice/4/user/registrymodifications.xcu", {st_mode=S_IFREG|0600, st_size=1421, ...}, 0) = 0 1617626 22:17:32.327613 rename("/home/bero/.config/libreoffice/4/user/bsMSIv", "/home/bero/.config/libreoffice/4/user/registrymodifications.xcu") = 0 1617626 22:17:32.327683 chown("/home/bero/.config/libreoffice/4/user/registrymodifications.xcu", -1, 1007) = 0 1617626 22:17:32.327708 rt_sigprocmask(SIG_BLOCK, ~[RT_1], NULL, 8) = 0 1617626 22:17:32.327727 exit(0) = ? 1617626 22:17:32.327754 +++ exited with 0 +++ 1617481 22:17:32.327758 <... futex resumed>) = 0 1617481 22:17:32.327784 newfstatat(AT_FDCWD, "/home/bero/.config/libreoffice/4/.lock", {st_mode=S_IFREG|0664, st_size=125, ...}, AT_SYMLINK_NOFOLLOW) = 0 1617481 22:17:32.327803 unlink("/home/bero/.config/libreoffice/4/.lock") = 0 1617481 22:17:32.327855 write(2, "Unspecified Application Error\n", 30) = 30 after reading all font files. This started after upgrading a number of system libraries (and rebuilding LO, so ABI changes are not the issue), so right now I'm assuming there's an incompatibility between LO and latest versions of libs it tries to use.
Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile ? Also, you indicated you "rebuilt" LO, did you use autogen.sh to force LO to take into account your new libs?
Dear Bernhard Rosenkraenzer, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Bernhard Rosenkraenzer, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp