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 595811 - crash in Evolution Mail and Calendar: attempting to preview a new message
crash in Evolution Mail and Calendar: attempting to preview a new message
Status: RESOLVED DUPLICATE of bug 594543
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.30.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-09-21 08:53 UTC by Yanko Kaneti
Modified: 2013-09-13 01:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Yanko Kaneti 2009-09-21 08:53:18 UTC
Version: 2.28.x

What were you doing when the application crashed?
Evolution has just started with an open imap folder, displaying the mesage list. and an empty preview pane. Two new messages , clicked on one of them, which would usually show it in the preview pane. Crash.


Distribution: Fedora release 11.91 (Rawhide)
Gnome Release: 2.27.92 2009-09-09 (Red Hat, Inc)
BugBuddy Version: 2.27.92

System: Linux 2.6.31-23.fc12.x86_64 #1 SMP Wed Sep 16 15:54:05 EDT 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10699901
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango
GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad

Memory status: size: 2136190976 vsize: 2136190976 resident: 1050681344 share: 25210880 rss: 1050681344 rss_rlim: 18446744073709551615
CPU usage: start_time: 1253522944 rtime: 8820 utime: 7145 stime: 1675 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f673abfd710 (LWP 28887)]
[New Thread 0x7f673b5fe710 (LWP 28886)]
[New Thread 0x7f673bfff710 (LWP 28885)]
[New Thread 0x7f6740fd1710 (LWP 28884)]
0x00007f6757f25ebd in __libc_waitpid (pid=28964, stat_loc=<value optimized out>, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 1 (Thread 0x7f675c7dd800 (LWP 28881))

  • #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 409
  • #4 check_if_gdb
    at gnome-breakpad.cc line 480
  • #5 bugbuddy_segv_handle
    at gnome-breakpad.cc line 223
  • #6 <signal handler called>
  • #7 IA__g_object_ref
    at gobject.c line 2339
  • #8 gal_view_etable_attach_tree
    at gal-view-etable.c line 289
  • #9 mail_shell_view_reader_changed_cb
    at e-mail-shell-view-private.c line 214
  • #10 IA__g_closure_invoke
    at gclosure.c line 767
  • #11 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #13 IA__g_signal_emit
    at gsignal.c line 3037
  • #14 IA__g_closure_invoke
    at gclosure.c line 767
  • #15 signal_emit_unlocked_R
    at gsignal.c line 3247
  • #16 IA__g_signal_emit_valist
    at gsignal.c line 2980
  • #17 IA__g_signal_emit
    at gsignal.c line 3037
  • #18 on_cursor_activated_idle
    at message-list.c line 3506
  • #19 g_main_dispatch
    at gmain.c line 1960
  • #20 IA__g_main_context_dispatch
    at gmain.c line 2513
  • #21 g_main_context_iterate
    at gmain.c line 2591
  • #22 IA__g_main_loop_run
    at gmain.c line 2799
  • #23 IA__gtk_main
    at gtkmain.c line 1205
  • #24 main
    at main.c line 625

	Inferior 1 [process 28881] will be detached.

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


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

** GLib-GObject **: g_signal_handler_disconnect: assertion `handler_id > 0' failed 
** GLib-GObject **: g_signal_handler_disconnect: assertion `handler_id > 0' failed 
** GLib-GObject **: g_signal_handler_disconnect: assertion `handler_id > 0' failed 


----------- .xsession-errors (157 sec old) ---------------------
warning: the debug information found in "/usr/lib/debug//usr/lib64/libtdb.so.1.1.5.debug" does not match "/usr/lib64/libtdb.so.1" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib64/libtdb.so.1.1.5.debug" does not match "/usr/lib64/libtdb.so.1" (CRC mismatch).
Missing separate debuginfo for /usr/lib64/libtdb.so.1
Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/34/fafaa8007ee23182c82ffdb451a09372dafb38.debug
warning: the debug information found in "/usr/lib/debug//usr/lib64/libstdc++.so.6.0.13.debug" does not match "/usr/lib64/libstdc++.so.6" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug/usr/lib64/libstdc++.so.6.0.13.debug" does not match "/usr/lib64/libstdc++.so.6" (CRC mismatch).
(galeon:8838): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Yanko Kaneti 2009-09-21 08:58:26 UTC
I haven't had any such crashes in the 2.28 branch. So I'll assume its the new work in trunk thats the culprit.
Comment 2 Yanko Kaneti 2009-09-21 09:04:29 UTC
It doesn't seem related to the particular message I was trying to preview.
While it also crashed the second time, the third time the message opened as
expected. So no really a way to reliably reproduce for me yet.
Comment 3 Akhil Laddha 2009-09-22 04:29:47 UTC
could be a dupe of bug 594543
Comment 4 Milan Crha 2009-09-22 08:48:45 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 594543 ***