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 119783 - Error message appearing in log file, no obvious reason found
Error message appearing in log file, no obvious reason found
Status: RESOLVED FIXED
Product: Pan
Classification: Other
Component: general
pre-0.14.1 betas
Other Linux
: Normal normal
: 0.14.1
Assigned To: Charles Kerr
Pan QA Team
Depends on:
Blocks:
 
 
Reported: 2003-08-13 11:56 UTC by Brian Morrison
Modified: 2006-06-18 05:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Brian Morrison 2003-08-13 11:56:17 UTC 
The following message is appearing in the log window quite frequently, but
there is no obvious reason why nor any effect that is apparent to me.

Gtk - file gtktogglebutton.c: line 325 (gtk_toggle_button_get_active): 
assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed

Please advise if it is an important error or not:
Comment 1 Charles Kerr 2003-08-13 15:33:23 UTC 
Yes, this is important.

(1) When does it appear?

(2) Please run pan inside of gdb and, before starting Pan,
    set a breakpoint for log_error_breakpoint:

      (gdb) break log_error_breakpoint
      breakpoint 1 set at pan.c:log_error_breakpoint
      (gdb) run

    and, once the breakpoint's reached, get a backtrace:

      breakpoint 1 reached at pan.c:log_error_breakpoint
      (gdb) bt
Comment 2 Brian Morrison 2003-08-14 08:12:18 UTC 
OK, what happens is that it appears randomly any time I click on a
group to load headers. Not 100%, not always the first group, not every
time I load a group.

This time it happened on the first group, so the backtrace is:

Breakpoint 1, log_error_breakpoint () at pan.c:145
145     }
(gdb) bt

+ Trace 39578

  • #0 log_error_breakpoint
    at pan.c line 145
  • #1 my_log_handler
  • #2 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #3 g_log
    from /usr/lib/libglib-2.0.so.0
  • #4 gtk_toggle_button_get_active
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 show_only_text_ckm_cb
    at filter-mediator.c line 281
  • #6 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 gtk_check_menu_item_toggled
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 gtk_check_menu_item_get_inconsistent
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #19 gtk_menu_item_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 gtk_check_menu_item_set_active
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 refresh
    at filter-mediator.c line 119
  • #22 refresh_idle
    at filter-mediator.c line 189
  • #23 gui_queue_timer_cb
    at util.c line 225
  • #24 pan_timeout_wrapper
    at util.c line 166
  • #25 g_main_context_wakeup
    from /usr/lib/libglib-2.0.so.0
  • #26 unblock_source
    from /usr/lib/libglib-2.0.so.0
  • #27 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #30 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 main
    at pan.c line 341
  • #32 __libc_start_main
    from /lib/libc.so.6 

I hope that is enough for you to work out what is happening.