https://bugs.documentfoundation.org/show_bug.cgi?id=151913

            Bug ID: 151913
           Summary: Libreoffice won't start if home directory is mounted
                    on mergerFS
           Product: LibreOffice
           Version: 5.4.7.2 release
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: LibreOffice
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: strona+documentfoundat...@czarniak.org

Created attachment 183423
  --> https://bugs.documentfoundation.org/attachment.cgi?id=183423&action=edit
LO strace

I'm unable to start any LO components if /home directory (most likely some
relevant to LO parts of it) is located on mergerFS.

yaro@yaro-desktop2:~$ mergerfs.ctl info
- mount: /home
  version: 2.33.5
  pid: 630
  srcmounts:
    - /mnt/md0
    - /mnt/md1
yaro@yaro-desktop2:~$ 

yaro@yaro-desktop2:~$ findmnt /home
TARGET SOURCE   FSTYPE        OPTIONS
/home  mergerfs fuse.mergerfs
rw,relatime,user_id=0,group_id=0,default_permissions,allow_other
yaro@yaro-desktop2:~$ 

------------

LO execution example (no output, nor error at all):
yaro@yaro-desktop2:~$ C_ALL=C libreoffice --version
yaro@yaro-desktop2:~$ 

And now if I "redirect" $HOME to the drive where .config (and most of the other
/home content) is located:
yaro@yaro-desktop2:~$ LC_ALL=C HOME="/mnt/md1/yaro" libreoffice --version
LibreOffice 6.4.7.2 40(Build:2)

yaro@yaro-desktop2:~$ 

It works fine. Writer, calc etc can be started without any problems. For some
reasons, LO doesn't like mergerFS and just exit without any message or error. 

I also checked strace but it did not provide me any extra information. But I'm
not good at it. :) Output provided in attachment.

I observe the same behavior on ubuntu 22.04, neon 20.04 and some relatively new
fedora. So it's not distro related.


I also reported bug on mergerFS github at:
https://github.com/trapexit/mergerfs/issues/1086

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to