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 505751 - crash in Tasks: reading email - applicat...
crash in Tasks: reading email - applicat...
Status: RESOLVED DUPLICATE of bug 400689
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-12-26 16:36 UTC by radeighan
Modified: 2008-02-11 05:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description radeighan 2007-12-26 16:36:38 UTC
Version: 2.10

What were you doing when the application crashed?
reading email - application open for +24h


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.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 138649600 vsize: 138649600 resident: 66957312 share: 37416960 rss: 66957312 rss_rlim: 4294967295
CPU usage: start_time: 1198536361 rtime: 3200 utime: 2817 stime: 383 cutime:321 cstime: 48 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 -1208452368 (LWP 32473)]
[New Thread -1229907056 (LWP 16487)]
[New Thread -1219413104 (LWP 32563)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208452368 (LWP 32473))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 camel_strdown
    from /usr/lib/libcamel-1.2.so.10
  • #6 em_popup_target_new_part
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #7 ??
    from /usr/lib/evolution/2.10/components/libevolution-mail.so
  • #8 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #10 ??
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #17 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #18 ??
    from /lib/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (8 sec old) ---------------------
main warning: can't store message (Invalid or incomplete multibyte or wide character): read box: "
[00000312] main playlist: nothing to play
[00000312] main playlist: stopping playback
(evolution:32473): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject'
(evolution:32473): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:32473): camel-CRITICAL **: camel_object_ref: assertion `CAMEL_IS_OBJECT(o)' failed
(evolution:32473): camel-WARNING **: Trying to check junk data is OBJECT 'CamelDataWrapper'
(evolution:32473): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed
(evolution:32473): camel-CRITICAL **: camel_data_wrapper_get_mime_type: assertion `CAMEL_IS_DATA_WRAPPER (data_wrapper)' failed
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-11 05:34:22 UTC
Thanks for the bug report. This particular bug has already been reported into
our bug tracking system, but please feel free to report any further bugs you
find.

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