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 611108 - crash in Evolution: Wanted to view message h...
crash in Evolution: Wanted to view message h...
Status: RESOLVED DUPLICATE of bug 600013
Product: evolution
Classification: Applications
Component: BugBuddyBugs
1.5.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-02-25 18:26 UTC by Priit Laes (IRC: plaes)
Modified: 2010-02-26 03:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Priit Laes (IRC: plaes) 2010-02-25 18:26:58 UTC
Version: 2.30.x

What were you doing when the application crashed?
Wanted to view message headers (or was it source) but closed the window before the message was loaded.


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.28.2 2009-12-18 (Gentoo)
BugBuddy Version: 2.28.0

System: Linux 2.6.33-rc8 #189 SMP Sun Feb 14 23:51:52 EET 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10705000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks Compact
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 910303232 vsize: 910303232 resident: 110891008 share: 31457280 rss: 110891008 rss_rlim: 18446744073709551615
CPU usage: start_time: 1267121102 rtime: 5437 utime: 5081 stime: 356 cutime:15 cstime: 24 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f9933377710 (LWP 30471)]
[New Thread 0x7f9936d4c710 (LWP 30269)]
[New Thread 0x7f993754d710 (LWP 30268)]
[New Thread 0x7f993e7fc710 (LWP 30259)]
[New Thread 0x7f993effd710 (LWP 30258)]
[New Thread 0x7f993f7fe710 (LWP 30257)]
[New Thread 0x7f994490c710 (LWP 30254)]
[New Thread 0x7f994590e710 (LWP 30252)]
[New Thread 0x7f994610f710 (LWP 30251)]
[New Thread 0x7f9946b3a710 (LWP 30250)]
[New Thread 0x7f994733b710 (LWP 30249)]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.4-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
0x00007f995d3f6bcd in __libc_waitpid (pid=30485, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

Thread 1 (Thread 0x7f995f2dd760 (LWP 30245))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at gspawn.c line 386
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 700
  • #3 run_bug_buddy
    at gnome-breakpad.cc line 369
  • #4 check_if_gdb
    at gnome-breakpad.cc line 440
  • #5 bugbuddy_segv_handle
    at gnome-breakpad.cc line 223
  • #6 <signal handler called>
  • #7 mail_reader_message_loaded_cb
    at e-mail-reader.c line 1783
  • #8 mail_msg_idle_cb
    at mail-mt.c line 453
  • #9 g_main_dispatch
    at gmain.c line 1960
  • #10 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #11 g_main_context_iterate
    at gmain.c line 2591
  • #12 IA__g_main_loop_run
    at gmain.c line 2799
  • #13 IA__gtk_main
    at gtkmain.c line 1219

	Inferior 1 [process 30245] will be detached.

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


---- Critical and fatal warnings logged during execution ----

** e-utils **: e_plugin_invoke: assertion `ep->enabled' failed 
** evolution-shell **: e_shell_backend_get_shell: assertion `E_IS_SHELL_BACKEND (shell_backend)' failed 
** evolution-shell **: e_shell_get_shell_settings: assertion `E_IS_SHELL (shell)' failed
Comment 1 Akhil Laddha 2010-02-26 03:31:02 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 bug 600013 ***