Bug 330742 – another Crash when saving a Signature (HTML format, with image)

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 330742 - another Crash when saving a Signature (HTML format, with image)


Summary:	another Crash when saving a Signature (HTML format, with image)


Status:	RESOLVED DUPLICATE of bug 239205

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.4.x (obsolete)
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-02-11 01:14 UTC by Karsten Bräckelmann
Modified:	2006-06-18 12:11 UTC

See Also:
GNOME target:	---
GNOME version:	2.11/2.12

Description Karsten Bräckelmann 2006-02-11 01:14:45 UTC

* Edit / Preferences / Composer Preferences / Signatures
* Edit an existing Signature
* Save it


Backtrace was generated from '/opt/gnome-2.12/bin/evolution-2.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 31085)]
[New Thread -1337984080 (LWP 31632)]
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 31085)]
[New Thread -1337984080 (LWP 31632)]
[Thread debugging using libthread_db enabled]
[New Thread -1229457728 (LWP 31085)]
[New Thread -1337984080 (LWP 31632)]
[New Thread -1324696656 (LWP 31189)]
[New Thread -1293808720 (LWP 31188)]
[New Thread -1302385744 (LWP 31115)]
[New Thread -1285416016 (LWP 31114)]
[New Thread -1268470864 (LWP 31096)]
[New Thread -1276863568 (LWP 31095)]
[New Thread -1260078160 (LWP 31093)]
[New Thread -1251292240 (LWP 31092)]
[New Thread -1242899536 (LWP 31091)]
[New Thread -1234506832 (LWP 31090)]
0xffffe410 in ?? ()

+ Trace 66082

#0 ??
#1 ??
#2 ??
#3 ??
#4 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#5 libgnomeui_segv_handle
from /opt/gnome-2.12.2/lib/libgnomeui-2.so.0
#6 <signal handler called>
#7 gtk_combo_box_get_model
from /opt/gnome-2.12.2/lib/libgtk-x11-2.0.so.0
#8 emae_signature_get_iter
from /opt/gnome-2.12.2/lib/evolution/2.4/components/libevolution-mail.so
#9 emae_signature_changed
from /opt/gnome-2.12.2/lib/evolution/2.4/components/libevolution-mail.so
#10 g_cclosure_marshal_VOID__OBJECT
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#12 signal_emit_unlocked_R
from /opt/gnome-2.12.2/lib/libgobject-2.0.so.0
#13 ??
#14 ??
#15 ??
#16 ??
#17 ??
#18 calloc
from /lib/tls/libc.so.6

Comment 1 Karsten Bräckelmann 2006-02-11 01:18:13 UTC

This was a Signtuare in HTML format with an (animated) image only.

The signature was saved, though. Happened teh second time in a row.

Comment 2 Karsten Bräckelmann 2006-02-11 06:27:01 UTC

Now that I re-built Evo and e-d-s with debugging symbols, I can not reproduce this crash... *sigh*

Comment 3 parthasarathi susarla 2006-02-16 10:41:27 UTC

Closing this bug, based on the last comment. Reopen if reproducible and has a better stack trace. Thanks

Comment 4 Karsten Bräckelmann 2006-02-18 23:02:12 UTC

What? Partha, this bug was always reproducible with an Evo without debugging symbols. Id don't see how these symbols could effect this, but...

Reproducible. REOPEN.

Comment 5 Ranjan Somani 2006-03-20 14:16:01 UTC

Karsten, I tried reproducing the bug but could not :-(. So, can u plz attach the image with which it crashed.

Comment 6 Karsten Bräckelmann 2006-03-25 02:47:20 UTC

I mentioned previously, that I am not able to reproduce this issue always. Plus, I got this issue by verifying some other bug in the first place, picking a somewhat random image... Thus it most likely is not related to the image.

Enabled debug symbols by default for my builds since. I'll attach any stacktrace with symbols I can get...

Comment 7 André Klapper 2006-06-18 12:11:17 UTC

same stacktrace as bug 239205 comment #8, closing as duplicate.

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