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 600490 - crash in Evolution Mail: Bug was on system stratu...
crash in Evolution Mail: Bug was on system stratu...
Status: RESOLVED DUPLICATE of bug 628635
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.28.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-11-02 22:44 UTC by mazen.neifer
Modified: 2010-09-08 08:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description mazen.neifer 2009-11-02 22:44:35 UTC
What were you doing when the application crashed?
Bug was on system stratup


Distribution: Debian squeeze/sid
Gnome Release: 2.28.0 2009-10-27 (Debian)
BugBuddy Version: 2.28.0

System: Linux 2.6.30-2-686 #1 SMP Sat Sep 26 01:16:22 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: Nuvola
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 77651968 vsize: 77651968 resident: 12783616 share: 10596352 rss: 12783616 rss_rlim: 18446744073709551615
CPU usage: start_time: 1257200249 rtime: 18 utime: 14 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb4fc9b70 (LWP 2856)]
[New Thread 0xb6024b70 (LWP 2556)]
0xb8060424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb63ab760 (LWP 2521))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 386
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gspawn.c line 700
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 display_notification
    at alarm-queue.c line 1494
  • #7 procedure_notification
    at alarm-queue.c line 1788
  • #8 alarm_trigger_cb
    at alarm-queue.c line 429
  • #9 alarm_ready_cb
    at alarm.c line 108
  • #10 g_timeout_dispatch
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 3396
  • #11 g_main_dispatch
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 1960
  • #12 IA__g_main_context_dispatch
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 2513
  • #13 g_main_context_iterate
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 2591
  • #14 IA__g_main_loop_run
    at /build/buildd-glib2.0_2.22.2-2-i386-R8GTDn/glib2.0-2.22.2/glib/gmain.c line 2799
  • #15 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #16 main
    at notify-main.c line 165
A debugging session is active.

	Inferior 1 [process 2521] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
** (evolution:2498): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
** (evolution:2498): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
console message: undefined @1: SyntaxError: Parse error
** (epiphany-browser:2529): DEBUG: NP_Initialize
** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded
** (epiphany-browser:2529): DEBUG: NP_Initialize
** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded
** (epiphany-browser:2529): DEBUG: NP_Initialize
** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded
** (epiphany-browser:2529): DEBUG: NP_Initialize
** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded
** (epiphany-browser:2529): DEBUG: NP_Initialize
** (epiphany-browser:2529): DEBUG: NP_Initialize succeeded
--------------------------------------------------
Comment 1 Akhil Laddha 2009-11-03 03:51:37 UTC
looks dupe of bug 596204
Comment 2 Milan Crha 2010-09-08 08:21:07 UTC
Marking this as a duplicate of a newer bug, because it contains a possible fix.

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