Bug 794102 – Stack smashing detected in 2.9.9 on application start

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 794102 - Stack smashing detected in 2.9.9 on application start


Summary:	Stack smashing detected in 2.9.9 on application start


Status:	RESOLVED FIXED

Product:	GIMP
Classification:	Other
Component:	General
Version:	git master
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	2.10
Assigned To:	GIMP Bugs
QA Contact:	GIMP Bugs

URL:
Whiteboard:

Duplicates:	794130 794136 (view as bug list)
Depends on:
Blocks:

Reported:	2018-03-06 04:49 UTC by Nazar Mokrynskyi
Modified:	2018-03-06 21:32 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Nazar Mokrynskyi 2018-03-06 04:49:34 UTC

I've recently upgraded from 2.9.9~11-ubu18.04.1~ppa~91a947b to 2.9.9~15-ubu18.04.5~ppa~c03eb86 build on Ubuntu 18.04 and got following crash on GIMP start:

GIMP-CRITICAL: gimp_device_info_set_device: assertion '(info->device == NULL && GDK_IS_DEVICE (device)) || (GDK_IS_DEVICE (info->device) && device == NULL)' failed

GIMP-CRITICAL: gimp_device_info_set_device: assertion '(info->device == NULL && GDK_IS_DEVICE (device)) || (GDK_IS_DEVICE (info->device) && device == NULL)' failed

*** stack smashing detected ***: <unknown> terminated
gimp: fatal error: Aborted
27	../sysdeps/unix/sysv/linux/read.c: No such file or directory.
gimp (pid:18881): [E]xit, show [S]tack trace or [P]roceed: s
27	../sysdeps/unix/sysv/linux/read.c: No such file or directory.
[New LWP 18882]
[New LWP 18883]
[New LWP 18884]
[New LWP 18889]
[New LWP 18890]
[New LWP 18891]
[New LWP 18892]
[New LWP 18893]
[New LWP 18894]
[New LWP 18895]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f49c7c22384 in __libc_read (fd=30, buf=0x7ffc6becddc0, nbytes=256) at ../sysdeps/unix/sysv/linux/read.c:27

+ Trace 238457

#0 __libc_read
at ../sysdeps/unix/sysv/linux/read.c line 27
#1 gimp_stack_trace_print
#2 gimp_stack_trace_query
#3 0x000055d6880db6d0 in
#4 0x000055d6880dbb88 in
#5 0x000055d6880dc297 in
#6 <signal handler called>
#7 __GI_raise
at ../sysdeps/unix/sysv/linux/raise.c line 51
#8 __GI_abort
at abort.c line 79
#9 __libc_message
at ../sysdeps/posix/libc_fatal.c line 181
#10 __GI___fortify_fail_abort
at fortify_fail.c line 33
#11 __stack_chk_fail
at stack_chk_fail.c line 29
#12 0x000055d688356dc1 in
#13 gimp_plug_in_manager_call_query
#14 gimp_plug_in_manager_restore
#15 0x000055d68837c9c2 in
#16 g_closure_invoke
#17 0x00007f49c8935ac8 in
#18 g_signal_emit_valist
#19 g_signal_emit
#20 gimp_restore
#21 app_run
#22 main

Comment 1 Ell 2018-03-06 08:01:37 UTC

Thanks.  This is already fixed in master, by:

commit c6e8dd888cd92a473bbb8d6d23ccd92101032e8f
Author: Ell <ell_se@yahoo.com>
Date:   Mon Mar 5 12:45:22 2018 -0500

    app: fix buffer overflow in gimp_plug_in_open()
    
    Commit b9e629abbb2a40aa34cd41e7f093b7171bc249db added two more
    command-line arguments when spawning plug-ins, but failed to expand
    the args array...

 app/plug-in/gimpplugin.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

The CRITICALs are unrelated (and probably benign), but might be worth a bug of their own.

Comment 2 Ell 2018-03-06 18:58:35 UTC

*** Bug 794130 has been marked as a duplicate of this bug. ***

Comment 3 Ell 2018-03-06 21:32:56 UTC

*** Bug 794136 has been marked as a duplicate of this bug. ***