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 446269 - crash in Evolution Mail: hope this provides more ...
crash in Evolution Mail: hope this provides more ...
Status: RESOLVED DUPLICATE of bug 371529
Product: evolution
Classification: Applications
Component: general
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-11 08:25 UTC by patrick.kox
Modified: 2007-06-11 09:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description patrick.kox 2007-06-11 08:25:26 UTC
What were you doing when the application crashed?
hope this provides more information then the last report.
Evolution crashes on startup


Distribution: Debian lenny/sid
Gnome Release: 2.18.2 2007-05-28 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1-686 #1 SMP Sat May 26 16:14:59 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Brushed
Icon Theme: OSX

Memory status: size: 114937856 vsize: 114937856 resident: 29827072 share: 16920576 rss: 29827072 rss_rlim: 4294967295
CPU usage: start_time: 1181550223 rtime: 221 utime: 194 stime: 27 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 -1233249696 (LWP 9881)]
[New Thread -1307575408 (LWP 9910)]
[New Thread -1299186800 (LWP 9909)]
[New Thread -1284633712 (LWP 9908)]
[New Thread -1249981552 (LWP 9900)]
[New Thread -1267856496 (LWP 9899)]
[New Thread -1293022320 (LWP 9897)]
[New Thread -1276245104 (LWP 9895)]
[New Thread -1259467888 (LWP 9893)]
[New Thread -1241592944 (LWP 9891)]
0xb7736b11 in ?? () from /lib/libpthread.so.0

Thread 8 (Thread -1276245104 (LWP 9895))

  • #0 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #1 _L_mutex_lock_88
    from /lib/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #3 segv_redirect
    at main.c line 436
  • #4 <signal handler called>
  • #5 camel_index_add_name
    at camel-index.c line 183
  • #6 camel_folder_summary_info_new_from_parser
    at camel-folder-summary.c line 1026
  • #7 camel_folder_summary_add_from_parser
    at camel-folder-summary.c line 931
  • #8 summary_update
    at camel-mbox-summary.c line 485
  • #9 mbox_summary_check
    at camel-mbox-summary.c line 572
  • #10 camel_local_summary_check
    at camel-local-summary.c line 268
  • #11 mbox_append_message
    at camel-mbox-folder.c line 203
  • #12 camel_folder_append_message
    at camel-folder.c line 648
  • #13 camel_filter_driver_filter_message
    at camel-filter-driver.c line 1511
  • #14 camel_filter_driver_filter_mbox
    at camel-filter-driver.c line 1192
  • #15 fetch_mail_fetch
    at mail-ops.c line 291
  • #16 mail_msg_received
    at mail-mt.c line 582
  • #17 thread_dispatch
    at e-msgport.c line 1005
  • #18 start_thread
    from /lib/libpthread.so.0
  • #19 clone
    from /lib/libc.so.6


----------- .xsession-errors (204 sec old) ---------------------
sh: disown: not found
sh: disown: not found

(synaptic:8988): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed

(synaptic:8988): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed
The program 'gdesklets-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadGC (invalid GC parameter)'.
  (Details: serial 144297 error_code 13 request_code 60 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
--------------------------------------------------
Comment 1 André Klapper 2007-06-11 09:09:32 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 371529 ***