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 312916 - Evolution shows the 'has unexpectedly quit' dialog shortly after selecting my mailbox.
Evolution shows the 'has unexpectedly quit' dialog shortly after selecting my...
Status: RESOLVED DUPLICATE of bug 312831
Product: evolution
Classification: Applications
Component: Mailer
2.2.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-08-08 17:50 UTC by Tommy McGuire
Modified: 2005-08-09 04:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Tommy McGuire 2005-08-08 17:50:35 UTC
Steps to reproduce:
The stack trace contains the output of bugbuddy

Stack trace:
From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.10.0
Subject: Evolution shows the 'has unexpectedly quit' dialog shortly after
selecting my mailbox.

Distribution: Fedora Core release 4 (Stentz)
Package: devhelp
Severity: normal
Version: GNOME2.10.0 0.10
Gnome-Distributor: Red Hat, Inc
Synopsis: Evolution shows the 'has unexpectedly quit' dialog shortly after
selecting my mailbox.
Bugzilla-Product: devhelp
Bugzilla-Component: General
Bugzilla-Version: 0.10
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I have no further information than the subject, but I do have the
debuginfo package installed.

Steps to reproduce the crash:
1.
2.
3.

Expected Results:


How often does this happen?
Every time I open my mailbox.

Additional Information:
Possible duplicate of bug 273714.


Debugging Information:

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208424768 (LWP 25093)]
[New Thread -1253119056 (LWP 25129)]
[New Thread -1286878288 (LWP 25119)]
[New Thread -1242629200 (LWP 25118)]
[New Thread -1276118096 (LWP 25116)]
[New Thread -1263608912 (LWP 25115)]
[New Thread -1232139344 (LWP 25112)]
[New Thread -1221649488 (LWP 25111)]
[New Thread -1211159632 (LWP 25110)]
0x004f9402 in ?? ()

Thread 2 (Thread -1253119056 (LWP 25129))

  • #0 ??
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_36
    from /lib/libpthread.so.0
  • #3 pthread_kill
    from /lib/libpthread.so.0
  • #4 segv_redirect
    at main.c line 437
  • #5 <signal handler called>
  • #6 camel_folder_threaded_messages_dump
    from /usr/lib/libcamel-provider-1.2.so.3
  • #7 msort_with_tmp
    from /lib/libc.so.6
  • #8 msort_with_tmp
    from /lib/libc.so.6
  • #9 msort_with_tmp
    from /lib/libc.so.6
  • #10 msort_with_tmp
    from /lib/libc.so.6
  • #11 msort_with_tmp
    from /lib/libc.so.6
  • #12 msort_with_tmp
    from /lib/libc.so.6
  • #13 qsort
    from /lib/libc.so.6
  • #14 camel_folder_threaded_messages_dump
    from /usr/lib/libcamel-provider-1.2.so.3
  • #15 camel_folder_threaded_messages_dump
    from /usr/lib/libcamel-provider-1.2.so.3
  • #16 camel_folder_thread_messages_new
    from /usr/lib/libcamel-provider-1.2.so.3
  • #17 regen_list_regen
    at message-list.c line 3525



Other information:
Possible duplicate of bug 273714.
Comment 1 Tommy McGuire 2005-08-08 18:22:17 UTC
Another stack trace.

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1209166144 (LWP 25961)]
[New Thread -1253864528 (LWP 26006)]
[New Thread -1306977360 (LWP 26003)]
[New Thread -1296487504 (LWP 25990)]
[New Thread -1285604432 (LWP 25987)]
[New Thread -1264354384 (LWP 25986)]
[New Thread -1274844240 (LWP 25984)]
[New Thread -1243370576 (LWP 25981)]
[New Thread -1232880720 (LWP 25980)]
[New Thread -1222390864 (LWP 25979)]
[New Thread -1211901008 (LWP 25978)]
0x009be402 in ?? ()

Thread 4 (Thread -1296487504 (LWP 25990))

  • #0 ??
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_36
    from /lib/libpthread.so.0
  • #3 pthread_kill
    from /lib/libpthread.so.0
  • #4 segv_redirect
    at main.c line 437
  • #5 <signal handler called>
  • #6 sort_node
    at camel-folder-thread.c line 373
  • #7 msort_with_tmp
    from /lib/libc.so.6
  • #8 msort_with_tmp
    from /lib/libc.so.6
  • #9 msort_with_tmp
    from /lib/libc.so.6
  • #10 msort_with_tmp
    from /lib/libc.so.6
  • #11 msort_with_tmp
    from /lib/libc.so.6
  • #12 qsort
    from /lib/libc.so.6
  • #13 sort_thread
    at camel-folder-thread.c line 405

Comment 2 Not Zed 2005-08-09 04:08:58 UTC
i can see we're going to get a lot of duplicates of this one :(


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