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 384066 - e-search-bar.c: GTK_IS_CHECK_MENU_ITEM failed
e-search-bar.c: GTK_IS_CHECK_MENU_ITEM failed
Status: RESOLVED DUPLICATE of bug 382860
Product: evolution
Classification: Applications
Component: Mailer
2.10.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-12-09 15:10 UTC by André Klapper
Modified: 2013-09-13 00:51 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description André Klapper 2006-12-09 15:10:26 UTC
evolution 2.9.3 from cvs. perhaps related to bug 382431? *shrug*

(i am missing the small "activated" signs in front of the dropdown menu in the search bar ("subject or sender", "recipients contain" and so on), i currently cannot see which mode is used. perhaps this is related to this crash.)


evo crashes when running with --g-fatal-warnings:

$:andre\> /opt/evo-cvs/bin/evolution-2.10 --g-fatal-warnings
CalDAV Eplugin starting up ...
** (evolution-2.10:4069): DEBUG: mailto URL command: /opt/evo-cvs/bin/evolution-2.10 %s
** (evolution-2.10:4069): DEBUG: mailto URL program: evolution-2.10

Gtk-CRITICAL **: gtk_check_menu_item_set_active: assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed
aborting...

Previous frame inner to this frame (corrupt stack?)

Backtrace was generated from '/opt/gnome/libexec/evolution-2.10'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1235711808 (LWP 4069)]
[New Thread -1584329824 (LWP 4075)]
[New Thread -1417573472 (LWP 4073)]
[New Thread -1409180768 (LWP 4072)]
[New Thread -1400788064 (LWP 4071)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1235711808 (LWP 4069))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 IA__g_logv
    at gmessages.c line 493
  • #5 IA__g_log
    at gmessages.c line 517
  • #6 IA__g_return_if_fail_warning
  • #7 IA__gtk_check_menu_item_set_active
    at gtkcheckmenuitem.c line 193
  • #8 e_search_bar_set_item_menu
    at e-search-bar.c line 1381
  • #9 set_property
    at e-filter-bar.c line 752
  • #10 object_set_property
    at gobject.c line 697
  • #11 IA__g_object_set_valist
    at gobject.c line 1125
  • #12 IA__g_object_set
    at gobject.c line 1207
  • #13 emfb_set_folder
    at em-folder-browser.c line 1888
  • #14 emfv_got_folder
    at em-folder-view.c line 691
  • #15 get_folder_got
    at mail-ops.c line 1230
  • #16 mail_msgport_replied
    at mail-mt.c line 473
  • #17 g_io_unix_dispatch
    at giounix.c line 162
  • #18 g_main_dispatch
    at gmain.c line 2049
  • #19 IA__g_main_context_dispatch
    at gmain.c line 2600
  • #20 g_main_context_iterate
    at gmain.c line 2681
  • #21 IA__g_main_loop_run
    at gmain.c line 2885
  • #22 bonobo_main
    at bonobo-main.c line 311
  • #23 main
    at main.c line 617
  • #0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-12-20 18:53:15 UTC
I believe this is bug 382860.


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