Description of problem: Opened a spreadsheet in LibreCalc. Version-Release number of selected component: libreoffice-core-5.2.7.2-3.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/lib64/libreoffice/program/soffice.bin --calc '2017 Investments.ods' --splash-pipe=5 crash_function: (anonymous namespace)::signalHandlerFunction executable: /usr/lib64/libreoffice/program/soffice.bin global_pid: 3233 kernel: 4.11.6-201.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 (anonymous namespace)::signalHandlerFunction at /usr/src/debug/libreoffice-5.2.7.2/sal/osl/unx/signal.cxx:434 #4 EditView::ShowCursor at /usr/src/debug/libreoffice-5.2.7.2/editeng/source/editeng/editview.cxx:397 #5 ScInputHandler::RemoveRangeFinder at /usr/src/debug/libreoffice-5.2.7.2/sc/source/ui/app/inputhdl.cxx:2007 #6 ScInputHandler::DataChanged at /usr/src/debug/libreoffice-5.2.7.2/sc/source/ui/app/inputhdl.cxx:2285 #7 ScInputHandler::InputChanged at /usr/src/debug/libreoffice-5.2.7.2/sc/source/ui/app/inputhdl.cxx:3832 #8 ScTextWnd::Command at /usr/src/debug/libreoffice-5.2.7.2/sc/source/ui/app/inputwin.cxx:1532 #9 ImplCallCommand(const VclPtr<vcl::Window> &, enum class CommandEventId, void *, bool, Point *) at /usr/src/debug/libreoffice-5.2.7.2/vcl/source/window/winproc.cxx:225 #10 HandleLongPressEvent::CallCommand at /usr/src/debug/libreoffice-5.2.7.2/vcl/source/window/winproc.cxx:1562 #11 HandleGestureEventBase::Dispatch at /usr/src/debug/libreoffice-5.2.7.2/vcl/source/window/winproc.cxx:1410 #12 HandleGestureEvent::HandleEvent at /usr/src/debug/libreoffice-5.2.7.2/vcl/source/window/winproc.cxx:1518
Created attachment 1291773 [details] File: backtrace
Created attachment 1291774 [details] File: cgroup
Created attachment 1291775 [details] File: core_backtrace
Created attachment 1291776 [details] File: dso_list
Created attachment 1291777 [details] File: environ
Created attachment 1291778 [details] File: limits
Created attachment 1291779 [details] File: maps
Created attachment 1291780 [details] File: mountinfo
Created attachment 1291781 [details] File: namespaces
Created attachment 1291782 [details] File: open_fds
Created attachment 1291783 [details] File: proc_pid_status
Created attachment 1291784 [details] File: var_log_messages
Does this crash for you on every document, or just some specific one ? and is it reproducible. caolanm->erack: the backtrace suggests that pActiveView in ScInputHandler::RemoveRangeFinder is null ?
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.