Bug 454426 – crash in Tasks: launch the task

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 454426 - crash in Tasks: launch the task


Summary:	crash in Tasks: launch the task


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-06 23:41 UTC by zakaria731
Modified:	2007-07-07 21:24 UTC

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

Description zakaria731 2007-07-06 23:41:12 UTC

Version: 2.10

What were you doing when the application crashed?
launch the task


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.3228.fc7 #1 SMP Tue Jun 12 14:56:37 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: 457027584 vsize: 457027584 resident: 40005632 share: 30093312 rss: 40005632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183778493 rtime: 96 utime: 79 stime: 17 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 46912496471648 (LWP 3508)]
(no debugging symbols found)
0x000000345560d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 146230

Thread 1 (Thread 46912496471648 (LWP 3508))

#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 ---------------------
  Resource id:  0x220006a
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1401a49
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x3f
CalDAV Eplugin starting up ...
(evolution:3508): e-data-server-DEBUG: Loaded default categories
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  157
  Minor opcode:  6
  Resource id:  0x3f
--------------------------------------------------

Comment 1 palfrey 2007-07-07 21:24:21 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 425129 ***