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 563973 - crash in Evolution Mail and Calendar: Editing properties (colo...
crash in Evolution Mail and Calendar: Editing properties (colo...
Status: RESOLVED DUPLICATE of bug 529037
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-12-10 12:47 UTC by pillateunlinux
Modified: 2008-12-10 13:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description pillateunlinux 2008-12-10 12:47:14 UTC
What were you doing when the application crashed?
Editing properties (color) of the calendar


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-powerpc #1 Thu Oct 9 12:30:07 CEST 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mac4Lin_MacMenu_v1.0_RC
Icon Theme: Mac4Lin_Icons_v1.0_RC

Memory status: size: 132141056 vsize: 132141056 resident: 45764608 share: 28827648 rss: 45764608 rss_rlim: 4294967295
CPU usage: start_time: 1228903889 rtime: 12971 utime: 10866 stime: 2105 cutime:8 cstime: 18 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x4804ed00 (LWP 8170)]
[New Thread 0x4b10d4b0 (LWP 8396)]
[New Thread 0x494b34b0 (LWP 8394)]
(no debugging symbols found)
0x0f60b290 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x4804ed00 (LWP 8170))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
  • #6 <signal handler called>
  • #7 gnome_calendar_get_current_view_widget
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #8 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #9 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #14 e_source_update_from_xml_node
    from /usr/lib/libedataserver-1.2.so.9
  • #15 ??
    from /usr/lib/evolution/2.22/components/libevolution-calendar.so
  • #16 e_config_commit
    from /usr/lib/evolution/2.22/libeutil.so.0
  • #17 ??
    from /usr/lib/evolution/2.22/libeutil.so.0
  • #18 g_cclosure_marshal_VOID
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 gtk_dialog_response
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #29 gtk_button_clicked
    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 /usr/lib/libgobject-2.0.so.0
  • #32 ??
    from /usr/lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #36 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #37 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #38 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #40 ??
    from /usr/lib/libgobject-2.0.so.0
  • #41 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #42 ??
    from /usr/lib/libgobject-2.0.so.0
  • #43 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #44 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #45 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #46 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #47 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #48 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #49 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #50 ??
    from /usr/lib/libglib-2.0.so.0
  • #51 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #52 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #53 ??
  • #54 ??
    from /lib/libc.so.6
  • #55 __libc_start_main
    from /lib/libc.so.6
  • #56 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (107973 sec old) ---------------------
END checking gmail account pillateunlinux ...
END checking gmail account pragmart ...
BEGIN checking gmail account pragmart ...
BEGIN checking gmail account pillateunlinux ...
END checking gmail account pillateunlinux ...
END checking gmail account pragmart ...
BEGIN checking gmail account pragmart ...
BEGIN checking gmail account pillateunlinux ...
END checking gmail account pillateunlinux ...
END checking gmail account pragmart ...
BEGIN checking gmail account pragmart ...
BEGIN checking gmail account pillateunlinux ...
END checking gmail account pillateunlinux ...
END checki
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Kandepu Prasad 2008-12-10 13:05:59 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 529037 ***