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 553340 - crash in Evolution Mail and Calendar: i was going through the ...
crash in Evolution Mail and Calendar: i was going through the ...
Status: RESOLVED DUPLICATE of bug 451144
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-09-23 00:10 UTC by andy.elentari
Modified: 2008-09-23 21:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description andy.elentari 2008-09-23 00:10:27 UTC 
What were you doing when the application crashed?
i was going through the various months on my calendar hitting PgDn.  i double-clicked on an appointment.  i closed it.  i continued hitting PgDn.  then evolution crashed.


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

System: Linux 2.6.26-1-686 #1 SMP Thu Aug 28 12:00:54 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: dlg-neu

Memory status: size: 126484480 vsize: 126484480 resident: 55939072 share: 23703552 rss: 55939072 rss_rlim: 4294967295
CPU usage: start_time: 1222127620 rtime: 1644 utime: 1552 stime: 92 cutime:9 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6645720 (LWP 11012)]
[New Thread 0xb1c22b90 (LWP 11233)]
[New Thread 0xb2423b90 (LWP 11232)]
[New Thread 0xb40fdb90 (LWP 11050)]
0xb7f42424 in __kernel_vsyscall ()

+ Trace 207096

Thread 1 (Thread 0xb6645720 (LWP 11012))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.5/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 segv_redirect
    at main.c line 519
  • #7 <signal handler called>
  • #8 IA__g_type_check_instance_is_a
    at /tmp/buildd/glib2.0-2.16.5/gobject/gtype.c line 3138
  • #9 IA__g_object_ref
    at /tmp/buildd/glib2.0-2.16.5/gobject/gobject.c line 1718
  • #10 e_cal_model_copy_component_data
    at e-cal-model.c line 2107
  • #11 calendar_control_sensitize_calendar_commands
    at calendar-commands.c line 422
  • #12 gcal_calendar_focus_change_cb
    at calendar-commands.c line 528
  • #13 IA__g_cclosure_marshal_VOID__BOOLEAN
    at /tmp/buildd/glib2.0-2.16.5/gobject/gmarshal.c line 111
  • #14 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.16.5/gobject/gclosure.c line 490
  • #15 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.16.5/gobject/gsignal.c line 2440
  • #16 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.16.5/gobject/gsignal.c line 2199
  • #17 gtk_signal_emit
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 calendar_focus_change_cb
    at gnome-cal.c line 1082
  • #19 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
    from /usr/lib/libgobject-2.0.so.0
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.16.5/gobject/gclosure.c line 490
  • #0 __kernel_vsyscall 






Comment 1


Philip Withnall





          2008-09-23 21:27:36 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 ***