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 519207 - crash in Tasks: Clicked on Send/Receive
crash in Tasks: Clicked on Send/Receive
Status: RESOLVED DUPLICATE of bug 441638
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.10.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-02-28 07:21 UTC by ashwin42
Modified: 2008-02-28 17:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description ashwin42 2008-02-28 07:21:13 UTC
Version: 2.10

What were you doing when the application crashed?
Clicked on Send/Receive


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23 #2 SMP Sun Oct 14 22:40:11 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 294744064 vsize: 294744064 resident: 106958848 share: 89821184 rss: 106958848 rss_rlim: 4294967295
CPU usage: start_time: 1204181942 rtime: 738 utime: 654 stime: 84 cutime:0 cstime: 2 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 -1209043232 (LWP 6583)]
[New Thread -1311130736 (LWP 7092)]
[New Thread -1482417264 (LWP 7090)]
[New Thread -1465631856 (LWP 7088)]
[New Thread -1293952112 (LWP 6614)]
[New Thread -1379898480 (LWP 6612)]
[New Thread -1302344816 (LWP 6604)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 2 (Thread -1311130736 (LWP 7092))

  • #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 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 ??
    from /lib/libglib-2.0.so.0
  • #9 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #10 g_slist_free
    from /lib/libglib-2.0.so.0
  • #11 g_strsplit
    from /lib/libglib-2.0.so.0
  • #12 camel_uid_cache_new
    from /usr/lib/libcamel-provider-1.2.so.10
  • #13 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #15 ??
    from /lib/libglib-2.0.so.0
  • #16 ??
    from /lib/libglib-2.0.so.0
  • #17 start_thread
    from /lib/libpthread.so.0
  • #18 clone
    from /lib/libc.so.6


----------- .xsession-errors (45 sec old) ---------------------
  self.pbar.set_fraction(fract)
CalDAV Eplugin starting up ...
** (evolution:6583): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:6583): DEBUG: mailto URL program: evolution
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:6583): e-data-server-DEBUG: Loading categories from "/home/ashwin/.evolution/categories.xml"
(evolution:6583): e-data-server-DEBUG: Loaded 29 categories
(evolution:6583): libebook-WARNING **: invalid escape, passing it through
(evolution:6583): 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:6583): libebook-WARNING **: invalid escape, passing it through
--------------------------------------------------
Comment 1 Tobias Mueller 2008-02-28 17:05:20 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 ***