Bug 1590279 - Several tutorial file crashes
Summary: Several tutorial file crashes
Keywords:
Status: CLOSED DUPLICATE of bug 1565220
Alias: None
Product: Fedora
Classification: Fedora
Component: inkscape
Version: 28
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-12 11:03 UTC by Basil Eric Rabi
Modified: 2018-06-20 19:18 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-20 19:18:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Basil Eric Rabi 2018-06-12 11:03:07 UTC
Description of problem:
The following tutorials crash when opening:
Inkscape: Shapes
Inkscape: Advanced
Elements of Design
Tips and Tricks

Version-Release number of selected component (if applicable):
inkscape-0.92.3-1.fc28  

How reproducible:
Always

Steps to Reproduce (via gui):
1. Click Help > Tutorial >

Actual results:
Inkscape encountered an internal error and will close now

Expected results:
The tutorial opens

Additional info:
The following files crash when opening inkscape via terminal:
/usr/share/inkscape/tutorials/tutorial-advanced.svg
/usr/share/inkscape/tutorials/tutorial-elements.svg
/usr/share/inkscape/tutorials/tutorial-shapes.svg

Message:
/usr/include/c++/8/bits/stl_vector.h:950: std::vector<_Tp, _Alloc>::const_reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) const [with _Tp = Inkscape::Text::Layout::Character; _Alloc = std::allocator<Inkscape::Text::Layout::Character>; std::vector<_Tp, _Alloc>::const_reference = const Inkscape::Text::Layout::Character&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.

Comment 1 Ben Woodard 2018-06-20 19:18:43 UTC

*** This bug has been marked as a duplicate of bug 1565220 ***


Note You need to log in before you can comment on or make changes to this bug.