Bug 459096 – crash in Tasks: Editing the preferences....

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 459096 - crash in Tasks: Editing the preferences....


Summary:	crash in Tasks: Editing the preferences....


Status:	RESOLVED DUPLICATE of bug 456653

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-21 20:09 UTC by win32pro
Modified:	2007-07-22 09:54 UTC

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

Description win32pro 2007-07-21 20:09:40 UTC

Version: 2.10

What were you doing when the application crashed?
Editing the preferences. Happens not the first time
Fedora 7, latest updates x86 (P4), 2GB RAM, radeon driver with Compiz (desktop effects enabled)


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaCappuccino
Icon Theme: nuoveXT-1.6

Memory status: size: 116957184 vsize: 116957184 resident: 46366720 share: 32202752 rss: 46366720 rss_rlim: 4294967295
CPU usage: start_time: 1185048295 rtime: 708 utime: 631 stime: 77 cutime:1 cstime: 4 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 -1209116960 (LWP 3772)]
[New Thread -1254454384 (LWP 3841)]
[New Thread -1221071984 (LWP 3840)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 149660

Thread 1 (Thread -1209116960 (LWP 3772))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 ??
from /lib/libglib-2.0.so.0
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 g_slice_free_chain_with_offset
from /lib/libglib-2.0.so.0
#9 g_slist_free
from /lib/libglib-2.0.so.0
#10 ??
from /usr/lib/libbonoboui-2.so.0
#11 ??
from /lib/libglib-2.0.so.0
#12 bonobo_ui_engine_dispose
from /usr/lib/libbonoboui-2.so.0
#13 ??
from /usr/lib/libbonoboui-2.so.0
#14 ??
#15 g_object_run_dispose
from /lib/libgobject-2.0.so.0
#16 gtk_object_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#17 gtk_widget_destroy
from /usr/lib/libgtk-x11-2.0.so.0
#18 e_shell_close_all_windows
#19 ??
#20 ??
from /lib/libglib-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 ??
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /lib/libglib-2.0.so.0
#24 bonobo_main
from /usr/lib/libbonobo-2.so.0
#25 main
#0 __kernel_vsyscall



----------- .xsession-errors (17 sec old) ---------------------
(evolution:3772): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.10/plugins/liborg-gnome-new-mail-notify.so' (not exported?)
BBDB spinning up...
(evolution:3772): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x98ae488'
(evolution:3772): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x98ae248'
(evolution:3772): e-dateedit.c-WARNING **: time_text:09:00
(evolution:3772): e-dateedit.c-WARNING **: time_text:09:00
(evolution:3772): e-dateedit.c-WARNING **: time_text:17:00
(evolution:3772): e-dateedit.c-WARNING **: time_text:17:00
--------------------------------------------------

Comment 1 palfrey 2007-07-22 09:54:05 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 456653 ***