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 521697 - crash in Tasks: forwarding a e-mail
crash in Tasks: forwarding a e-mail
Status: RESOLVED DUPLICATE of bug 410823
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-03-11 00:51 UTC by Rob Robason
Modified: 2008-03-17 09:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Rob Robason 2008-03-11 00:51:17 UTC
What were you doing when the application crashed?
forwarding a e-mail


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 333242368 vsize: 333242368 resident: 192995328 share: 19443712 rss: 192995328 rss_rlim: 4294967295
CPU usage: start_time: 1204926127 rtime: 117433 utime: 106563 stime: 10870 cutime:3115 cstime: 352 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 -1208322336 (LWP 24251)]
[New Thread -1336579184 (LWP 24833)]
[New Thread -1275204720 (LWP 24300)]
[New Thread -1296184432 (LWP 24266)]
[New Thread -1226183792 (LWP 24256)]
0x008be402 in __kernel_vsyscall ()

Thread 1 (Thread -1208322336 (LWP 24251))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 segv_redirect
    at main.c line 408
  • #4 <signal handler called>
  • #5 get_range_at_position
    at e-name-selector-entry.c line 244
  • #6 update_completions_on_idle_cb
    at e-name-selector-entry.c line 856
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #11 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #12 main
    at main.c line 586
  • #0 __kernel_vsyscall


----------- .xsession-errors (26 sec old) ---------------------
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (check_midnight_refresh)
alarm-queue.c:1834 (c(evolution:24251): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:24251): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:24251): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEntry'
(evolution:24251): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed
(evolution:24251): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEditable'
(evolution:24251): Gtk-CRITICAL **: gtk_editable_get_position: assertion `GTK_IS_EDITABLE (editable)' failed
(evolution:24251): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------
Comment 1 Kandepu Prasad 2008-03-15 20:48:54 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 410823 ***
Comment 2 Rob Robason 2008-03-16 17:31:04 UTC
This error seems to occur consistently when replying to messages from a sender with non-ascii characters in the email address. After the crash, the message appears in the Outbox folder, and can be successfully sent with Send/Recieve.

The To: line that causes the problem is "Hårlê¥ßê¢k <login_name@sbcglobal.net>" (login name sanitized for privacy).

I hope this is the bug you fixed.