You are not logged in.
Hi everybody,
Last week I update my Arch system. After that, Libreoffice stopped working. When I click on it, nothing happens. Uninstalled it, then reinstalled. Nothing. I'm using Libreoffice-fresh, but tried LO-still too with no results. Tried a new profile and... nothing. In terminal, when I run LibreOffice, there's no message of any kind (and nothing happens).
Do you have any idea of what's going on? Any tips?
Thanks for helping,
D.
Last edited by dicaiopolis (2016-11-13 23:31:45)
Offline
gnome? on wayland? (the default)
from the terminal emulator, try to run "lowriter" - "LibreOffice" (CamelCased) should not exist (and actually give a respective error message "command not found" or similar)
Offline
gnome? on wayland? (the default)
from the terminal emulator, try to run "lowriter" - "LibreOffice" (CamelCased) should not exist (and actually give a respective error message "command not found" or similar)
Thanks for your answer. I'm on KDE (Plasma 5). Running "lowriter" gives no results. Nothing happens, no error message, no message at all. Just like running "libreoffice".
Thanks,
D.
Offline
entering that in konsole prints nothing at all???
does it exit immediately?
what, if you
export SAL_USE_VCLPLUGIN=gen
lowriter
Offline
entering that in konsole prints nothing at all???
does it exit immediately?what, if you
export SAL_USE_VCLPLUGIN=gen lowriter
It prints nothing and nothing happens, I mean, you get the terminal occupied (as if it were trying to run libreoffice), but no message at all and nothing happens...
Running:
export SAL_USE_VCLPLUGIN=gen
lowriter
gets the same result...
Thanks,
D.
Offline
move away ~/.config/libreoffice and try again. if that doesn't get you anywhere you best edit the script to strace the binary to see where it stalls.
Offline
move away ~/.config/libreoffice and try again. if that doesn't get you anywhere you best edit the script to strace the binary to see where it stalls.
I've already moved ~/.config/libreoffice: no results.
Could you give some details about "edit the script to trace the binary to see where it stalls"?
Thanks,
D.
Offline
I was thinking if, during the update, some files were installed with 0 size. Maybe that's the issue. How could I trace 0 bite files in my system to try to reinstall the packages?
Offline
I could fix it finding some packages using
pacman -Qkk 2>&1 | grep "^.*: no mtree file$"
and then reinstalling every single package that was listed.
Thanks once more,
D.
Offline