Description of problem:
I created a text area. Then I clicked away from it. Then to return focus to it and get the cursor back, I double clicked
the area... and Inkscape crashed.
This happens regularly, but not consistently enough to reproduce every time.
(Note: While I do use firejail on this machine, I am NOT using it to sandbox Inkscape.)
Version-Release number of selected component:
crash_function: std::__replacement_assert(char const*, int, char const*, char const*)
runlevel: N 5
Thread no. 1 (10 frames)
#2 std::__replacement_assert(char const*, int, char const*, char const*) at /usr/include/c++/8/x86_64-redhat-linux/bits/c++config.h:2391
#3 std::vector<Inkscape::Text::Layout::Character, std::allocator<Inkscape::Text::Layout::Character> >::operator(unsigned long) const at /usr/include/c++/8/bits/stl_vector.h:805
#4 Inkscape::Text::Layout::iterator::iterator(Inkscape::Text::Layout const*, unsigned int) at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/libnrtype/Layout-TNG.h:1057
#5 Inkscape::Text::Layout::_cursorXOnLineToIterator(unsigned int, double) const at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/libnrtype/Layout-TNG-OutIter.cpp:50
#6 Inkscape::Text::Layout::getNearestCursorPositionTo(double, double) const at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/libnrtype/Layout-TNG-OutIter.cpp:156
#7 Inkscape::Text::Layout::getNearestCursorPositionTo(Geom::Point const&) const at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/2geom/point.h:104
#8 sp_te_get_position_by_coords(SPItem const*, Geom::Point const&) at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/text-editing.cpp:112
#9 Inkscape::UI::Tools::sp_text_context_place_cursor_at(Inkscape::UI::Tools::TextTool*, SPObject*, Geom::Point) at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/ui/tools/text-tool.cpp:1699
#10 Inkscape::UI::Tools::SelectTool::root_handler(_GdkEvent*) at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/ui/tools/select-tool.cpp:492
#11 Inkscape::UI::Tools::sp_event_context_virtual_root_handler(Inkscape::UI::Tools::ToolBase*, _GdkEvent*) at /usr/src/debug/inkscape-0.92.3-5.fc29.x86_64/src/ui/tools/tool-base.cpp:1003
Potential duplicate: bug 1578924
Created attachment 1510486 [details]
Created attachment 1510487 [details]
Created attachment 1510488 [details]
Created attachment 1510489 [details]
Created attachment 1510490 [details]
Created attachment 1510491 [details]
Created attachment 1510492 [details]
Created attachment 1510493 [details]
Created attachment 1510494 [details]
Created attachment 1510495 [details]
Created attachment 1510496 [details]
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.
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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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
Thank you for reporting this bug and we are sorry it could not be fixed.