Launchpad has imported 5 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=48341.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-04-05T15:48:00+00:00 Mathieu GUILLAUME wrote: The first time LibreOffice is started with a custom UserInstallation, it will stop after a few seconds. How to reproduce: Run: /usr/lib/libreoffice/program/soffice.bin -env:UserInstallation=file:///tmp/lotest Result: returns after a few seconds, no soffice process remaining Run the same command again: OK, doesn't exit by itself Remove /tmp/lotest and try again: KO, exits by itself This has been reproduced on Ubuntu 11.10 with LibreOffice 3.4 and Ubuntu 12.04 beta1 with LibreOffice 3.5.1. When I tested on Windows with a 3.4 distribution, this didn't happen, not sure if this is specific to the ubuntu packaging or general to linux. Related tickets: - Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/902344 - Nuxeo: https://jira.nuxeo.com/browse/NXP-8118 Reply at: https://bugs.launchpad.net/df- libreoffice/+bug/902344/comments/6 ------------------------------------------------------------------------ On 2012-04-10T12:31:34+00:00 Mathieu GUILLAUME wrote: Apparently, this is linked to the command line options syntax change, this does not happen with "--env" instead of "-env" Reply at: https://bugs.launchpad.net/df- libreoffice/+bug/902344/comments/7 ------------------------------------------------------------------------ On 2012-04-10T13:04:39+00:00 Sbergman wrote: (In reply to comment #1) > Apparently, this is linked to the command line options syntax change, this > does > not happen with "--env" instead of "-env" No, UNO bootstrap variables (like that "UserInstallation") are still passed via -env, not --env (unless Debian and/or Ubuntu broke that in their specific LO instances, which I doubt). What happens in LO 3.5 if you pass --env:... is that that argument is effectively ignored (so that it will use the default user installation in the above case); LO 3.6 will give an error about an unknown option. Reply at: https://bugs.launchpad.net/df- libreoffice/+bug/902344/comments/8 ------------------------------------------------------------------------ On 2012-04-10T15:58:34+00:00 Mathieu GUILLAUME wrote: The crash happens during the loading of extensions. If I use the LibreOffice-provided .debs and don't install any of the "libobasis3.5-extension-*" packages, the crash doesn't happen. This doesn't seem to be possible with the Ubuntu packaging however. Is there a command-line option to start without loading any extension? I couldn't find one. Reply at: https://bugs.launchpad.net/df- libreoffice/+bug/902344/comments/11 ------------------------------------------------------------------------ On 2012-04-10T20:43:27+00:00 Mathieu GUILLAUME wrote: I managed to skip loading the bundled extensions by creating an empty dir (say /tmp/empty) and adding this to the command line: -env:BUNDLED_EXTENSIONS=file:///tmp/empty This solves my problem, but the bug still exists. Reply at: https://bugs.launchpad.net/df- libreoffice/+bug/902344/comments/12 ** Changed in: df-libreoffice Status: Unknown => New ** Changed in: df-libreoffice Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/902344 Title: [Upstream] Headless soffice failure condition To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/902344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
