Bug 402060 – crash in Evolution: trying to create an emai...

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 402060 - crash in Evolution: trying to create an emai...


Summary:	crash in Evolution: trying to create an emai...


Status:	RESOLVED DUPLICATE of bug 352108

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-29 11:53 UTC by thanate
Modified:	2007-02-01 22:29 UTC

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

Description thanate 2007-01-29 11:53:29 UTC

What were you doing when the application crashed?
trying to create an email account


Distribution: Debian 4.0
Gnome Release: 2.17.90 2007-01-28 (GARNOME)
BugBuddy Version: 2.17.3

System: Linux 2.6.19.2 #1 PREEMPT Fri Jan 12 19:13:01 MST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 74317824 vsize: 0 resident: 74317824 share: 0 rss: 28188672 rss_rlim: 0
CPU usage: start_time: 1170071564 rtime: 0 utime: 312 stime: 0 cutime:295 cstime: 0 timeout: 17 it_real_value: 0 frequency: 0

Backtrace was generated from '/home/boat/garnome/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1234139456 (LWP 3797)]
[New Thread -1266644048 (LWP 3806)]
0xb7f58410 in __kernel_vsyscall ()

+ Trace 106254

Thread 1 (Thread -1234139456 (LWP 3797))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 libgnomeui_segv_handle
at gnome-ui-init.c line 872
#3 <signal handler called>
#4 IA__g_logv
at gmessages.c line 503
#5 IA__g_log
at gmessages.c line 517
#6 IA__g_return_if_fail_warning
#7 IA__gtk_file_chooser_set_filename
at gtkfilechooser.c line 514
#8 emae_setup_service
at em-account-editor.c line 1669
#9 emae_receive_page
at em-account-editor.c line 1841
#10 ec_rebuild
at e-config.c line 568
#11 ec_idle_handler_for_rebuild
at e-config.c line 932
#12 g_idle_dispatch
at gmain.c line 3928
#13 IA__g_main_context_dispatch
at gmain.c line 2045
#14 g_main_context_iterate
at gmain.c line 2677
#15 IA__g_main_loop_run
at gmain.c line 2881
#16 IA__gtk_main
at gtkmain.c line 1148
#17 startup_wizard
at startup-wizard.c line 97
#18 epl_invoke
at e-plugin.c line 874
#19 e_plugin_invoke
at e-plugin.c line 663
#20 emph_event_handle
at e-event.c line 407
#21 e_event_emit
at e-event.c line 296
#22 e_shell_attempt_upgrade
at e-shell.c line 906
#23 e_shell_construct
at e-shell.c line 690
#24 e_shell_new
at e-shell.c line 736
#25 idle_cb
at main.c line 350
#26 g_idle_dispatch
at gmain.c line 3928
#27 IA__g_main_context_dispatch
at gmain.c line 2045
#28 g_main_context_iterate
at gmain.c line 2677
#29 IA__g_main_loop_run
at gmain.c line 2881
#30 bonobo_main
at bonobo-main.c line 311
#31 main
at main.c line 614
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Bonobo accessibility support initialized
msn: C: NS 000: PNG
msn: S: NS 000: QNG 44
CalDAV Eplugin starting up ...
** (evolution-2.8:3797): DEBUG: mailto URL command: evolution-2.8
** (evolution-2.8:3797): DEBUG: mailto URL program: evolution-2.8
Gtk-CRITICAL **: gtk_file_chooser_set_filename: assertion `GTK_IS_FILE_CHOOSER (chooser)' failed
aborting...
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------

Comment 1 Karsten Bräckelmann 2007-02-01 22:29:24 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 352108 ***