Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component: 1:libreoffice-core-6.2.5.2-1.fc30 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --writer file:///run/media/yk/5D1A-F2CF/Fedora-opas.odt --splash-pipe=6 crash_function: (anonymous namespace)::signalHandlerFunction executable: /usr/lib64/libreoffice/program/soffice.bin journald_cursor: s=964a923ddb1a4bc280fb961c4ca69c4c;i=39df;b=dd6a21846629428abea483f6b69ec7b9;m=2788ba9a6;t=58e81e65af3ce;x=d311391380adfa22 kernel: 5.1.18-300.fc30.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1593487 [details] File: backtrace
Created attachment 1593488 [details] File: cgroup
Created attachment 1593489 [details] File: core_backtrace
Created attachment 1593490 [details] File: cpuinfo
Created attachment 1593491 [details] File: dso_list
Created attachment 1593492 [details] File: environ
Created attachment 1593493 [details] File: limits
Created attachment 1593494 [details] File: maps
Created attachment 1593495 [details] File: mountinfo
Created attachment 1593496 [details] File: open_fds
Created attachment 1593497 [details] File: proc_pid_status
caolanm->ricky.tigg: if you load Fedora-opas.odt and try to save it again does it always crash, or is it a one-time thing ? caolanm->sberg: given the gio stuff in some of the threads I wonder if this could be a F29 version or https://bugs.documentfoundation.org/show_bug.cgi?id=124962 ?
Hi. It happened about nine times. There had been two previous attempts to send ABRT reports related to this event; they failed due to useless debug stacks. It is indeed related to the save function or otherwise while document had been opened long enough.
(In reply to Caolan McNamara from comment #12) > caolanm->sberg: given the gio stuff in some of the threads I wonder if this > could be a F29 version or > https://bugs.documentfoundation.org/show_bug.cgi?id=124962 ? Doesn't look to me like its related.
as a longshot are you able to attach that Fedora-opas.odt here and we can see if it crashes for us too.
Created attachment 1593633 [details] involved document
No crash in casual testing and save locally when trying with the same version, so not trivially reproducible which is a pity
Similar problem has been detected: Working with document. reporter: libreport-2.10.1 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --writer file:///run/media/yk/5D1A-F2CF/Ty%C3%B6/Fedora-opas.odt --splash-pipe=6 crash_function: (anonymous namespace)::signalHandlerFunction executable: /usr/lib64/libreoffice/program/soffice.bin journald_cursor: s=787f173f3a294588a239cff2be4da87d;i=1bcf;b=708d98c85422430896b4b17e0e2c66f2;m=9c57931d;t=590c89a2c4ab4;x=a1b24547649382e7 kernel: 5.2.9-200.fc30.x86_64 package: 1:libreoffice-core-6.2.6.2-1.fc30 reason: soffice.bin killed by SIGABRT rootdir: / runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.