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 331871 - crash in e_canvas_item_grab_focus at e-canvas.c:580
crash in e_canvas_item_grab_focus at e-canvas.c:580
Status: RESOLVED DUPLICATE of bug 327035
Product: evolution
Classification: Applications
Component: Mailer
2.6.x
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-02-20 07:43 UTC by Diego González
Modified: 2013-09-13 01:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Diego González 2006-02-20 07:43:51 UTC 
on the console i get this message: 

e-canvas.c-CRITICAL **: e_canvas_item_grab_focus: assertion `GTK_WIDGET_CAN_FOCUS (GTK_WIDGET (item->canvas))' failed
aborting...

note that the new gnome policy (aborting in every critical warning) might be making the application crash.

the backtrace is:

+ Trace 66346

  • #0 __kernel_vsyscall
  • #1 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #2 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #3 IA__g_logv
    at gmessages.c line 497
  • #4 IA__g_log
    at gmessages.c line 517
  • #5 IA__g_return_if_fail_warning
  • #6 e_canvas_item_grab_focus
    at e-canvas.c line 580
  • #7 ethi_event
    at e-table-header-item.c line 1681
  • #8 gnome_canvas_marshal_BOOLEAN__BOXED
    at gnome-canvas-marshal.c line 125
  • #9 g_type_class_meta_marshal
    at gclosure.c line 567
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #13 IA__g_signal_emit_by_name
    at gsignal.c line 2265
  • #14 emit_event
    at e-canvas.c line 264
  • #15 e_canvas_button
    at e-canvas.c line 528
  • #16 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #17 g_type_class_meta_marshal
    at gclosure.c line 567
  • #18 IA__g_closure_invoke
    at gclosure.c line 490
  • #19 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #20 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #21 IA__g_signal_emit
    at gsignal.c line 2241
  • #22 gtk_widget_event_internal
    at gtkwidget.c line 3751
  • #23 IA__gtk_widget_event
    at gtkwidget.c line 3557
  • #24 IA__gtk_propagate_event
    at gtkmain.c line 2166
  • #25 IA__gtk_main_do_event
    at gtkmain.c line 1395
  • #26 gdk_event_dispatch
    at gdkevents-x11.c line 2311
  • #27 g_main_dispatch
    at gmain.c line 1916
  • #28 IA__g_main_context_dispatch
    at gmain.c line 2466
  • #29 g_main_context_iterate
    at gmain.c line 2547
  • #30 IA__g_main_loop_run
    at gmain.c line 2751
  • #31 bonobo_main
    from /opt/gnome2/lib/libbonobo-2.so.0 






Comment 1


André Klapper





          2006-02-20 16:40:21 UTC
        



looks related to bug 327035






Comment 2


Stanislav Brabec





          2006-03-15 14:27:52 UTC
        



GNOME 2.12 (critical warning crash disabled), SuSE Linux 10.1 beta 7 AMD64 evolution-2.5.92-6, evolution-data-server-1.5.92-5. Crash probably in the action, but with different backtrace.

Click to unread mail header in the mail summary.

Backtrace was generated from '/opt/gnome/bin/evolution-2.6'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47928774827232 (LWP 14214)]
[New Thread 1166858576 (LWP 31131)]
[New Thread 1166592336 (LWP 31130)]
[New Thread 1157933392 (LWP 14305)]
[New Thread 1157667152 (LWP 14304)]
[New Thread 1149274448 (LWP 14278)]
[New Thread 1140881744 (LWP 14277)]
[New Thread 1132489040 (LWP 14263)]
[New Thread 1098918224 (LWP 14262)]
[New Thread 1107310928 (LWP 14261)]
[New Thread 1124096336 (LWP 14258)]
[New Thread 1115703632 (LWP 14257)]
[New Thread 1090525520 (LWP 14254)]
[New Thread 1082132816 (LWP 14251)]
0x00002b97466f4bbf in __libc_waitpid (pid=12451, stat_loc=0x7fff6893da6c, 
    options=0) at waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);




+
Trace
    66959






Thread 1
          (Thread 47928774827232 (LWP 14214))


    

  • 
#0
__libc_waitpid

    
                at waitpid.c
                  line
                  41

    

    • 

  • 
#1
libgnomeui_segv_handle

    
                at gnome-ui-init.c
                  line
                  749

    

    • 

  • 
#2
<signal handler called>

    • 

  • 
#3
*__GI___poll

    
                at poll.c
                  line
                  87

    

    • 

  • 
#4
g_main_context_iterate

    
                at gmain.c
                  line
                  2867

    

    • 

  • 
#5
g_main_loop_run

    
                at gmain.c
                  line
                  2769

    

    • 

  • 
#6
bonobo_main

    
                at bonobo-main.c
                  line
                  394

    

    • 

  • 
#7
main

    
                at main.c
                  line
                  610

    

    • 













Comment 3


Lucky Wankhede





          2007-08-17 06:57:19 UTC
        



I think both the stack traces look different to me, having no relation.

pardon me if I am wrong.. 

Any steps to reproduce the crash.. 






Comment 4


Stanislav Brabec





          2007-08-20 12:16:11 UTC
        



It seems that I pasted my stacktrace to a bad bug. My one is probably already fixed, so please ignore my backtrace.






Comment 5


Priit Laes (IRC: plaes)





          2007-09-06 16:50:52 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 327035 ***