Bug 126742 – Memory fault in start-up

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 126742 - Memory fault in start-up


Summary:	Memory fault in start-up


Status:	RESOLVED DUPLICATE of bug 118517

Product:	GIMP
Classification:	Other
Component:	Plugins
Version:	1.x
Hardware:	Other Linux

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

URL:
Whiteboard:

Duplicates:	126645 (view as bug list)
Depends on:
Blocks:

Reported:	2003-11-11 18:44 UTC by Jean-Jacques Malosse
Modified:	2003-11-12 21:10 UTC

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

Description Jean-Jacques Malosse 2003-11-11 18:44:41 UTC

At the end of the startup process, the programme crashes and asks 
Proceed, Exit etc. It can proceed and then works OK. Here is the dump 
from gdb:

0  0x4071d328 in read () from /lib/libc.so.6

+ Trace 41655

#1 __JCR_LIST__
from /usr/lib/libglib-2.0.so.0
#2 g_io_channel_read_chars
at giochannel.c line 1772
#3 wire_read
at gimpwire.c line 135
#4 wire_read_int8
at gimpwire.c line 360
#5 wire_read_int32
at gimpwire.c line 320
#6 wire_read_msg
at gimpwire.c line 266
#7 plug_in_call_init
at plug-in.c line 224
#8 plug_ins_init
at plug-ins.c line 293
#9 gimp_marshal_VOID__POINTER_BOOLEAN
at gimpmarshal.c line 519
#10 g_type_class_meta_marshal
at gclosure.c line 514
#11 g_closure_invoke
at gclosure.c line 437
#12 signal_emit_unlocked_R
at gsignal.c line 2474
#13 g_signal_emit_valist
at gsignal.c line 2195
#14 g_signal_emit
at gsignal.c line 2239
#15 gimp_restore
at gimp.c line 911
#16 app_init
at app_procs.c line 219
#17 main
at main.c line 419
#18 __libc_start_main
from /lib/libc.so.6

Comment 1 Dave Neary 2003-11-11 19:05:00 UTC

It would have been better to add this comment to the existing bug,
rather than create a new one. In any case, this does indeed show that
a plug-in is crashing on initialisation, which is a recoverable
failure usually.

Without knowing which plug-in, there's not really much we can do. Do
you have an idea which plug-in was being queried? What was on the
splash screen at the time?

Cheers,
Dave.

Comment 2 Dave Neary 2003-11-11 19:05:07 UTC

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

Comment 3 Sven Neumann 2003-11-11 19:28:38 UTC

Just start GIMP with the --verbose command-line option and check the
output. As I said, it's most likely an old plug-in from an earlier
installation.

Comment 4 Jean-Jacques Malosse 2003-11-12 20:42:44 UTC

The bug is that an old plug-in (tool-safe-plugin.c (?)) was left in 
my my plug-in directories. It was dated from April 2003. The source 
is no longer in the distribution. The make install should clean up 
the directories. I would say that it is an installation bug. Thanks 
for the hint.

JJ Malosse

Comment 5 Sven Neumann 2003-11-12 21:09:00 UTC

You are supposed to uninstall anold version before you install a new
version.

Comment 6 Sven Neumann 2003-11-12 21:10:55 UTC


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