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 490137 - crash in Tasks: Viewing a message with a...
crash in Tasks: Viewing a message with a...
Status: RESOLVED DUPLICATE of bug 468427
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: 2007-10-25 13:23 UTC by lortiz
Modified: 2008-04-04 14:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description lortiz 2007-10-25 13:23:48 UTC
Version: 2.10

What were you doing when the application crashed?
Viewing a message with a forwarded meeting notice


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

System: Linux 2.6.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Bluecurve-Tangerine
Icon Theme: Crux

Memory status: size: 159801344 vsize: 159801344 resident: 64049152 share: 41222144 rss: 64049152 rss_rlim: 4294967295
CPU usage: start_time: 1193318299 rtime: 814 utime: 761 stime: 53 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208613152 (LWP 26868)]
[New Thread -1264596080 (LWP 27002)]
[New Thread -1308734576 (LWP 26921)]
[New Thread -1233126512 (LWP 26881)]
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208613152 (LWP 26868))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 e_cal_get_static_capability
    at e-cal.c line 2510
  • #6 find_cal_opened_cb
    at itip-formatter.c line 447
  • #7 IA__g_cclosure_marshal_VOID__INT
    at gmarshal.c line 216
  • #8 IA__g_closure_invoke
    at gclosure.c line 490
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #11 IA__g_signal_emit
    at gsignal.c line 2243
  • #12 async_signal_idle_cb
    at e-cal.c line 1774
  • #13 g_idle_dispatch
    at gmain.c line 3928
  • #14 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #15 g_main_context_iterate
    at gmain.c line 2677
  • #16 IA__g_main_loop_run
    at gmain.c line 2881
  • #17 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #18 main
    at main.c line 586
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
Increasing itip formatter search count to 1
Increasing itip formatter search count to 2
Increasing itip formatter search count to 3
Increasing itip formatter search count to 4
Decreasing itip formatter search count to 3
Decreasing itip formatter search count to 2
Decreasing itip formatter search count to 1
Decreasing itip formatter search count to 0
calendar selection changed
Increasing itip formatter search count to 1
Increasing itip formatter search count to 2
Increasing itip formatter search count to 3
Increasing itip formatter search count to 4
Decreasing itip formatter search count to 2
(evolution:26868): libecal-WARNING **: e-cal.c:2789: Unable to contact backend
--------------------------------------------------
Comment 1 Akhil Laddha 2008-04-04 14:11:07 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 468427 ***