Bug 2001644 - [abrt] libreoffice-core: wl_proxy_get_user_data(): soffice.bin killed by SIGSEGV
Summary: [abrt] libreoffice-core: wl_proxy_get_user_data(): soffice.bin killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: libreoffice
Version: 34
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:6bcde8a4651d01e09dce79b89d6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-06 16:28 UTC by allison
Modified: 2022-06-07 20:15 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2022-06-07 20:15:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (77.00 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: core_backtrace (23.88 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: cpuinfo (2.29 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: dso_list (567 bytes, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: environ (2.03 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: exploitable (82 bytes, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: limits (1.29 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: maps (3.98 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: mountinfo (2.50 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: open_fds (3.04 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details
File: proc_pid_status (1.39 KB, text/plain)
2021-09-06 16:28 UTC, allison
no flags Details

Description allison 2021-09-06 16:28:14 UTC
Description of problem:
I had two documents open. One from word and one from excel. I think I was doing an initial save on the LibreOffice Impress...
when CRASH! both docs choked!
Not a big issue. I only lost a few minutes of work (in the other doc) that I was going to redo anyway. 
But if this report can help LibreOffice in any small way then I am glad to share.
:)

Version-Release number of selected component:
libreoffice-core-1:7.1.5.2-1.fc34

Additional info:
reporter:       libreport-2.15.2
backtrace_rating: 4
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-glib-libreoffice\x2dwriter-73266.scope
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --writer file:///tmp/mozilla_allison0/Draft-PowerPoint-Demo.docx --splash-pipe=6
crash_function: wl_proxy_get_user_data
executable:     /usr/lib64/libreoffice/program/soffice.bin
journald_cursor: s=c9a7c23b54154ee8956893aa8bd3304e;i=2fbbd;b=a881c515da9a4931b5e81d0595bb2e2c;m=26a806174b;t=5cb54c5e9cca1;x=db317f818363ecdf
kernel:         5.13.8-200.fc34.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 wl_proxy_get_user_data at ../src/wayland-client.c:2047
 #1 wl_surface_get_user_data at /usr/include/wayland-client-protocol.h:3625
 #2 data_device_enter at wayland/gdkdevice-wayland.c:1177
 #3 ffi_call_unix64 at ../src/x86/unix64.S:76
 #4 ffi_call at ../src/x86/ffi64.c:525
 #5 wl_closure_invoke at ../src/connection.c:1018
 #6 dispatch_event at ../src/wayland-client.c:1452
 #7 dispatch_queue at ../src/wayland-client.c:1598
 #8 wl_display_dispatch_queue_pending at ../src/wayland-client.c:1840
 #9 wl_display_dispatch_pending at ../src/wayland-client.c:1903

Comment 1 allison 2021-09-06 16:28:16 UTC
Created attachment 1820918 [details]
File: backtrace

Comment 2 allison 2021-09-06 16:28:18 UTC
Created attachment 1820919 [details]
File: core_backtrace

Comment 3 allison 2021-09-06 16:28:19 UTC
Created attachment 1820920 [details]
File: cpuinfo

Comment 4 allison 2021-09-06 16:28:20 UTC
Created attachment 1820921 [details]
File: dso_list

Comment 5 allison 2021-09-06 16:28:21 UTC
Created attachment 1820922 [details]
File: environ

Comment 6 allison 2021-09-06 16:28:22 UTC
Created attachment 1820923 [details]
File: exploitable

Comment 7 allison 2021-09-06 16:28:23 UTC
Created attachment 1820924 [details]
File: limits

Comment 8 allison 2021-09-06 16:28:24 UTC
Created attachment 1820925 [details]
File: maps

Comment 9 allison 2021-09-06 16:28:26 UTC
Created attachment 1820926 [details]
File: mountinfo

Comment 10 allison 2021-09-06 16:28:27 UTC
Created attachment 1820927 [details]
File: open_fds

Comment 11 allison 2021-09-06 16:28:28 UTC
Created attachment 1820928 [details]
File: proc_pid_status

Comment 12 Ben Cotton 2022-05-12 15:01:41 UTC
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 13 Ben Cotton 2022-06-07 20:15:32 UTC
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.