Bug 1655240

Summary: [abrt] inkscape: std::__replacement_assert(char const*, int, char const*, char const*)(): inkscape killed by SIGABRT
Product: [Fedora] Fedora Reporter: Rob Tomsick <robert>
Component: inkscapeAssignee: Gwyn Ciesla <gwync>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: duffy, gwync, jonathan.underwood, lkundrak, rlerch
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/4c980e531cbeec878a76fdf1dc4035c4cbe554ef
Whiteboard: abrt_hash:ebcb248c6ef6e1f2712e3f407c68c02e0c981bd8;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 20:12:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Rob Tomsick 2018-12-01 19:46:30 UTC 
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:
inkscape-0.92.3-5.fc29

Additional info:
reporter:       libreport-2.9.6
backtrace_rating: 4
cmdline:        /usr/bin/inkscape
crash_function: std::__replacement_assert(char const*, int, char const*, char const*)
executable:     /usr/bin/inkscape
journald_cursor: s=0e0ff21a983f43ae9fcff66ddf3a171b;i=126c6;b=55d4c273886b4e92abf1c2920ba0c42d;m=75f9600e6;t=57bfae7d979e6;x=1f4453ed7e37977
kernel:         4.19.4-300.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
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
Comment 1 Rob Tomsick 2018-12-01 19:46:35 UTC 
Created attachment 1510486 [details]
File: backtrace
Comment 2 Rob Tomsick 2018-12-01 19:46:36 UTC 
Created attachment 1510487 [details]
File: cgroup
Comment 3 Rob Tomsick 2018-12-01 19:46:38 UTC 
Created attachment 1510488 [details]
File: core_backtrace
Comment 4 Rob Tomsick 2018-12-01 19:46:38 UTC 
Created attachment 1510489 [details]
File: cpuinfo
Comment 5 Rob Tomsick 2018-12-01 19:46:40 UTC 
Created attachment 1510490 [details]
File: dso_list
Comment 6 Rob Tomsick 2018-12-01 19:46:41 UTC 
Created attachment 1510491 [details]
File: environ
Comment 7 Rob Tomsick 2018-12-01 19:46:42 UTC 
Created attachment 1510492 [details]
File: limits
Comment 8 Rob Tomsick 2018-12-01 19:46:43 UTC 
Created attachment 1510493 [details]
File: maps
Comment 9 Rob Tomsick 2018-12-01 19:46:44 UTC 
Created attachment 1510494 [details]
File: mountinfo
Comment 10 Rob Tomsick 2018-12-01 19:46:45 UTC 
Created attachment 1510495 [details]
File: open_fds
Comment 11 Rob Tomsick 2018-12-01 19:46:46 UTC 
Created attachment 1510496 [details]
File: proc_pid_status
Comment 12 Ben Cotton 2019-10-31 20:23:00 UTC 
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.
Comment 13 Ben Cotton 2019-11-27 20:12:01 UTC 
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
bug.

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