Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#55638 - [libreoffice-fresh] loops to recover file which just trying to open.
Attached to Project:
Arch Linux
Opened by denixx baykin (denixx) - Friday, 15 September 2017, 12:29 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 19 September 2017, 13:15 GMT
Opened by denixx baykin (denixx) - Friday, 15 September 2017, 12:29 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 19 September 2017, 13:15 GMT
|
DetailsDescription:
libreoffice-fresh crashes, and tries to recover file I tried to open. Loops. $ libreoffice process 12608: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. D-Bus not built with -rdynamic so unable to print a backtrace Application Error Additional info: * package version(s) $ libreoffice --version LibreOffice 5.4.1.2.0 40m0(Build:2) * config and/or log files etc. Look above, please. Let me know if there is additional info can be gathered somewhere. Steps to reproduce: I've tried to open some file, and it's restarting and asks me if I'm willing to recover file I've just tried to open. |
This task depends upon
If I launch
$ libreoffice
in console, it may not fail, and allows discard recovery process.
After that I can open the same file with Open file dialog.
Apache VCL? Or something different?
export SAL_USE_VCLPLUGIN=kde4
in /etc/profile.d/libreoffice-fresh.sh file
and rebooted after upgrade.
Now all is fine, as I can see.
Workaround is ok, issue can be closed.
May I reopen it if there still will be (related) problems?