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 451058 - crash in Tasks: I was syncing my account...
crash in Tasks: I was syncing my account...
Status: RESOLVED DUPLICATE of bug 431459
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-25 21:13 UTC by Renich Bon Ciric
Modified: 2007-09-29 00:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Renich Bon Ciric 2007-06-25 21:13:20 UTC
Version: 2.10

What were you doing when the application crashed?
I was syncing my accounts. This crash happens very often! Not only when syncing but when trying to view contents of emails and copying/moving them.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 610070528 vsize: 610070528 resident: 40071168 share: 30613504 rss: 40071168 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182805535 rtime: 80 utime: 66 stime: 14 cutime:2 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912496402016 (LWP 3358)]
[New Thread 1178638672 (LWP 3443)]
[New Thread 1094719824 (LWP 3438)]
[New Thread 1105209680 (LWP 3437)]
[New Thread 1084229968 (LWP 3436)]
[New Thread 1115699536 (LWP 3435)]
[New Thread 1136679248 (LWP 3412)]
[New Thread 1126189392 (LWP 3411)]
0x00000039f500d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496402016 (LWP 3358))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /lib64/libglib-2.0.so.0
  • #5 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #6 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #7 main
    at main.c line 586
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (6 sec old) ---------------------
(evolution:3358): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:3358): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:3358): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:3358): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:3358): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
--------------------------------------------------
Comment 1 palfrey 2007-06-26 17:12:31 UTC
Can you reproduce this while running Evolution under gdb? See http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details how to do this.
Comment 2 Renich Bon Ciric 2007-06-28 05:48:51 UTC
Well, in the link you gave me, it says that bugbuddy should be the "easyest way" of doing this.

That is bugbuddy's output and it posted it by itself.
Comment 3 palfrey 2007-06-28 12:32:48 UTC
It's the easiest way, but it doesn't always work properly - mainly because Bug Buddy calls gdb *after* the crash, which makes it harder to catch certain cases of bugs (like this one). If you can get a trace from gdb directly, this would be more useful.
Comment 4 Renich Bon Ciric 2007-06-29 05:32:03 UTC
I get it, Tom. I'm on it right away. It's a little hard to catch, though...

I'll get back to you soon.
Comment 5 Renich Bon Ciric 2007-06-30 05:49:27 UTC
Ha! Got it!!

Here you go:

-- gdb output for evolution starts here --
[renich@renich ~]$ gdb evolution
GNU gdb Red Hat Linux (6.6-15.fc7rh)
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...
Using host libthread_db library "/lib64/libthread_db.so.1".
(gdb) run
Starting program: /usr/bin/evolution 
[Thread debugging using libthread_db enabled]
[New Thread 46912508085888 (LWP 6721)]
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
[Detaching after fork from child process 6726. (Try `set detach-on-fork off'.)]
[Detaching after fork from child process 6728.]
[Detaching after fork from child process 6730.]
[Detaching after fork from child process 6732.]
[Detaching after fork from child process 6734.]
[Detaching after fork from child process 6736.]
[Detaching after fork from child process 6738.]
[Detaching after fork from child process 6740.]
[Detaching after fork from child process 6742.]

(evolution:6721): evolution-mail-WARNING **: ignored this junk plugin: not enabled or we have already loaded one

(evolution:6721): e-utils-WARNING **: Plugin 'Spamassassin junk plugin' failed to load hook 'org.gnome.evolution.mail.junk:1.0'
** (evolution:6721): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:6721): DEBUG: mailto URL program: evolution
[New Thread 1084229968 (LWP 6743)]
[New Thread 1094719824 (LWP 6744)]
[New Thread 1105209680 (LWP 6745)]
[New Thread 1115699536 (LWP 6746)]
[New Thread 1126189392 (LWP 6747)]
[Thread 1126189392 (LWP 6747) exited]
[New Thread 1126189392 (LWP 6748)]
[New Thread 1136679248 (LWP 6749)]
[New Thread 1147169104 (LWP 6750)]
[Thread 1084229968 (LWP 6743) exited]
[Thread 1094719824 (LWP 6744) exited]

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
[New Thread 1094719824 (LWP 6768)]
[Thread 1147169104 (LWP 6750) exited]
[New Thread 1147169104 (LWP 6769)]
[New Thread 1084229968 (LWP 6770)]
[New Thread 1157658960 (LWP 6771)]

(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922

[New Thread 1168148816 (LWP 6772)]
[New Thread 1178638672 (LWP 6773)]
[Thread 1178638672 (LWP 6773) exited]
[New Thread 1178638672 (LWP 6774)]
[Thread 1084229968 (LWP 6770) exited]
[Thread 1147169104 (LWP 6769) exited]
[Thread 1157658960 (LWP 6771) exited]
[Thread 1178638672 (LWP 6774) exited]
[New Thread 1178638672 (LWP 6775)]

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

(evolution:6721): camel-WARNING **: camel_exception_get_id called with NULL parameter.
[Thread 1178638672 (LWP 6775) exited]

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

(evolution:6721): camel-WARNING **: camel_exception_get_id called with NULL parameter.
[Thread 1094719824 (LWP 6768) exited]
[Thread 1105209680 (LWP 6745) exited]

(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922

[New Thread 1105209680 (LWP 6788)]

(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922

(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


(evolution:6721): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 46912508085888 (LWP 6721)]
0x00000035a542f970 in g_main_context_check () from /lib64/libglib-2.0.so.0
(gdb) thread apply all bt

Thread 14 (Thread 1168148816 (LWP 6772))

  • #0 select
    from /lib64/libc.so.6
  • #1 camel_read
  • #2 camel_stream_buffer_gets
    at camel-stream-buffer.c line 411
  • #3 camel_imap_store_readline
    at camel-imap-store.c line 3031
  • #4 camel_imap_command_response
  • #5 imap_read_response
    at camel-imap-command.c line 374
  • #6 camel_imap_command
    at camel-imap-command.c line 116
  • #7 camel_imap_folder_selected
    at camel-imap-folder.c line 370
  • #8 imap_refresh_info
    at camel-imap-folder.c line 528
  • #9 mail_msg_proxy
    at mail-mt.c line 491
  • #10 ??
    from /lib64/libglib-2.0.so.0
  • #11 ??
    from /lib64/libglib-2.0.so.0
  • #12 start_thread
    from /lib64/libpthread.so.0
  • #13 clone
    from /lib64/libc.so.6

Thread 8 (Thread 1136679248 (LWP 6749))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #3 ??
    from /lib64/libglib-2.0.so.0
  • #4 ??
    from /usr/lib64/libORBit-2.so.0
  • #5 link_watch_move_io
    from /usr/lib64/libORBit-2.so.0
  • #6 link_servers_move_io_T
  • #7 ??
    from /usr/lib64/libORBit-2.so.0
  • #8 link_exec_command
    from /usr/lib64/libORBit-2.so.0
  • #9 link_set_io_thread
    from /usr/lib64/libORBit-2.so.0
  • #10 ORBit_small_invoke_stub
    from /usr/lib64/libORBit-2.so.0
  • #11 ConfigDatabase2_all_entries_with_schema_name
    from /usr/lib64/libgconf-2.so.4
  • #12 gconf_engine_all_entries
    from /usr/lib64/libgconf-2.so.4
  • #13 ??
    from /usr/lib64/libgconf-2.so.4
  • #14 gconf_client_add_dir
    from /usr/lib64/libgconf-2.so.4
  • #15 e_plugin_lib_enable
    at bf-junk-filter.c line 242
  • #16 epl_loadmodule
    at e-plugin.c line 844
  • #17 epl_invoke
    at e-plugin.c line 866
  • #18 em_junk_check_junk
    at em-junk-hook.c line 92
  • #19 junk_test
  • #20 e_sexp_term_eval
    at e-sexp.c line 710
  • #21 e_sexp_eval
    at e-sexp.c line 1306
  • #22 camel_filter_search_match
  • #23 camel_filter_driver_filter_message
    at camel-filter-driver.c line 1439
  • #24 filter_filter
    at camel-folder.c line 1711
  • #25 session_thread_proxy
    at camel-session.c line 530
  • #26 ??
    from /lib64/libglib-2.0.so.0
  • #27 ??
    from /lib64/libglib-2.0.so.0
  • #28 start_thread
    from /lib64/libpthread.so.0
  • #29 clone
    from /lib64/libc.so.6

Thread 1 (Thread 46912508085888 (LWP 6721))

  • #0 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #1 ??
    from /lib64/libglib-2.0.so.0
  • #2 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #3 bonobo_main
    from /usr/lib64/libbonobo-2.so.0
  • #4 main
    at main.c line 586

-- gdb output for evolution ends here --
Comment 6 Tobias Mueller 2007-08-19 01:39:10 UTC
Could be related to bug 431459

Is there any special way how you reproduce it?
Comment 7 Renich Bon Ciric 2007-08-19 08:07:50 UTC
Not that I am aware of...
Comment 8 Tobias Mueller 2007-09-29 00:07:54 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 431459 ***