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 444624 - crash in Tasks: I clicked on Send/Receiv...
crash in Tasks: I clicked on Send/Receiv...
Status: RESOLVED DUPLICATE of bug 441638
Product: evolution
Classification: Applications
Component: Tasks
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-06 07:29 UTC by froztbyte
Modified: 2007-09-26 18:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description froztbyte 2007-06-06 07:29:55 UTC
What were you doing when the application crashed?
I clicked on Send/Receive and was waiting for it to finish when it crashed


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 173445120 vsize: 173445120 resident: 34373632 share: 21307392 rss: 34373632 rss_rlim: 4294967295
CPU usage: start_time: 1181114393 rtime: 443 utime: 409 stime: 34 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(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 -1208310048 (LWP 5560)]
[New Thread -1299625072 (LWP 5707)]
[New Thread -1249285232 (LWP 5592)]
[New Thread -1288742000 (LWP 5589)]
[New Thread -1238385776 (LWP 5578)]
(no debugging symbols found)
0x00bf9402 in __kernel_vsyscall ()

Thread 2 (Thread -1299625072 (LWP 5707))

  • #0 __kernel_vsyscall
  • #1 __lll_mutex_lock_wait
    from /lib/libpthread.so.0
  • #2 _L_mutex_lock_79
    from /lib/libpthread.so.0
  • #3 pthread_mutex_lock
    from /lib/libpthread.so.0
  • #4 ??
  • #5 <signal handler called>
  • #6 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #7 g_slist_free
    from /lib/libglib-2.0.so.0
  • #8 g_strsplit
    from /lib/libglib-2.0.so.0
  • #9 camel_uid_cache_new
    from /usr/lib/libcamel-provider-1.2.so.10
  • #10 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #11 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6


----------- .xsession-errors (11 sec old) ---------------------
** (nautilus:3697): WARNING **: Hit unhandled case 4 (Invalid parameters) in fm_report_error_loading_directory
CalDAV Eplugin starting up ...
** (evolution:5560): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:5560): DEBUG: mailto URL program: evolution
(evolution:5560): e-data-server-DEBUG: Loading categories from "/home/froztbyte/.evolution/categories.xml"
(evolution:5560): e-data-server-DEBUG: Loaded 33 categories
(evolution:5560): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:5560): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa514140'
(evolution:5560): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0xa514260'
(evolution:5560): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5560): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 palfrey 2007-06-06 10:27:56 UTC
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 and
reopen this bug or report a new one. Thanks in advance!
Comment 2 Tobias Mueller 2007-09-26 18:41:06 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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