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 468193 - crash in Email:
crash in Email:
Status: RESOLVED DUPLICATE of bug 451144
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: High critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 462486 462493 468197 475650 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-08-19 13:49 UTC by u.deblasiis
Modified: 2007-12-19 03:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description u.deblasiis 2007-08-19 13:49:30 UTC
Version: 2.10

What were you doing when the application crashed?



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.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 147480576 vsize: 147480576 resident: 46657536 share: 36462592 rss: 46657536 rss_rlim: 4294967295
CPU usage: start_time: 1187531257 rtime: 431 utime: 396 stime: 35 cutime:2 cstime: 5 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 -1208494368 (LWP 3494)]
[New Thread -1304708208 (LWP 3561)]
[New Thread -1272972400 (LWP 3520)]
[New Thread -1249318000 (LWP 3517)]
(no debugging symbols found)
0x00ad7402 in __kernel_vsyscall ()

Thread 1 (Thread -1208494368 (LWP 3494))

  • #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 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #26 ??
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #29 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #32 ??
    from /lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #37 gtk_widget_grab_focus
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #39 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #40 ??
    from /usr/lib/evolution/2.10/components/libevolution-calendar.so
  • #41 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #43 ??
    from /lib/libgobject-2.0.so.0
  • #44 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #45 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #46 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #50 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #51 ??
    from /lib/libglib-2.0.so.0
  • #52 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #53 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #54 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(evolution:3494): e-dateedit.c-WARNING **: time_text:09.00
(evolution:3494): e-dateedit.c-WARNING **: time_text:09.30
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x1a00e7a
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x14002c6
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x65
--------------------------------------------------
Comment 1 Johnny Jacob 2007-08-22 07:25:38 UTC
*** Bug 468197 has been marked as a duplicate of this bug. ***
Comment 2 Chenthill P 2007-08-22 17:59:16 UTC
*** Bug 462493 has been marked as a duplicate of this bug. ***
Comment 3 Chenthill P 2007-08-22 18:00:37 UTC
*** Bug 462486 has been marked as a duplicate of this bug. ***
Comment 4 palfrey 2007-12-04 18:05:01 UTC
*** Bug 475650 has been marked as a duplicate of this bug. ***
Comment 5 André Klapper 2007-12-19 03:45:29 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 ***