Bug 531549 – Crash: Dismissing and Accepting Certificates on startup

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 531549 - Crash: Dismissing and Accepting Certificates on startup


Summary:	Crash: Dismissing and Accepting Certificates on startup


Status:	RESOLVED DUPLICATE of bug 553608

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.22.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:	2008-05-05 13:11 UTC by Karsten Bräckelmann
Modified:	2009-07-15 17:11 UTC

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

Description Karsten Bräckelmann 2008-05-05 13:11:22 UTC

Occured while debugging bug 531545 and bug 530245.

Started Evo, confirmed the Saved Search by hitting OK. Also, there was an dialog about a bad IMAP SSL Cert, asking me if I wanna trust it. (Don't really know why that one kept popping up on start.)

Dismissed the SSL Cert (by accident, actually). Same SSL Cert dialog popped up again. This time, I hit OK -- and Evolution crashed.


Note: This seems to be reproducible. I got that crash at least a second time during testing. However, I tried to narrow it down by altering the above steps of accepting the search. IIRC the crash did not occur, when I accepted the Search. Might be unrelated, though. For some strange reason, Evo now finally does not keep asking for the Cert, so I can't reproduce this any longer.

Pasting the entire stacktrace of all threads, since the top-most trace crashed early.


Distribution: Mandriva Linux release 2008.0 (Official) for i586
Gnome Release: 2.22.0 2008-03-15 (GARNOME)

Memory status: size: 161378304 vsize: 161378304 resident: 97488896 share: 16809984 rss: 97488896 rss_rlim: 4294967295
CPU usage: start_time: 1209991235 rtime: 846 utime: 763 stime: 83 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome-2.22/bin/evolution'

Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1232406848 (LWP 22672)]
[New Thread -1253037168 (LWP 22681)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 196936

Thread 2 (Thread -1253037168 (LWP 22681))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/i686/libpthread.so.0
#2 _L_mutex_lock_80
from /lib/i686/libpthread.so.0
#3 pthread_mutex_lock
from /lib/i686/libpthread.so.0
#4 <signal handler called>
#5 ??
#6 folder_changed
at camel-vee-folder.c line 1469
#7 camel_object_trigger_event
at camel-object.c line 1495
#8 folder_changed_change
at camel-vee-folder.c line 1426
#9 session_thread_proxy
at camel-session.c line 587
#10 g_thread_pool_thread_proxy
at gthreadpool.c line 265
#11 g_thread_create_proxy
at gthread.c line 635
#12 start_thread
from /lib/i686/libpthread.so.0
#13 clone
from /lib/i686/libc.so.6

Comment 1 Matthew Barnes 2008-05-05 18:15:42 UTC

Thread 2 crashed on a "folder-changed" event in camel-vee-folder.c, possibly on a bad function pointer.

static void
folder_changed(CamelFolder *sub, CamelFolderChangeInfo *changes, CamelVeeFolder *vf)
{
        ((CamelVeeFolderClass *)((CamelObject *)vf)->klass)->folder_changed(vf, sub, changes);
}

Comment 2 Kandepu Prasad 2008-05-26 06:45:19 UTC

could be duplicate of bug 434802

Comment 3 Milan Crha 2009-07-15 17:11:56 UTC

I'm marking this as a duplicate of a newer bug, as there are more duplicates and I asked there for some more detailed information about search folder setup and steps to reproduce this too.

Karsten, what are your search folders?

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