Bug 483586 – crash in Tasks: I was forwarding a e-mai...

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 483586 - crash in Tasks: I was forwarding a e-mai...


Summary:	crash in Tasks: I was forwarding a e-mai...


Status:	RESOLVED DUPLICATE of bug 410823

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	evolution-calendar-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-05 04:04 UTC by Rob Robason
Modified:	2007-10-05 14:05 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Rob Robason 2007-10-05 04:04:12 UTC

What were you doing when the application crashed?
I was forwarding a e-mail I got to a friend


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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 181686272 vsize: 181686272 resident: 47837184 share: 19398656 rss: 47837184 rss_rlim: 4294967295
CPU usage: start_time: 1191504128 rtime: 2444 utime: 2281 stime: 163 cutime:48 cstime: 14 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 -1208658208 (LWP 10272)]
[New Thread -1286829168 (LWP 10535)]
[New Thread -1258325104 (LWP 10384)]
[New Thread -1270875248 (LWP 10347)]
[New Thread -1247442032 (LWP 10341)]
[New Thread -1226462320 (LWP 10337)]
0x003cf402 in __kernel_vsyscall ()

+ Trace 167883

Thread 1 (Thread -1208658208 (LWP 10272))

#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 (28 sec old) ---------------------
** (evolution:10272): DEBUG: mailto URL program: evolution
(evolution:10272): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
(evolution:10272): e-data-server-DEBUG: Loading categories from "/home/lynn/.evolution/categories.xml"
(evolution:10272): e-data-server-DEBUG: Loaded 29 categories
(evolution:10272): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEntry'
(evolution:10272): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed
(evolution:10272): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GtkEditable'
(evolution:10272): Gtk-CRITICAL **: gtk_editable_get_position: assertion `GTK_IS_EDITABLE (editable)' failed
(evolution:10272): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
--------------------------------------------------

Comment 1 palfrey 2007-10-05 14:05:55 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 ***