Bug 1637949

Summary: [fix available] LibreOffice application crash while using any input method when Xsession is Wayland
Product: Red Hat Enterprise Linux 7 Reporter: Pooja Yadav <poyadav>
Component: libreofficeAssignee: Caolan McNamara <caolanm>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.6   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-12 09:04:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot for libreoffice crash. none

Description Pooja Yadav 2018-10-10 11:41:42 UTC
Created attachment 1492527 [details]
Screenshot for libreoffice crash.

Description of problem: LibreOffice application crashes when we try to input using any input method like Hangul, Kan-kanji when Xsession is Wayland.
[test@localhost ~]$ cat /var/lib/AccountsService/users/test 
[User]
Language=
XSession=gnome-wayland
Icon=/home/test/.face
SystemAccount=false

Version-Release number of selected component (if applicable):
libreoffice-core-5.3.6.1-19.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install Rhel in any locale like ko_KR
2. Install gnome-session-wayland-session and reboot.
3. While logging in, select Wayland.
3. Launch LibreOffice application eg.-ooimpress
4. Change the input method to hangul or any input method, and try to input.

Actual results:
LibreOffice crashes.

[test@localhost ~]$ ooimpress


Fatal exception: Signal 11
Stack:
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3ae30)[0x7f9129702e30]
/usr/lib64/libreoffice/program/libuno_sal.so.3(+0x3afa1)[0x7f9129702fa1]
/lib64/libc.so.6(+0x36280)[0x7f9129074280]
/lib64/libglib-2.0.so.0(g_utf8_pointer_to_offset+0x40)[0x7f9127894950]
/usr/lib64/libreoffice/program/libvclplug_gtk3lo.so(+0x7cf0d)[0x7f910aa11f0d]
/lib64/libgobject-2.0.so.0(+0xfbb7)[0x7f9127b3ebb7]
/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0x477)[0x7f9127b58657]
/lib64/libgobject-2.0.so.0(g_signal_emit_by_name+0x528)[0x7f9127b59828]
/lib64/libgobject-2.0.so.0(+0xfbb7)[0x7f9127b3ebb7]
/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0x477)[0x7f9127b58657]
/lib64/libgobject-2.0.so.0(g_signal_emit_by_name+0x528)[0x7f9127b59828]
/lib64/libgtk-3.so.0(+0x3cb193)[0x7f910a458193]
/lib64/libffi.so.6(ffi_call_unix64+0x4c)[0x7f91209e3dcc]
/lib64/libffi.so.6(ffi_call+0x1f5)[0x7f91209e36f5]
/lib64/libwayland-client.so.0(+0x8944)[0x7f9108486944]
/lib64/libwayland-client.so.0(+0x5a4c)[0x7f9108483a4c]
/lib64/libwayland-client.so.0(wl_display_dispatch_queue_pending+0x7c)[0x7f9108484ecc]
/lib64/libgdk-3.so.0(+0x8bdc8)[0x7f9109e2edc8]
/lib64/libgdk-3.so.0(gdk_display_get_event+0x79)[0x7f9109dd62d9]
/lib64/libgdk-3.so.0(+0x8baf2)[0x7f9109e2eaf2]
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x159)[0x7f9127865049]
/lib64/libglib-2.0.so.0(+0x4c3a8)[0x7f91278653a8]
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f912786545c]
/usr/lib64/libreoffice/program/libvclplug_gtk3lo.so(+0x46aab)[0x7f910a9dbaab]
/usr/lib64/libreoffice/program/libvcllo.so(_ZN11Application5YieldEv+0x51)[0x7f912193edb1]
/usr/lib64/libreoffice/program/libvcllo.so(_ZN11Application7ExecuteEv+0x45)[0x7f9121940c35]
/usr/lib64/libreoffice/program/libsofficeapp.so(+0x2ad39)[0x7f9129435d39]
/usr/lib64/libreoffice/program/libvcllo.so(+0x52d116)[0x7f9121945116]
/usr/lib64/libreoffice/program/libvcllo.so(_Z6SVMainv+0x22)[0x7f9121945202]
/usr/lib64/libreoffice/program/libsofficeapp.so(soffice_main+0x8a)[0x7f9129460dea]
/usr/lib64/libreoffice/program/soffice.bin[0x40064b]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f91290603d5]
/usr/lib64/libreoffice/program/soffice.bin[0x40067f]


Expected results:
Libreoffice should not crash and user should be able to input.

Additional info:

Comment 2 Caolan McNamara 2018-10-10 12:01:11 UTC
I imagine this is the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1569331 was

Comment 3 Pooja Yadav 2018-10-10 12:04:02 UTC
(In reply to Caolan McNamara from comment #2)
> I imagine this is the same problem as
> https://bugzilla.redhat.com/show_bug.cgi?id=1569331 was

Yeah, its the same problem.

Comment 4 Caolan McNamara 2020-02-12 09:04:34 UTC
because we're approaching the RHEL-7 Extended Life Cycle Support phase I'm not going to fix this at this point. This is fixed in RHEL-8 via bug 1648281.

Comment 5 RHEL Program Management 2020-02-12 09:04:42 UTC
Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain  the issue receives the proper prioritization with product and development management.

https://www.redhat.com/support/process/production/#howto