From: lxlml <lxlml@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Using text tool in gimp causes seg fault
Date: Tue, 20 Sep 2022 20:12:15 +0200 [thread overview]
Message-ID: <20220920181215.IWZKwzaEvmop3TvsZ0VIY-2Z5QXkzA9f8m2r38hzaqE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39393@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 5324 bytes --]
New comment by lxlml on void-packages repository
https://github.com/void-linux/void-packages/issues/39393#issuecomment-1252728855
Comment:
The root of this issue seems to be a bug in [glib](https://github.com/void-linux/void-packages/issues/39393)
`<!-- Copy-paste this whole debug data to report to developers -->
```
GNU Image Manipulation Program version 2.10.30
git-describe: GIMP_2_10_30
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=/usr/bin/cc
COLLECT_LTO_WRAPPER=/usr/lib64/gcc/x86_64-unknown-linux-gnu/10.2.1/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /builddir/gcc-10.2.1_pre1/configure --build=x86_64-unknown-linux-gnu --enable-gnu-unique-object --enable-vtable-verify --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --libexecdir=/usr/lib64 --libdir=/usr/lib64 --enable-threads=posix --enable-__cxa_atexit --disable-multilib --with-system-zlib --enable-shared --enable-lto --enable-plugins --enable-linker-build-id --disable-werror --disable-nls --enable-default-pie --enable-default-ssp --enable-checking=release --disable-libstdcxx-pch --with-isl --with-linker-hash-style=gnu --disable-sjlj-exceptions --disable-target-libiberty --enable-languages=c,c++,objc,obj-c++,fortran,lto,go,ada
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 10.2.1 20201203 (GCC)
# Libraries #
using babl version 0.1.96 (compiled against version 0.1.88)
using GEGL version 0.4.38 (compiled against version 0.4.34)
using GLib version 2.74.0 (compiled against version 2.70.2)
using GdkPixbuf version 2.42.6 (compiled against version 2.40.0)
using GTK+ version 2.24.33 (compiled against version 2.24.32)
using Pango version 1.50.9 (compiled against version 1.50.3)
using Fontconfig version 2.14.0 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)
```
> fatal error: Segmentation fault
Stack trace:
```
/usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x398)[0x7f1ac2edc888]
gimp-2.10(+0xe1d3b)[0x558c6f557d3b]
gimp-2.10(+0xe210a)[0x558c6f55810a]
gimp-2.10(+0xe2769)[0x558c6f558769]
/usr/lib/libpthread.so.0(+0x13900)[0x7f1ac2295900]
/usr/lib/libgobject-2.0.so.0(+0x24993)[0x7f1ac254c993]
/usr/lib/libgobject-2.0.so.0(+0x1aaf6)[0x7f1ac2542af6]
/usr/lib/libgobject-2.0.so.0(+0x1b482)[0x7f1ac2543482]
/usr/lib/libgobject-2.0.so.0(g_object_new_with_properties+0x1e9)[0x7f1ac2544919]
gimp-2.10(gimp_image_undo_push+0x1a6)[0x558c6f8dbb16]
gimp-2.10(gimp_image_undo_push_text_layer+0x10c)[0x558c6f8de8dc]
gimp-2.10(gimp_text_tool_apply+0xf7)[0x558c6f609f17]
gimp-2.10(+0x195b8f)[0x558c6f60bb8f]
gimp-2.10(+0x195d42)[0x558c6f60bd42]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7f1ac253d6bf]
/usr/lib/libgobject-2.0.so.0(+0x2937b)[0x7f1ac255137b]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0xfd1)[0x7f1ac2557d01]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f1ac2557ebf]
gimp-2.10(+0x1985f5)[0x558c6f60e5f5]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7f1ac253d6bf]
/usr/lib/libgobject-2.0.so.0(+0x2937b)[0x7f1ac255137b]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0xfd1)[0x7f1ac2557d01]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_by_name+0x1ff)[0x7f1ac25580df]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7f1ac253d6bf]
/usr/lib/libgobject-2.0.so.0(+0x2937b)[0x7f1ac255137b]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0xfd1)[0x7f1ac2557d01]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_by_name+0x1ff)[0x7f1ac25580df]
/usr/lib/libgtk-x11-2.0.so.0(+0x11bc70)[0x7f1ac311bc70]
/usr/lib/libgtk-x11-2.0.so.0(+0x11c253)[0x7f1ac311c253]
gimp-2.10(gimp_text_tool_editor_key_press+0x98)[0x558c6f60fbc8]
gimp-2.10(+0x1ef6bc)[0x558c6f6656bc]
gimp-2.10(gimp_display_shell_canvas_tool_events+0x91)[0x558c6f6666c1]
/usr/lib/libgtk-x11-2.0.so.0(+0x135807)[0x7f1ac3135807]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7f1ac253d6bf]
/usr/lib/libgobject-2.0.so.0(+0x2937b)[0x7f1ac255137b]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x97a)[0x7f1ac25576aa]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f1ac2557ebf]
/usr/lib/libgtk-x11-2.0.so.0(+0x2513e4)[0x7f1ac32513e4]
/usr/lib/libgtk-x11-2.0.so.0(gtk_window_propagate_key_event+0xa8)[0x7f1ac3264d48]
gimp-2.10(+0x30c7bb)[0x558c6f7827bb]
/usr/lib/libgtk-x11-2.0.so.0(+0x135807)[0x7f1ac3135807]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x16f)[0x7f1ac253d6bf]
/usr/lib/libgobject-2.0.so.0(+0x28d99)[0x7f1ac2550d99]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x97a)[0x7f1ac25576aa]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f1ac2557ebf]
/usr/lib/libgtk-x11-2.0.so.0(+0x2513e4)[0x7f1ac32513e4]
/usr/lib/libgtk-x11-2.0.so.0(gtk_propagate_event+0x14c)[0x7f1ac3133efc]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x36b)[0x7f1ac31342cb]
/usr/lib/libgdk-x11-2.0.so.0(+0x5facc)[0x7f1ac2fa3acc]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x25b)[0x7f1ac2444b2b]
/usr/lib/libglib-2.0.so.0(+0x54dd8)[0x7f1ac2444dd8]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x73)[0x7f1ac24450c3]
gimp-2.10(app_run+0x378)[0x558c6f5574d8]
gimp-2.10(main+0x37e)[0x558c6f556d9e]
/usr/lib/libc.so.6(__libc_start_main+0xea)[0x7f1ac20e3e0a]
gimp-2.10(_start+0x2a)[0x558c6f556f2a]
````
next prev parent reply other threads:[~2022-09-20 18:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 18:08 [ISSUE] " lxlml
2022-09-20 18:12 ` [ISSUE] [CLOSED] " lxlml
2022-09-20 18:12 ` lxlml [this message]
2022-09-20 18:15 ` lxlml
2022-09-20 18:42 ` lxlml
2022-09-20 18:57 ` paper42
2022-09-21 3:43 ` bugcrazy
2022-09-21 6:28 ` oreo639
2022-09-21 6:28 ` oreo639
2022-09-21 6:29 ` oreo639
2022-09-21 6:32 ` oreo639
2022-09-21 6:42 ` oreo639
2022-09-21 6:42 ` oreo639
2022-09-21 7:01 ` oreo639
2022-09-21 7:01 ` oreo639
2022-09-21 7:03 ` oreo639
2022-09-21 7:03 ` oreo639
2022-09-21 7:05 ` oreo639
2022-09-21 7:08 ` oreo639
2022-09-21 7:08 ` oreo639
2022-09-21 7:14 ` oreo639
2022-09-21 7:14 ` oreo639
2022-09-21 7:17 ` oreo639
2022-09-21 7:45 ` oreo639
2022-09-21 9:39 ` paper42
2022-09-21 10:32 ` biopsin
2022-09-21 14:06 ` bugcrazy
2022-09-21 14:25 ` biopsin
2022-09-21 14:26 ` biopsin
2022-09-21 14:26 ` paper42
2022-09-21 17:08 ` bugcrazy
2022-09-21 19:56 ` oreo639
2022-09-21 19:56 ` oreo639
2022-09-21 19:57 ` oreo639
2022-09-21 19:58 ` oreo639
2022-09-21 19:59 ` oreo639
2022-09-21 21:10 ` bugcrazy
2022-09-21 21:28 ` paper42
2022-09-21 21:31 ` paper42
2022-09-22 0:05 ` bugcrazy
2022-09-22 0:14 ` paper42
2022-09-24 15:57 ` paper42
2022-09-24 15:57 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-24 15:58 ` paper42
2022-09-25 15:24 ` paper42
2022-09-26 16:38 ` [ISSUE] [CLOSED] " paper42
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220920181215.IWZKwzaEvmop3TvsZ0VIY-2Z5QXkzA9f8m2r38hzaqE@z \
--to=lxlml@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).