Bug 453691 – crash in Tasks: just installed f7 just t...

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 453691 - crash in Tasks: just installed f7 just t...


Summary:	crash in Tasks: just installed f7 just t...


Status:	RESOLVED DUPLICATE of bug 425129

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-07-04 13:55 UTC by michon
Modified:	2007-07-11 18:40 UTC

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

Description michon 2007-07-04 13:55:07 UTC

What were you doing when the application crashed?
just installed f7
just tried to launch Application->Internet->Email
but started bug reporting tool instead


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:47:07 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 486400000 vsize: 486400000 resident: 24289280 share: 14278656 rss: 24289280 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183557114 rtime: 75 utime: 68 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 46912496356960 (LWP 3226)]
(no debugging symbols found)
0x0000003ee940d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 145699

Thread 1 (Thread 46912496356960 (LWP 3226))

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



----------- .xsession-errors ---------------------
CalDAV Eplugin starting up ...
** (evolution:3070): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3070): DEBUG: mailto URL program: evolution
--- Hash table keys for warning below:
--> file:///root
(nautilus:3100): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
closing
closing
closing
Loading "installonlyn" plugin
CalDAV Eplugin starting up ...
** (evolution:3226): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:3226): DEBUG: mailto URL program: evolution
--------------------------------------------------

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