Bug 475310 – crash in Evolution: 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 475310 - crash in Evolution: first start


Summary:	crash in Evolution: first start


Status:	RESOLVED DUPLICATE of bug 425129

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-09-10 01:08 UTC by vlasov
Modified:	2007-09-10 11:21 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description vlasov 2007-09-10 01:08:29 UTC

What were you doing when the application crashed?
first start


Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 466640896 vsize: 466640896 resident: 10919936 share: 17297408 rss: 28217344 rss_rlim: -773067776
CPU usage: start_time: 1189386504 rtime: 65 utime: 60 stime: 5 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/evolution-2.8'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47686101302448 (LWP 4949)]
(no debugging symbols found)
0x00002b5ec6ab6c5f in waitpid () from /lib64/libpthread.so.0

+ Trace 161667

Thread 1 (Thread 47686101302448 (LWP 4949))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 strcmp
from /lib64/libc.so.6
#4 icaltimezone_get_builtin_timezone_from_offset
from /opt/gnome/lib64/libecal-1.2.so.7
#5 e_timezone_dialog_set_timezone
from /opt/gnome/lib64/evolution/2.8/libetimezonedialog.so.0
#6 startup_wizard_timezone_page
from /opt/gnome/lib64/evolution/2.8/plugins/liborg-gnome-evolution-startup-wizard.so
#7 e_plugin_hook_register_type
from /opt/gnome/lib64/evolution/2.8/libeutil.so.0
#8 e_config_page_check
from /opt/gnome/lib64/evolution/2.8/libeutil.so.0
#9 e_config_target_changed
from /opt/gnome/lib64/evolution/2.8/libeutil.so.0
#10 e_config_create_widget
from /opt/gnome/lib64/evolution/2.8/libeutil.so.0
#11 e_config_create_window
from /opt/gnome/lib64/evolution/2.8/libeutil.so.0
#12 em_account_editor_new
from /opt/gnome/lib64/evolution/2.8/components/libevolution-mail.so
#13 startup_wizard
from /opt/gnome/lib64/evolution/2.8/plugins/liborg-gnome-evolution-startup-wizard.so
#14 e_plugin_hook_register_type
from /opt/gnome/lib64/evolution/2.8/libeutil.so.0
#15 e_event_emit
from /opt/gnome/lib64/evolution/2.8/libeutil.so.0
#16 e_shell_attempt_upgrade
#17 e_shell_construct
#18 e_shell_new
#19 main
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 André Klapper 2007-09-10 11:21:18 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 ***