GNOME Bugzilla – Bug 444575
crash in get_range_at_position at e-name-selector-entry.c:244
Last modified: 2007-07-02 00:11:41 UTC
What were you doing when the application crashed? just tried to send an email - but evolution crashes all the time anyway so probably there is some more general problem. hope the "crash details" help... Thank you for your efforts! Distribution: Debian lenny/sid Gnome Release: 2.18.2 2007-05-28 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21.1-dietrich-vanilla-realtime #1 SMP PREEMPT Mon May 14 10:22:43 JST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 179601408 vsize: 179601408 resident: 52555776 share: 21938176 rss: 52555776 rss_rlim: 4294967295 CPU usage: start_time: 1181098549 rtime: 5018 utime: 4631 stime: 387 cutime:0 cstime: 0 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 -1233344832 (LWP 28738)] [New Thread -1317872752 (LWP 30424)] [New Thread -1352053872 (LWP 29594)] [New Thread -1282409584 (LWP 28803)] [New Thread -1248867440 (LWP 28801)] [New Thread -1278542960 (LWP 28785)] [New Thread -1269216368 (LWP 28764)] [New Thread -1257256048 (LWP 28763)] [New Thread -1240441968 (LWP 28759)] 0xb77e2b11 in ?? () from /lib/libpthread.so.0
+ Trace 138639
Thread 1 (Thread -1233344832 (LWP 28738))
----------- .xsession-errors (54 sec old) --------------------- Could not connect to smtp.web.de: No route to host (evolution:28738): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?) (evolution:28738): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:28738): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution:28738): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkEntry' (evolution:28738): Gtk-CRITICAL **: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed (evolution:28738): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkEditable' (evolution:28738): Gtk-CRITICAL **: gtk_editable_get_position: assertion `GTK_IS_EDITABLE (editable)' failed --------------------------------------------------
Hi - I naively just followed the indications on the "Bug Buddy" - and voila - all kind of personal information on the bug tracker :( Could you please delete this bug report? How about writing some filter which erases personal information from the reports? How do I configure the bug tool to not publish my email? I wonder that there are still services which do this anyway!
Thanks for taking the time to report this bug. (In reply to comment #1) > Hi - I naively just followed the indications on the "Bug Buddy" - and voila - > all kind of personal information on the bug tracker :( can you be more specific? if you refer to the trace itself: Bug Buddy clearly states that you should review the debug information and make sure that no confidential data is included. i can only see your mail server and your username, nothing else. > Could you please delete this bug report? > How about writing some filter which erases personal information from the > reports? willing to come up with a patch? i really wonder how to automatically identify such things... > How do I configure the bug tool to not publish my email? your email address is only visible after logging in to bugzilla, and you can even change this to a real name in the preferences. So I don't see too much personal information here. Regarding the stack trace itself: Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols also for glib and gtk? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug. Thanks in advance!
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 ***