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 480435 - crash in Tasks: Opening an appointment o...
crash in Tasks: Opening an appointment o...
Status: RESOLVED DUPLICATE of bug 451144
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-26 02:10 UTC by fdellalena
Modified: 2007-12-19 03:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description fdellalena 2007-09-26 02:10:16 UTC 
Version: 2.10

What were you doing when the application crashed?
Opening an appointment on Exchange Server Calendar 


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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: default.kde

Memory status: size: 202522624 vsize: 202522624 resident: 74997760 share: 50819072 rss: 74997760 rss_rlim: 4294967295
CPU usage: start_time: 1190772137 rtime: 649 utime: 574 stime: 75 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 -1208281376 (LWP 3692)]
[New Thread -1295955056 (LWP 3852)]
[New Thread -1352029296 (LWP 3783)]
[New Thread -1285465200 (LWP 3720)]
[New Thread -1220871280 (LWP 3717)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 165519

Thread 1 (Thread -1208281376 (LWP 3692))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 <signal handler called>
  • #5 g_object_ref
    from /lib/libgobject-2.0.so.0
  • #6 e_cal_model_copy_component_data
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #7 calendar_control_sensitize_calendar_commands
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #8 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #9 g_cclosure_marshal_VOID__BOOLEAN
    from /lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #11 ??
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #13 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #15 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /lib/libgobject-2.0.so.0
  • #26 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #27 ??
    from /lib/libgobject-2.0.so.0
  • #28 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #29 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #33 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #34 ??
    from /lib/libglib-2.0.so.0
  • #35 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #36 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #37 main
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-12-19 03:45:33 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 451144 ***