Bug 445670 – crash in Tasks: I just clicked on the e-...

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 445670 - crash in Tasks: I just clicked on the e-...


Summary:	crash in Tasks: I just clicked on the e-...


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-06-09 03:28 UTC by itdreams
Modified:	2007-06-12 00:56 UTC

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

Description itdreams 2007-06-09 03:28:18 UTC

What were you doing when the application crashed?
I just clicked on the e-mail link in Firefox.


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: No
Accessibility: Disabled
GTK+ Theme: MacOS-X
Icon Theme: AquiGnome

Memory status: size: 488267776 vsize: 488267776 resident: 24285184 share: 14422016 rss: 24285184 rss_rlim: 18446744073709551615
CPU usage: start_time: 1181359287 rtime: 56 utime: 45 stime: 11 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 46912496361056 (LWP 3255)]
(no debugging symbols found)
0x000000374240d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 139501

Thread 1 (Thread 46912496361056 (LWP 3255))

#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 (970 sec old) ---------------------
localuser:master being added to access control list
SESSION_MANAGER=local/QWERTY1:/tmp/.ICE-unix/2598
** Message: failed to load session from /home/master/.nautilus/saved-session-633ATT
winscard_clnt.c:3349:SCardCheckDaemonAvailability() PCSC Not Running
Loading "installonlyn" plugin
Loading "installonlyn" plugin
--------------------------------------------------

Comment 1 André Klapper 2007-06-12 00:56:37 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 ***