Segmentation fault converting SVG to PDF
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Inkscape |
Invalid
|
Undecided
|
Unassigned | ||
inkscape (Fedora) |
Won't Fix
|
Undecided
|
Bug Description
Using a custom docker container, with very little special (https:/
Version in container: Inkscape 0.92.2 5c3e80d, 2017-08-06 (Latest available in Alpine Edge repos)
The same files build fine under my native arch install (Inkscape 0.92.2 2405546, 2018-03-11).
Build log available at https:/
Tried searching for some verbose flags to debug it myself, but there don't seem to be any.
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #6 |
Created attachment 1419402
File: backtrace
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #7 |
Created attachment 1419403
File: cgroup
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #8 |
Created attachment 1419404
File: core_backtrace
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #9 |
Created attachment 1419405
File: cpuinfo
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #10 |
Created attachment 1419406
File: dso_list
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #11 |
Created attachment 1419407
File: environ
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #12 |
Created attachment 1419408
File: limits
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #13 |
Created attachment 1419409
File: maps
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #14 |
Created attachment 1419410
File: mountinfo
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #15 |
Created attachment 1419411
File: open_fds
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #16 |
Created attachment 1419412
File: proc_pid_status
In Red Hat Bugzilla #1565220, code (code-redhat-bugs) wrote : | #17 |
Similar problem has been detected:
Started dragging a text selection around.
reporter: libreport-2.9.4
backtrace_rating: 4
cmdline: inkscape /home/da/
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=11ea4f5d97d14
kernel: 4.16.0-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, woodard (woodard-redhat-bugs) wrote : | #18 |
I've got a very similar problem:
$ rpm -q inkscape
inkscape-
/usr/include/
Thread 1 "inkscape" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/
50 return ret;
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/
#1 0x00007fffedcbe591 in __GI_abort () at abort.c:79
#2 0x00007ffff6eb4748 in std::__
#3 0x00007ffff75f63d3 in std::vector<
from /usr/bin/
#4 0x00007ffff75f090d in Inkscape:
#5 0x00007ffff75b1ea0 in SPText:
#6 0x00007ffff75b2b65 in SPText:
#7 0x00007ffff758fd48 in SPObject:
#8 0x00007ffff756b165 in SPGroup:
#9 0x00007ffff758fd48 in SPObject:
#10 0x00007ffff756b165 in SPGroup:
#11 0x00007ffff75a011c in SPRoot:
#12 0x00007ffff758fd48 in SPObject:
#13 0x00007ffff7479e62 in SPDocument:
#14 0x00007ffff7479e9d in sp_document_
#15 0x00007ffff476d0eb in g_idle_dispatch () from /lib64/
#16 0x00007ffff47707cd in g_main_
#17 0x00007ffff4770b98 in g_main_
#18 0x00007ffff4770ec2 in g_main_loop_run () from /lib64/
#19 0x00007ffff0457703 in gtk_dialog_run () from /lib64/
#20 0x00007ffff71e1560 in Inkscape:
#21 0x00007ffff748d15b in sp_file_
---Type <return> to continue, or q <return> to qui...
In Red Hat Bugzilla #1565220, woodard (woodard-redhat-bugs) wrote : | #19 |
Created attachment 1430418
problem that reproduces this crash
In Red Hat Bugzilla #1565220, larikwhite (larikwhite-redhat-bugs) wrote : | #20 |
*** Bug 1578869 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, rolle.hoffmann (rolle.hoffmann-redhat-bugs) wrote : | #21 |
Similar problem has been detected:
1. I added a png-image.
2. Then I added a text (with outline color).
3. duplicate the text and changed the text string
crash
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=9c13e53b9a3b4
kernel: 4.16.9-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, rafsoon (rafsoon-redhat-bugs) wrote : | #22 |
Similar problem has been detected:
Inkscape crashed when editing a file (imported pdf generated online from a website). A backup svg file was saved automatically after the crash. Opening the saved backup file causes crash each time, like the one I report here.
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape /home/rafal/
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=c99d1b39981a4
kernel: 4.16.8-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, rafsoon (rafsoon-redhat-bugs) wrote : | #23 |
Similar problem has been detected:
Found the bug is surprisingly easy to reproduce in my version of inkscape:
1. Open inkscape (new file)
2. Create a text field
3. Type in some text and hit the Enter key
4. Crash
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape /home/rafal/
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=c99d1b39981a4
kernel: 4.16.8-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Andrew Cowie (afcowie) wrote : | #1 |
Encountered what appears to be the same problem on Fedora 28.
$ inkscape --export-area-page --export-
/usr/include/
Emergency save activated!
Emergency save completed. Inkscape will close now.
$ inkscape --version
Inkscape 0.92.3 (2405546, 2018-03-11)
AfC
summary: |
- Segmentation fault converting SVG to PDF on alpine linux + Segmentation fault converting SVG to PDF |
In Red Hat Bugzilla #1565220, andrew (andrew-redhat-bugs-1) wrote : | #24 |
This has shown up on Fedora 28 (here) and on Alpine Linux. I found this bug from someone on Alpine Linux. https:/
AfC
Changed in inkscape (Fedora): | |
importance: | Unknown → Undecided |
status: | Unknown → Confirmed |
In Red Hat Bugzilla #1565220, mallmanndias (mallmanndias-redhat-bugs) wrote : | #25 |
*** Bug 1589365 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, ingo (ingo-redhat-bugs-1) wrote : | #26 |
My report was rejected as duplicate of this after uploading everything...
It is specific to fedora's built of inkscape and cannot be reproduced with the same inkscape version on most other distributions. Nor does it show in a self-built one. The same bug reported directly to inkscape has there (at least) two issue ids:
https:/
https:/
These tickets also contain files to test the bug with and detailed instructions on how to reproduce.
Cheers.
In Red Hat Bugzilla #1565220, dibicono (dibicono-redhat-bugs) wrote : | #27 |
*** Bug 1589452 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, sam.bristow (sam.bristow-redhat-bugs) wrote : | #28 |
*** Bug 1590078 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, mj.wilson.uk (mj.wilson.uk-redhat-bugs) wrote : | #29 |
*** Bug 1590231 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, hipolitofuentes (hipolitofuentes-redhat-bugs) wrote : | #30 |
*** Bug 1590590 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, pviktori (pviktori-redhat-bugs) wrote : | #31 |
Similar problem has been detected:
I pressed Enter while editing a piece of text.
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=a8881ea714074
kernel: 4.16.14-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, pviktori (pviktori-redhat-bugs) wrote : | #32 |
Similar problem has been detected:
I pressed Enter whileediting a piece of text.
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=a8881ea714074
kernel: 4.16.14-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, damidalla (damidalla-redhat-bugs) wrote : | #33 |
Similar problem has been detected:
1. Open a new Inkscape document
2. Create a new Text
3. Start writing and press the Enter key, going to a new line
Inkscape crashes and, obviously, that's not the desired behaviour!
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=6a7d75e9050e4
kernel: 4.16.14-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, g (g-redhat-bugs) wrote : | #34 |
*** Bug 1592105 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, gn.prp.gabriel (gn.prp.gabriel-redhat-bugs) wrote : | #35 |
*** Bug 1592776 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, gn.prp.gabriel (gn.prp.gabriel-redhat-bugs) wrote : | #36 |
Description of problem:
The program execution is aborted every time you try to break the line of a text that the area was not defined by drag and drop of the cursor. Sometimes (often) this also happens with text boxes with defined area.
Steps to Reproduce:
- Open an empty document in Inkscape
- Select the text tool and click on the editing area
- Type any text, like "inkscape"
- Break the line by pressing enter.
- program closes immediately.
Version-Release number of selected component:
inkscape-
Additional info:
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=789fb53797304
kernel: 4.16.14-
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, liebundartig (liebundartig-redhat-bugs) wrote : | #37 |
Similar problem has been detected:
I tried to open an SVG file created with Fedora 26 x86_64's version of Inkscape.
$ inkscape name.svg
/usr/include/
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
WARNING: Requested update while update in progress, counter = 5
... previous line repeated some 30 times ...
Aborted (core dumped)
Downgrading Inkscape in Fedora 28 x86_64 does not help.
Using a snap package helps.
Manually searching RHBZ during backtrace creation I found bug 1590279. It results in the same error message.
reporter: libreport-2.9.4
backtrace_rating: 4
cmdline: inkscape NewKineticModel
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=98a34e76d77c4
kernel: 4.16.3-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, woodard (woodard-redhat-bugs) wrote : | #38 |
*** Bug 1590279 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, mkolman (mkolman-redhat-bugs) wrote : | #39 |
Similar problem has been detected:
Tried to open a bigger (~2 MB) SVG file & Inskcape crashed.
Reproducer:
$ git clone https:/
Cloning into 'modrana-
remote: Counting objects: 312, done.
remote: Total 312 (delta 0), reused 0 (delta 0), pack-reused 312
Receiving objects: 100% (312/312), 1.70 MiB | 1.89 MiB/s, done.
Resolving deltas: 100% (85/85), done.
$ cd modrana-graphics/
$ inkscape icons.svg
WARNING: unknown type: svg:foreignObject
WARNING: unknown type: svg:foreignObject
WARNING: unknown type: svg:foreignObject
/usr/include/
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
/usr/include/
Aborted (core dumped)
Additional information:
Krita can open the file just fine without crashing.
reporter: libreport-2.9.5
backtrace_rating: 3
cmdline: inkscape icons.svg
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=24a4982d27604
kernel: 4.15.17-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, babkinstas (babkinstas-redhat-bugs) wrote : | #40 |
*** Bug 1595764 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, info (info-redhat-bugs) wrote : | #41 |
A workaround is to install the Inkscape flatpak from Flathub, though that is currently an earlier version 0.92.2. If necessary you can manipulate text in the flatpak Inkscape, then copy and paste it into the Fedora version.
In Red Hat Bugzilla #1565220, lpampolha (lpampolha-redhat-bugs) wrote : | #42 |
*** Bug 1597066 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, rafsoon (rafsoon-redhat-bugs) wrote : | #43 |
A recent patch on Fedora 28 fixes this problem for me:
$ inkscape --version
Inkscape 0.92.3 (2405546, 2018-03-11)
In Red Hat Bugzilla #1565220, rafsoon (rafsoon-redhat-bugs) wrote : | #44 |
(In reply to Rafal from comment #38)
> A recent patch on Fedora 28 fixes this problem for me:
> $ inkscape --version
> Inkscape 0.92.3 (2405546, 2018-03-11)
$ rpm -q inkscape
inkscape-
In Red Hat Bugzilla #1565220, liebundartig (liebundartig-redhat-bugs) wrote : | #45 |
This version fixed my problem too:
$ rpm -q inkscape
inkscape-
In Red Hat Bugzilla #1565220, jonha87 (jonha87-redhat-bugs) wrote : | #46 |
Similar problem has been detected:
Writing Test in Inkscape
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=0f11c5d751fa4
kernel: 4.17.3-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, jonha87 (jonha87-redhat-bugs) wrote : | #47 |
Similar problem has been detected:
Double clicked on text object and deleted a word
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=0f11c5d751fa4
kernel: 4.17.3-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, info (info-redhat-bugs) wrote : | #48 |
With July's inkscape-
stl_vector.h:950: std::vector<_Tp, _Alloc>
in the console and
std::
possibly the same as comment #13 and comment #32, even though comment #40 reports this version fixed it.
I haven't been able to reproduce that crash, so the newer version seems better but not out of the woods.
In Red Hat Bugzilla #1565220, mcrha (mcrha-redhat-bugs) wrote : | #49 |
This might be a wild shot, but if it's a Fedora specific issue, maybe it's related to [1], though inkscape itself is not listed in those identified packages. I can be complete wrong, it only reminded me of this [1] message. I'm sorry if this would mislead anyone.
[1] https://<email address hidden>
Benjamin Buch (benni-buch) wrote : | #2 |
- Segmentation when converting this to PDF Edit (24.6 KiB, image/svg+xml)
Inkscape version: 0.92.2-r1 on alpine linux
Reproduce with:
~$ docker run -it -v ~/download:
# apk add inkscape
[...]
# cd download
# inkscape -D -z --file=
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
** Message: 21:53:59.777: Error: Inkscape encountered an internal error and will close now.
Segmentation fault (core dumped)
Additionally I executed via gdb:
/download # apk add gdb
(1/5) Installing gdbm (1.13-r1)
(2/5) Installing xz-libs (5.2.4-r0)
(3/5) Installing sqlite-libs (3.24.0-r0)
(4/5) Installing python3 (3.6.4-r1)
(5/5) Installing gdb (8.0.1-r6)
Executing busybox-
OK: 153 MiB in 98 packages
/download # gdb --args inkscape -D -z --file=
GNU gdb (GDB) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://
Find the GDB manual and other documentation resources online at:
<http://
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from inkscape...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/inkscape -D -z --file=
warning: Error disabling address space randomization: Operation not permitted
[New LWP 52]
[New LWP 53]
[New LWP 54]
[New LWP 55]
[New LWP 56]
[New LWP 57]
[New LWP 58]
Thread 1 "inkscape" received signal SIGSEGV, Segmentation fault.
0x000055f1b6e04398 in font_factory:
(gdb) bt
#0 0x000055f1b6e04398 in font_factory:
#1 0x000055f1b6e04149 in font_factory:
#2 0x000055f1b6e04677 in font_factory:
#3 0x000055f1b6d0a97b in SPText:
#4 0x000055f1b6d0b032 in SPText:
#5 0x000055f1b6c4f60f in fix_blank_
#6 0x000055f1b6c4ffa8 in sp_file_
#7 0x000055f1b6c4ffd2 in sp_file_
#8 0x000055f1b6c4ffd2 in sp_file_
#9 0x000055f1b6c50038 in sp_file_
#10 0x000055f1b6c3f956 in SPDocument:
#11 0x000055f1b6c3f
Alvin Penner (apenner) wrote : | #3 |
- not reproduced on Windows 10, Inkscape 0.92.3 (2405546, 2018-03-11), using the command:
inkscape --export-area-page --export-
In Red Hat Bugzilla #1565220, mallmanndias (mallmanndias-redhat-bugs) wrote : | #50 |
*** Bug 1607075 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, adriansilvanio (adriansilvanio-redhat-bugs) wrote : | #51 |
*** Bug 1610607 has been marked as a duplicate of this bug. ***
Benjamin Buch (benni-buch) wrote : | #4 |
Installing ttf-dejavu on alpine does fix it.
I suppose the sigfault (Inkscape 0.92.2-r1) appears if there are no fonts installed. On Inkscape 0.91 the text parts are left out in this case. Both behaviors are bad.
Please let Inkscape check if a suitable font is installed and if not let it exit with an error.
In Red Hat Bugzilla #1565220, doug.hs (doug.hs-redhat-bugs) wrote : | #52 |
*** Bug 1631986 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, ingobugzilla (ingobugzilla-redhat-bugs) wrote : | #53 |
Similar problem has been detected:
Clicking on a text box to modify a letter.
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=68a33e6f5a054
kernel: 4.18.9-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, superman.jason (superman.jason-redhat-bugs) wrote : | #54 |
*** Bug 1632878 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, tarot.espiritudelzen (tarot.espiritudelzen-redhat-bugs) wrote : | #55 |
*** Bug 1634444 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, erwan-redhatbugzilla (erwan-redhatbugzilla-redhat-bugs) wrote : | #56 |
Similar problem has been detected:
Editing text in a complex SVG obtained from printing a PDF into SVG in Gnome
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: inkscape /home/ebousse/
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=8fc6d50d055a4
kernel: 4.18.12-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, dominguezmendoza.miguelangel (dominguezmendoza.miguelangel-redhat-bugs) wrote : | #57 |
*** Bug 1641306 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, vlad (vlad-redhat-bugs) wrote : | #58 |
*** Bug 1644145 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, morgan.gangwere (morgan.gangwere-redhat-bugs) wrote : | #59 |
*** Bug 1645728 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, mryodatak (mryodatak-redhat-bugs) wrote : | #60 |
Same for me on fedora 29 :
/usr/include/
Emergency save activated!
Emergency save completed. Inkscape will close now.
If you can reproduce this crash, please file a bug at www.inkscape.org
with a detailed description of the steps leading to the crash, so we can fix it.
/usr/include/
[1] 17312 abort (core dumped) inkscape
In Red Hat Bugzilla #1565220, paul (paul-redhat-bugs-1) wrote : | #61 |
Similar problem has been detected:
I was editing a file with a text element. I selected the element and clicked on it to try to edit the text. Inkscape encountered an internal error.
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: /usr/bin/inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=9505d5ca33fa4
kernel: 4.18.16-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, mcrha (mcrha-redhat-bugs) wrote : | #62 |
This looks related to bug #1575842, but the previous comment contains inkscape-
In Red Hat Bugzilla #1565220, liebundartig (liebundartig-redhat-bugs) wrote : | #63 |
(in reply to my comment #40) my workflow did not trigger the bug anymore, but it seems to be still around.
Yesterday I encountered this bug on Fedora 28 (and today on 29) x86_64.
$ rpm -q inkscape
inkscape-
and
inkscape-
I found an easy and reliable way to trigger the bug with the packages from the Fedora repositories, I did not try the snap/flatpack package:
1. start inkscape
2. press F8 (to select text tool)
3. left click somewhere on the canvas
4. press enter
5. press up arrow, hold down shift, press down arrow
6. inkscape crashes
In Red Hat Bugzilla #1565220, jscarbor (jscarbor-redhat-bugs) wrote : | #64 |
Here's an easier way to crash inkscape-
1. Start inkscape.
2. Use the text tool and place a text box, then enter 3 characters.
3. With the text tool, click near the end of the text string.
4. Inkscape crashes
Interestingly, it does not crash if you click at the beginning of the text string in step 3.
In Red Hat Bugzilla #1565220, olsam (olsam-redhat-bugs) wrote : | #65 |
Similar problem has been detected:
I double clicked on a text field. There was another text field covering the same area, but I think I clicked on the part outside of the shared space.
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: /usr/bin/inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=16b07eceedf84
kernel: 4.18.18-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, lucavall90 (lucavall90-redhat-bugs) wrote : | #66 |
*** Bug 1653271 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #1565220, adrianhp (adrianhp-redhat-bugs) wrote : | #67 |
Similar problem has been detected:
Al seleccionar un texto de cualquier longitud y arrastrar el cursor hasta el último caracter se produce este error, perdiéndose los datos desde la última salvaguarda.
reporter: libreport-2.9.5
backtrace_rating: 4
cmdline: /usr/bin/inkscape
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=7667baf7aa084
kernel: 4.20.7-
package: inkscape-
reason: inkscape killed by SIGABRT
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
In Red Hat Bugzilla #1565220, bcotton (bcotton-redhat-bugs) wrote : | #68 |
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.
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 28 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.
In Red Hat Bugzilla #1565220, bcotton (bcotton-redhat-bugs) wrote : | #69 |
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.
In Red Hat Bugzilla #1565220, jscarbor (jscarbor-redhat-bugs) wrote : | #70 |
I see that the issue in Comment 0, my issue in Comment 59, and the issue in Comment 58 have been resolved in Fedora 29, Inkscape 0.92.4. I didn't test every sequence from every comment, but it does seem more stable now when fiddling with text.
Changed in inkscape (Fedora): | |
status: | Confirmed → Won't Fix |
grey tomorrow (gtomorrow) wrote : | #71 |
Closing because INVALID.
If you feel this issue has been unjustly closed, please feel free to open a new issue at https:/
Closed by: https:/
tags: | added: bug-migration |
Changed in inkscape: | |
status: | New → Invalid |
Description of problem:
I double-clicked on a row of text and pressed Delete.
Version-Release number of selected component: 0.92.2- 6.fc28
inkscape-
Additional info: Pictures/ download unique identifiers.svg replacement_ assert 3ffb85d769ed717 ed00;i= 2e109;b= 6241f78103ff4b4 6a0f5080968c004 04;m=16ac6d1f16 ;t=5696cc5e3e78 d;x=64550c1b8eb 55383 300.fc28. x86_64
reporter: libreport-2.9.4
backtrace_rating: 4
cmdline: inkscape /home/da/
crash_function: std::__
executable: /usr/bin/inkscape
journald_cursor: s=11ea4f5d97d14
kernel: 4.16.0-
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000