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 388049 - crash in Evolution: mail lezen
crash in Evolution: mail lezen
Status: RESOLVED DUPLICATE of bug 360237
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
: 405482 415054 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-20 21:21 UTC by pderuytter
Modified: 2007-04-11 22:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description pderuytter 2006-12-20 21:21:42 UTC 
What were you doing when the application crashed?
mail lezen


Distribution: Fedora Core release 4 (Stentz)
Gnome Release: 2.16.1 2006-11-11 (GARNOME)
BugBuddy Version: 2.16.0

Memory status: size: 82661376 vsize: 0 resident: 82661376 share: 0 rss: 23015424 rss_rlim: 0
CPU usage: start_time: 1166649624 rtime: 0 utime: 759 stime: 0 cutime:687 cstime: 0 timeout: 72 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/garnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209039168 (LWP 7938)]
[New Thread -1247298640 (LWP 7956)]
[New Thread -1223222352 (LWP 7955)]
[New Thread -1233712208 (LWP 7950)]
[New Thread -1212732496 (LWP 7947)]
0x001ab402 in ?? ()

+ Trace 95779

Thread 3 (Thread -1223222352 (LWP 7955))

  • #0 ??
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_36
    from /lib/libpthread.so.0
  • #3 ??
  • #4 ??
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 <signal handler called>
  • #9 memset
    from /lib/libc.so.6
  • #10 e_memchunk_alloc0
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #11 parse_term_new
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #12 parse_value
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #13 parse_values
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #14 parse_value
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #15 e_sexp_parse
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #16 camel_folder_search_search
    from /opt/garnome/lib/libcamel-provider-1.2.so.8
  • #17 local_search_by_uids
    from /opt/garnome/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
  • #18 camel_folder_search_by_uids
    from /opt/garnome/lib/libcamel-provider-1.2.so.8
  • #19 vtrash_search_by_expression
    from /opt/garnome/lib/libcamel-provider-1.2.so.8
  • #20 camel_folder_search_by_expression
    from /opt/garnome/lib/libcamel-provider-1.2.so.8
  • #21 regen_list_regen
    from /opt/garnome/lib/evolution/2.8/components/libevolution-mail.so
  • #22 mail_msg_received
    from /opt/garnome/lib/evolution/2.8/components/libevolution-mail.so
  • #23 thread_dispatch
    from /opt/garnome/lib/libedataserver-1.2.so.7
  • #24 start_thread
    from /lib/libpthread.so.0
  • #25 clone
    from /lib/libc.so.6 






Comment 1


palfrey





          2007-01-07 17:08:03 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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






Comment 2


Kjartan Maraas





          2007-02-07 19:30:02 UTC
        



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






Comment 3


Susana





          2007-03-05 23:59:41 UTC
        



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






Comment 4


palfrey





          2007-04-11 22:25:40 UTC
        



Hmm. Not a dupe of 364944...

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!







Comment 5


palfrey





          2007-04-11 22:29:42 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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