Description of problem: Document was closed. Version-Release number of selected component: 1:libreoffice-core-6.3.2.2-1.fc31 Additional info: reporter: libreport-2.10.1 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user/dbus\x2d:1.2\x2dorg.gnome.Nautilus.slice/dbus-:1.2-org.gnome.Nautilus 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=7a3a51bd43f4497b8152e5686ec09204;i=2c244;b=9d00d111dfdd40d38ebf17a27e12736a;m=64a6d010a;t=594543d77d698;x=3d24f84416920792 kernel: 5.3.2-300.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1623228 [details] File: backtrace
Created attachment 1623229 [details] File: core_backtrace
Created attachment 1623230 [details] File: cpuinfo
Created attachment 1623231 [details] File: dso_list
Created attachment 1623232 [details] File: environ
Created attachment 1623233 [details] File: limits
Created attachment 1623234 [details] File: maps
Created attachment 1623235 [details] File: mountinfo
Created attachment 1623236 [details] File: open_fds
Created attachment 1623237 [details] File: proc_pid_status
Is this reproducible, perhaps on exporting a certain document ?
I had consistently got ABRT related errors using a unique and specific odt-document, which Had been sent once on request. With new document it won't happen. I am not able to figure out an 'export' feature on my application.
"which Had been sent once on request" Was that to me ? I can find no emails from your email address sent to me.
Hey. it had been sent against Comment 15 to Bug 1733328 as involved document.
ah, played around with it again, but can't reproduce it with casual editing opening a few sidebar panels, closing and/or saving the document. Hard to identify what is triggering this.
was this problem the same underlying problem of bug 1766990, i.e. missing starmath, or does it still persist with that installed ?
At least present and bug 1766990 issues titles –by system produced– are identical.
*** This bug has been marked as a duplicate of bug 1766990 ***