Bug 619134 – crash in Evolution Mail: Editing a plain-text mes...

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 619134 - crash in Evolution Mail: Editing a plain-text mes...


Summary:	crash in Evolution Mail: Editing a plain-text mes...


Status:	RESOLVED DUPLICATE of bug 615816

Product:	evolution
Classification:	Applications
Component:	BugBuddyBugs
Version:	2.28.x (obsolete)
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Evolution Triage Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-05-19 21:46 UTC by drdent42
Modified:	2010-05-20 00:18 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description drdent42 2010-05-19 21:46:41 UTC

What were you doing when the application crashed?
Editing a plain-text message.


Distribution: Debian squeeze/sid
Gnome Release: 2.30.0 2010-04-26 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.33.4 #1 SMP PREEMPT Fri May 14 15:46:46 MDT 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 238268416 vsize: 238268416 resident: 53628928 share: 17268736 rss: 53628928 rss_rlim: 18446744073709551615
CPU usage: start_time: 1274305410 rtime: 7588 utime: 5812 stime: 1776 cutime:65 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb32bbb70 (LWP 7493)]
[New Thread 0xb10efb70 (LWP 7492)]
[New Thread 0xac0e5b70 (LWP 7458)]
[New Thread 0xad8e8b70 (LWP 7457)]
[New Thread 0xb08eeb70 (LWP 7455)]
[New Thread 0xab8e4b70 (LWP 7453)]
[New Thread 0xb4a15b70 (LWP 7434)]
[New Thread 0xb5216b70 (LWP 7433)]
0xb78d6424 in __kernel_vsyscall ()

+ Trace 221999

Thread 1 (Thread 0xb5b7aad0 (LWP 7425))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gspawn.c line 386
#3 IA__g_spawn_command_line_sync
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gspawn.c line 700
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
#6 <signal handler called>
#7 ??
from /lib/libdbus-1.so.3
#8 ??
from /lib/libdbus-1.so.3
#9 ??
from /lib/libdbus-1.so.3
#10 dbus_timeout_handle
from /lib/libdbus-1.so.3
#11 ??
from /usr/lib/libgnome-keyring.so.0
#12 g_timeout_dispatch
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 3396
#13 g_main_dispatch
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 1960
#14 IA__g_main_context_dispatch
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 2513
#15 g_main_context_iterate
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 2591
#16 IA__g_main_loop_run
at /build/buildd-glib2.0_2.24.1-1-i386-84Pp4V/glib2.0-2.24.1/glib/gmain.c line 2799
#17 bonobo_main
from /usr/lib/libbonobo-2.so.0
#18 ??
#19 __libc_start_main
from /lib/i686/cmov/libc.so.6
#20 ??

A debugging session is active.

	Inferior 1 [process 7425] will be detached.

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


----------- .xsession-errors (12 sec old) ---------------------
  position 839 271, placed by fvwm (normal placement)
    placement method: MinOverlapPercent
[fvwm][AddWindow]: new window:
  name:      Bug Buddy
  icon name: (unknown)
  resource:  bug-buddy
  class:     Bug-buddy
[fvwm][__explain_placement]: placed new window 0x4800003 'Bug Buddy':
  initial size 514x231
  desk 0 (current desk)
  current page
  screen: current screen: 0 0 1600x1200 (current screen)
  position 548 499  (used program specified position)
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2010-05-20 00:18:47 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 bug 615816 ***