[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#905874: libreoffice: No input of accented characters through dead-key composition



On 08/12/2018 02:54 AM, Rene Engelhard wrote:
On Sat, Aug 11, 2018 at 05:20:54PM -0400, Mario L. Epp K. wrote:
On 08/11/2018 09:58 AM, Rene Engelhard wrote:
retitle 905874: libreoffice: No input of accented characters through dead-key composition in gen and kde4 plugins
thanks

On Sat, Aug 11, 2018 at 01:22:51PM +0200, Rene Engelhard wrote:
On Fri, Aug 10, 2018 at 10:18:30PM -0400, Mario L. Epp wrote:
On researching the issue prior to making this report, I found this issue
reported on the DocumentFoundation Bugzilla as "Bug 112770" at
<https://bugs.documentfoundation.org/show_bug.cgi?id=112770>. But I am not
shure how to implement the solution from 6.0.0 to 5.2.7.2 for KDE5 on Debian 9.

Maybe install the 6.1.0 backport from stretch-backports? That one also
has a KDE5 integration other than that KDE4 thingy "working" with KDE5.

This will never be fixed in stable properly (until buster releases of
course with above new KDE5 integration)

I uninstalled the "stable" LibreOffice before installing the "backported"
LibreOffice with the Metapackage. After the instalation I rebooted the
computer.

The metapackage doesn't install the KDE integration.

But the same bug appears also in LibreOffice 6.1.0.2 (Build ID:
1:6.1.0~rc2-3~bpo9+1), Linux 4.9; UI render: defualt; VCL: x11.
                                                         ^^^^^^^^
And with the KDE integration actually installed? That would just leave
the non-integrated LO affected only.

Thank you, I did not catch that omission. After installing the KDE-integration, the dead keys work as advertised. And in the Help->About dialog it now reads: "VCL: gtk3_kde5"

I also did a clean install of Debian 9 (new partition tables). The basic KDE system for a clean/new installation worked without a problem. The Help->About dialog of LibreOffice reads: version 5.2.7.2 (Build ID: 1:5.2.7-1+deb9u4); VCL: kde4

The other new install with this bug had the "/home" partition mounted from the previous installation of Debian 8. So, maybe there was some problem with the upgrade.

It seems that I have now been able to resolve this problem to my satisfaction. Thank you.

Mario L. Epp


Reply to: