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 520153 - crash in Tasks: Nothing. I wasn't even ...
crash in Tasks: Nothing. I wasn't even ...
Status: RESOLVED DUPLICATE of bug 426807
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-03-03 18:38 UTC by Michael J. Hammel
Modified: 2008-03-20 13:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Michael J. Hammel 2008-03-03 18:38:28 UTC 
Version: 2.10

What were you doing when the application crashed?
Nothing.  I wasn't even sitting at the computer.  Maybe it was trying to do an IMAP fetch.


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.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 257056768 vsize: 257056768 resident: 95621120 share: 79785984 rss: 95621120 rss_rlim: 4294967295
CPU usage: start_time: 1204563750 rtime: 1238 utime: 1162 stime: 76 cutime:0 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 -1208805664 (LWP 22822)]
[New Thread -1453614192 (LWP 23543)]
[New Thread -1300399216 (LWP 22933)]
[New Thread -1268921456 (LWP 22874)]
[New Thread -1258017904 (LWP 22840)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 191179

Thread 1 (Thread -1208805664 (LWP 22822))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_slice_free_chain_with_offset
    from /lib/libglib-2.0.so.0
  • #9 g_slist_free
    from /lib/libglib-2.0.so.0
  • #10 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #14 ??
    from /lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #16 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #17 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (1367 sec old) ---------------------
CalDAV Eplugin starting up ...
** (evolution:22822): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:22822): 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:22822): e-data-server-DEBUG: Loading categories from "/home/mjhammel/.evolution/categories.xml"
(evolution:22822): e-data-server-DEBUG: Loaded 12 categories
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x4c00140 (Diagram1.d); these messages lack timestamps and therefore suck.
(evolution:22822): camel-CRITICAL **: camel_object_is: assertion `o != NULL' failed
(evolution:22822): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed
(evolution:22822): 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...
--------------------------------------------------
Comment 1 Tobias Mueller 2008-03-20 13:34:40 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 426807 ***