Bug 456132 – crash in Tasks:

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 456132 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 453932

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-12 05:00 UTC by manish.k
Modified:	2007-07-12 11:18 UTC

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

Description manish.k 2007-07-12 05:00:51 UTC

Version: 2.10

What were you doing when the application crashed?



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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 112963584 vsize: 112963584 resident: 36376576 share: 30109696 rss: 36376576 rss_rlim: 4294967295
CPU usage: start_time: 1184216423 rtime: 109 utime: 94 stime: 15 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208482080 (LWP 2031)]
[New Thread -1234678896 (LWP 2055)]
(no debugging symbols found)
0x00d2c402 in __kernel_vsyscall ()

+ Trace 147436

Thread 1 (Thread -1208482080 (LWP 2031))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 ??
#4 <signal handler called>
#5 e2k_context_fba
from /usr/lib/libexchange-storage-1.2.so.3
#6 e2k_autoconfig_get_context
from /usr/lib/libexchange-storage-1.2.so.3
#7 exchange_account_connect
from /usr/lib/libexchange-storage-1.2.so.3
#8 exchange_config_listener_authenticate
from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
#9 ??
from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
#10 g_cclosure_marshal_VOID__OBJECT
from /lib/libgobject-2.0.so.0
#11 ??
from /lib/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib/libgobject-2.0.so.0
#13 ??
from /lib/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#15 g_signal_emit
from /lib/libgobject-2.0.so.0
#16 ??
from /usr/lib/libedataserver-1.2.so.9
#17 e_account_list_construct
from /usr/lib/libedataserver-1.2.so.9
#18 ??
from /usr/lib/evolution/2.10/plugins/liborg-gnome-exchange-operations.so
#19 ??
from /lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#21 ??
from /lib/libglib-2.0.so.0
#22 g_main_loop_run
from /lib/libglib-2.0.so.0
#23 bonobo_main
from /usr/lib/libbonobo-2.so.0
#24 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
  Resource id:  0x2000003
(evolution:2031): libsoup-CRITICAL **: soup_message_set_request: assertion `SOUP_IS_MESSAGE (msg)' failed
(evolution:2031): libsoup-CRITICAL **: soup_message_set_flags: assertion `SOUP_IS_MESSAGE (msg)' failed
(evolution:2031): libsoup-CRITICAL **: soup_session_send_message: assertion `SOUP_IS_MESSAGE (msg)' failed
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1400232
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
--------------------------------------------------

Comment 1 palfrey 2007-07-12 11:18:19 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 453932 ***