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 312857 - gw: Evolution crashes while starting up
gw: Evolution crashes while starting up
Status: RESOLVED DUPLICATE of bug 310866
Product: evolution
Classification: Applications
Component: Mailer
2.4.x (obsolete)
Other All
: High critical
: ---
Assigned To: parthasarathi susarla
Evolution QA team
groupwise evolution[groupwise]
: 313184 315014 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-08-08 07:57 UTC by Nicel KM
Modified: 2013-09-13 00:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Attachments
Patch for the bug (1.74 KB, patch)
2005-08-09 15:12 UTC, parthasarathi susarla
none Details | Review
Patch for the bug (3.38 KB, patch)
2005-08-25 06:08 UTC, parthasarathi susarla
none Details | Review
patch to fix the prob (7.06 KB, patch)
2005-09-02 12:49 UTC, vivek jain
none Details | Review

Description Nicel KM 2005-08-08 07:57:20 UTC
Steps to reproduce:
-Start evolution
-It gives the below message on console:


es menu class init
adding hook target 'source'

(evolution-2.4:10154): camel-WARNING **: camel_exception_get_id called with NULL
parameter.

(evolution-2.4:10154): camel-WARNING **: camel_exception_get_id called with NULL
parameter.

(evolution-2.4:10154): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion
`GDK_IS_GC (gc)' failed
get_folder: Mailbox
Refreshi_info:Mailbox
*** Exists in cache, continuing....


-Dialog saying Evolution crashed pops up.

Stack trace:
Backtrace was generated from '/opt/gnome/bin/evolution-2.4'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1097875072 (LWP 10154)]
[New Thread 1123036080 (LWP 10190)]
[Thread debugging using libthread_db enabled]
[New Thread 1097875072 (LWP 10154)]
[New Thread 1123036080 (LWP 10190)]
[New Thread 1120934832 (LWP 10189)]
[New Thread 1118833584 (LWP 10169)]
[New Thread 1114106800 (LWP 10168)]
[New Thread 1112005552 (LWP 10166)]
[New Thread 1109511088 (LWP 10165)]
[New Thread 1107323824 (LWP 10164)]
[Thread debugging using libthread_db enabled]
[New Thread 1097875072 (LWP 10154)]
[New Thread 1123036080 (LWP 10190)]
0xffffe410 in ?? ()

Thread 2 (Thread 1123036080 (LWP 10190))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /opt/gnome/lib/libcamel-provider-1.2.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 segv_redirect
    at main.c line 433
  • #13 segv_redirect
    at main.c line 433
  • #14 <signal handler called>
  • #15 camel_message_info_uint32
    at camel-folder-summary.c line 2863
  • #16 folder_getv
    at camel-folder.c line 353
  • #17 offline_folder_getv
    at camel-offline-folder.c line 207
  • #18 gw_getv
    at camel-groupwise-folder.c line 1786
  • #19 camel_object_get
    at camel-object.c line 1591
  • #20 camel_folder_get_unread_message_count
    at camel-folder.c line 585
  • #21 update_1folder
    at mail-folder-cache.c line 362
  • #22 folder_changed
    at mail-folder-cache.c line 457
  • #23 camel_object_trigger_event
    at camel-object.c line 1497
  • #24 gw_update_cache
    at camel-groupwise-folder.c line 1086
  • #25 groupwise_refresh_folder
    at camel-groupwise-folder.c line 866
  • #26 groupwise_refresh_info
    at camel-groupwise-folder.c line 756
  • #27 camel_folder_refresh_info
    at camel-folder.c line 299
  • #28 refresh_folders_get
    at mail-send-recv.c line 712
  • #29 mail_msg_received
    at mail-mt.c line 556
  • #30 thread_received_msg
    at e-msgport.c line 826
  • #31 thread_dispatch
    at e-msgport.c line 907
  • #32 start_thread
    from /lib/tls/libpthread.so.0
  • #33 clone
    from /lib/tls/libc.so.6


Other information:
Comment 1 Nagappan Alagappan 2005-08-08 11:05:56 UTC
Nicel: Whats the build date you are using ? I'm using 02 and 04 August-2005 with
groupwise account. I don't have any such issue.
Comment 2 Nicel KM 2005-08-08 11:25:49 UTC
I use the 2nd Aug build; It started happening only recently. Looks like some
issue with the built up cache.
Anyway, Partha confirmed it.
Comment 3 parthasarathi susarla 2005-08-09 15:12:30 UTC
Created attachment 50472 [details] [review]
Patch for the bug
Comment 4 parthasarathi susarla 2005-08-09 15:57:57 UTC
committed to HEAD
Comment 5 Nicel KM 2005-08-12 09:20:46 UTC
Still happening with the 12th Aug build:

stack trace from latest build:



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

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1097879168 (LWP 18899)]
[New Thread 1121676208 (LWP 18910)]
[Thread debugging using libthread_db enabled]
[New Thread 1097879168 (LWP 18899)]
[New Thread 1121676208 (LWP 18910)]
[Thread debugging using libthread_db enabled]
[New Thread 1097879168 (LWP 18899)]
[New Thread 1121676208 (LWP 18910)]
[New Thread 1119574960 (LWP 18909)]
[New Thread 1117076400 (LWP 18906)]
[New Thread 1114209200 (LWP 18905)]
[New Thread 1112107952 (LWP 18903)]
[New Thread 1109613488 (LWP 18902)]
[New Thread 1107422128 (LWP 18901)]
0xffffe410 in ?? ()

Thread 6 (Thread 1112107952 (LWP 18903))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /opt/gnome/lib/evolution-data-server-1.2/camel-providers/libcamelgroupwise.so
  • #9 ??
  • #10 groupwise_folder_item_to_msg
    at camel-groupwise-folder.c line 1419
  • #11 segv_redirect
    at main.c line 433
  • #12 <signal handler called>
  • #13 strcmp
    from /lib/tls/libc.so.6
  • #14 string_cmp
    at camel-groupwise-folder.c line 1432
  • #15 g_slist_find_custom
    from /opt/gnome/lib/libglib-2.0.so.0
  • #16 gw_update_all_items
    at camel-groupwise-folder.c line 1459
  • #17 update_update
    at camel-groupwise-folder.c line 723
  • #18 session_thread_received
    at camel-session.c line 524
  • #19 thread_received_msg
    at e-msgport.c line 826
  • #20 thread_dispatch
    at e-msgport.c line 907
  • #21 start_thread
    from /lib/tls/libpthread.so.0
  • #22 clone
    from /lib/tls/libc.so.6

Comment 6 C Shilpa 2005-08-17 08:38:50 UTC
Evolution crashed while filtering a folder. Using
evolution-2.3.7.0.200508160032-0.snap.novell.11.1 and
evolution-data-server-1.3.7.0.200508160032-0.snap.novell.11.1

Here is the stack trace:

Thread 8 (Thread 1113594800 (LWP 14057))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /opt/gnome/lib/libcamel-provider-1.2.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 segv_redirect
    at main.c line 433
  • #13 segv_redirect
    at main.c line 433
  • #14 <signal handler called>
  • #15 camel_message_info_uint32
    at camel-folder-summary.c line 2864
  • #16 summary_header_save
    at camel-folder-summary.c line 1458
  • #17 gw_summary_header_save
    at camel-groupwise-summary.c line 177
  • #18 camel_folder_summary_save
    at camel-folder-summary.c line 667
  • #19 groupwise_sync
    at camel-groupwise-folder.c line 629
  • #20 camel_folder_sync
    at camel-folder.c line 274
  • #21 close_folder
    at camel-filter-driver.c line 972
  • #22 g_hash_table_foreach
    from /opt/gnome/lib/libglib-2.0.so.0
  • #23 close_folders
    at camel-filter-driver.c line 989
  • #24 camel_filter_driver_finalise
    at camel-filter-driver.c line 249
  • #25 camel_object_unref
    at camel-object.c line 920
  • #26 em_filter_folder_element_filter
    at mail-ops.c line 153
  • #27 mail_msg_received
    at mail-mt.c line 556
  • #28 thread_received_msg
    at e-msgport.c line 826
  • #29 thread_dispatch
    at e-msgport.c line 907
  • #30 start_thread
    from /lib/tls/libpthread.so.0
  • #31 clone
    from /lib/tls/libc.so.6

Comment 7 parthasarathi susarla 2005-08-25 06:08:49 UTC
Created attachment 51312 [details] [review]
Patch for the bug

just making sure that the the folder is locked whenever needed.
Comment 8 vivek jain 2005-08-26 04:46:37 UTC
The patch is committed in CVS head on 2005-08-25. Closing this.
Comment 9 Nagappan Alagappan 2005-08-26 13:43:53 UTC
Verified with Evolution 2.3.8.

Nicel / Shilpa: If reproducable, please reopen it.
Comment 10 C Shilpa 2005-09-01 05:47:39 UTC
still happening using evolution-2.4.0.0.200508300318-0.snap.novell.11.1.
Reopening the bug.

Here is the stack trace:

Thread 3 (Thread 1121504176 (LWP 3535))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #5 _L_mutex_lock_33
    from /lib/tls/libpthread.so.0
  • #6 ??
  • #7 ??
  • #8 ??
    from /opt/gnome/lib/libcamel-provider-1.2.so.6
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 segv_redirect
    at main.c line 433
  • #13 segv_redirect
    at main.c line 433
  • #14 <signal handler called>
  • #15 camel_message_info_uint32
    at camel-folder-summary.c line 2864
  • #16 summary_header_save
    at camel-folder-summary.c line 1458
  • #17 gw_summary_header_save
    at camel-groupwise-summary.c line 176
  • #18 camel_folder_summary_save
    at camel-folder-summary.c line 667
  • #19 groupwise_sync
    at camel-groupwise-folder.c line 638
  • #20 groupwise_refresh_folder
    at camel-groupwise-folder.c line 835
  • #21 groupwise_refresh_info
    at camel-groupwise-folder.c line 791
  • #22 camel_folder_refresh_info
    at camel-folder.c line 299
  • #23 refresh_folder_refresh
    at mail-ops.c line 1582
  • #24 mail_msg_received
    at mail-mt.c line 556
  • #25 thread_received_msg
    at e-msgport.c line 826
  • #26 thread_dispatch
    at e-msgport.c line 907
  • #27 start_thread
    from /lib/tls/libpthread.so.0
  • #28 clone
    from /lib/tls/libc.so.6

Comment 11 vivek jain 2005-09-02 04:27:50 UTC
*** Bug 315014 has been marked as a duplicate of this bug. ***
Comment 12 vivek jain 2005-09-02 12:49:04 UTC
Created attachment 51712 [details] [review]
patch to fix the prob
Comment 13 C Shilpa 2005-09-09 05:22:20 UTC
*** Bug 313184 has been marked as a duplicate of this bug. ***
Comment 14 C Shilpa 2005-09-09 09:14:51 UTC
stack trace similar to trace given in #310866. marking as duplicate of #310866.

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