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 475315 - crash in Tasks: Deleted an e-mail addres...
crash in Tasks: Deleted an e-mail addres...
Status: RESOLVED DUPLICATE of bug 458670
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-09-10 01:38 UTC by bert.rolston
Modified: 2007-10-23 11:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description bert.rolston 2007-09-10 01:38:26 UTC
Version: 2.10

What were you doing when the application crashed?
Deleted an e-mail address in the CC: field and clicked on the BCC: field when my friend Bug Buddy appeared.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: OSX

Memory status: size: 385048576 vsize: 385048576 resident: 133754880 share: 96759808 rss: 133754880 rss_rlim: 4294967295
CPU usage: start_time: 1189368649 rtime: 27204 utime: 24411 stime: 2793 cutime:3 cstime: 10 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208928544 (LWP 3394)]
[New Thread -1295774832 (LWP 8806)]
[New Thread -1349112944 (LWP 3439)]
[New Thread -1325761648 (LWP 3436)]
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208928544 (LWP 3394))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 IA__g_utf8_offset_to_pointer
    at gutf8.c line 302
  • #6 get_entry_substring
    at e-name-selector-entry.c line 520
  • #7 entry_activate
    at e-name-selector-entry.c line 1402
  • #8 user_focus_out
    at e-name-selector-entry.c line 1464
  • #9 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #13 IA__g_signal_emit
    at gsignal.c line 2243
  • #14 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #15 do_focus_change
    at gtkwindow.c line 4782
  • #16 gtk_window_real_set_focus
    at gtkwindow.c line 4984
  • #17 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #18 g_type_class_meta_marshal
    at gclosure.c line 567
  • #19 IA__g_closure_invoke
    at gclosure.c line 490
  • #20 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #21 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #22 IA__g_signal_emit
    at gsignal.c line 2243
  • #23 _gtk_window_internal_set_focus
    at gtkwindow.c line 1274
  • #24 gtk_widget_real_grab_focus
    at gtkwidget.c line 4301
  • #25 gtk_entry_grab_focus
    at gtkentry.c line 2128
  • #26 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #27 g_type_class_meta_marshal
    at gclosure.c line 567
  • #28 IA__g_closure_invoke
    at gclosure.c line 490
  • #29 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #30 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #31 IA__g_signal_emit
    at gsignal.c line 2243
  • #32 IA__gtk_widget_grab_focus
    at gtkwidget.c line 4220
  • #33 gtk_entry_button_press
    at gtkentry.c line 1668
  • #34 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #35 g_type_class_meta_marshal
    at gclosure.c line 567
  • #36 IA__g_closure_invoke
    at gclosure.c line 490
  • #37 signal_emit_unlocked_R
    at gsignal.c line 2478
  • #38 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #39 IA__g_signal_emit
    at gsignal.c line 2243
  • #40 gtk_widget_event_internal
    at gtkwidget.c line 3915
  • #41 IA__gtk_propagate_event
    at gtkmain.c line 2341
  • #42 IA__gtk_main_do_event
    at gtkmain.c line 1575
  • #43 gdk_event_dispatch
    at gdkevents-x11.c line 2318
  • #44 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #45 g_main_context_iterate
    at gmain.c line 2677
  • #46 IA__g_main_loop_run
    at gmain.c line 2881
  • #47 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #48 main
    at main.c line 586
  • #0 __kernel_vsyscall


----------- .xsession-errors (17 sec old) ---------------------
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/lib/libssl.so.6" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libkrb5support.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libldap-2.3.so.0" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
beryl: water: GL_ARB_fragment_program is missing
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-15 17:57:26 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 2 André Klapper 2007-10-23 11:26:16 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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