Bug 453793 – crash in Email: first start

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 453793 - crash in Email: first start


Summary:	crash in Email: first start


Status:	RESOLVED DUPLICATE of bug 425129

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-07-04 20:56 UTC by s.osetrov
Modified:	2007-07-11 18:40 UTC

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

Description s.osetrov 2007-07-04 20:56:29 UTC

What were you doing when the application crashed?
first start


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: 94826496 vsize: 94826496 resident: 23171072 share: 14749696 rss: 23171072 rss_rlim: 4294967295
CPU usage: start_time: 1183582448 rtime: 254 utime: 199 stime: 55 cutime:1 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209018656 (LWP 2972)]
(no debugging symbols found)
0x00ab6402 in __kernel_vsyscall ()

+ Trace 145773

Thread 1 (Thread -1209018656 (LWP 2972))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 strcmp
from /lib/libc.so.6
#6 icaltimezone_get_builtin_timezone_from_offset
from /usr/lib/libecal-1.2.so.7
#7 e_timezone_dialog_set_timezone
from /usr/lib/evolution/2.10/libetimezonedialog.so.0
#8 startup_wizard_timezone_page
from /usr/lib/evolution/2.10/plugins/liborg-gnome-evolution-startup-wizard.so
#9 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#10 e_plugin_invoke
from /usr/lib/evolution/2.10/libeutil.so.0
#11 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#12 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#13 e_config_create_widget
from /usr/lib/evolution/2.10/libeutil.so.0
#14 e_config_create_window
from /usr/lib/evolution/2.10/libeutil.so.0
#15 em_account_editor_new
from /usr/lib/evolution/2.10/components/libevolution-mail.so
#16 startup_wizard
from /usr/lib/evolution/2.10/plugins/liborg-gnome-evolution-startup-wizard.so
#17 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#18 e_plugin_invoke
from /usr/lib/evolution/2.10/libeutil.so.0
#19 ??
from /usr/lib/evolution/2.10/libeutil.so.0
#20 e_event_emit
from /usr/lib/evolution/2.10/libeutil.so.0
#21 e_shell_attempt_upgrade
#22 e_shell_construct
#23 e_shell_new
#24 ??
#25 ??
from /lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 ??
from /lib/libglib-2.0.so.0
#28 g_main_loop_run
from /lib/libglib-2.0.so.0
#29 bonobo_main
from /usr/lib/libbonobo-2.so.0
#30 main
#0 __kernel_vsyscall



----------- .xsession-errors (51 sec old) ---------------------
localuser:tat3 being added to access control list
SESSION_MANAGER=local/tat-f7:/tmp/.ICE-unix/2477
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
CalDAV Eplugin starting up ...
(evolution:2972): e-data-server-DEBUG: Loaded default categories
** (evolution:2972): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:2972): DEBUG: mailto URL program: evolution
--------------------------------------------------

Comment 1 André Klapper 2007-07-11 18:40:05 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 425129 ***