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 576244 - crash in Evolution Mail and Calendar: nothing!
crash in Evolution Mail and Calendar: nothing!
Status: RESOLVED DUPLICATE of bug 400988
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-03-21 23:46 UTC by Sam Morris
Modified: 2009-03-22 01:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Sam Morris 2009-03-21 23:46:10 UTC
What were you doing when the application crashed?
nothing!


Distribution: Debian squeeze/sid
Gnome Release: 2.24.2 2009-01-04 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.29-rc8-amd64 #1 SMP Tue Mar 17 01:54:39 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10599902
Selinux: No
Accessibility: Disabled
GTK+ Theme: Darklooks
Icon Theme: gnome

Memory status: size: 413896704 vsize: 413896704 resident: 14479360 share: 11472896 rss: 14479360 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237675005 rtime: 8 utime: 7 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/evolution-alarm-notify'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f6b9517e7e0 (LWP 21619)]
[New Thread 0x7f6b9515a950 (LWP 21620)]
0x00007f6b9183c31f in __libc_waitpid (pid=6869, stat_loc=0x7fff9d2dcab0, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7f6b9517e7e0 (LWP 21619))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.18.4/glib/gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.18.4/glib/gspawn.c line 694
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 alarm_trigger_cb
    at alarm-queue.c line 1658
  • #7 alarm_ready_cb
    at alarm.c line 108
  • #8 g_timeout_dispatch
    at /build/buildd/glib2.0-2.18.4/glib/gmain.c line 3589
  • #9 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.18.4/glib/gmain.c line 2144
  • #10 g_main_context_iterate
    at /build/buildd/glib2.0-2.18.4/glib/gmain.c line 2778
  • #11 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.18.4/glib/gmain.c line 2986
  • #12 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #13 main
    at notify-main.c line 165
0x00007f6b9183c31f	41	in ../sysdeps/unix/sysv/linux/waitpid.c
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (936 sec old) ---------------------
(evolution:21566): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:21566): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:21566): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(evolution:21566): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
Window manager warning: Attempt to perform window operation 26 on window none when operation 26 on none already in effect
(gnome-appearance-properties:6236): appearance-properties-WARNING **: Unknown Tag: comment
(gnome-appearance-properties:6236): appearance-properties-WARNING **: Unknown Tag: comment
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-03-22 01:20:59 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 400988 ***