Bug 455437 – 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 455437 - crash in Tasks:


Summary:	crash in Tasks:


Status:	RESOLVED DUPLICATE of bug 460409

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-10 07:04 UTC by atul
Modified:	2007-09-21 18:51 UTC

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

Description atul 2007-07-10 07:04:34 UTC

What were you doing when the application crashed?



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

Memory status: size: 112836608 vsize: 112836608 resident: 30367744 share: 19025920 rss: 30367744 rss_rlim: 4294967295
CPU usage: start_time: 1184049176 rtime: 251 utime: 225 stime: 26 cutime:0 cstime: 1 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 -1209157920 (LWP 5073)]
[New Thread -1314423920 (LWP 5317)]
[New Thread -1282294896 (LWP 5104)]
[New Thread -1251316848 (LWP 5101)]
(no debugging symbols found)
0x0084b402 in __kernel_vsyscall ()

+ Trace 146927

Thread 2 (Thread -1314423920 (LWP 5317))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/libpthread.so.0
#2 _L_mutex_lock_79
from /lib/libpthread.so.0
#3 pthread_mutex_lock
from /lib/libpthread.so.0
#4 ??
#5 <signal handler called>
#6 ??
from /lib/libglib-2.0.so.0
#7 ??
from /lib/libglib-2.0.so.0
#8 ??
from /lib/libglib-2.0.so.0
#9 __nptl_deallocate_tsd
from /lib/libpthread.so.0
#10 start_thread
from /lib/libpthread.so.0
#11 clone
from /lib/libc.so.6



----------- .xsession-errors (1608 sec old) ---------------------
(evolution:5073): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5073): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5073): e-data-server-ui-DEBUG: ep_msg_send: in main thread? 0
(evolution:5073): Gtk-CRITICAL **: gtk_toggle_button_get_active: assertion `GTK_IS_TOGGLE_BUTTON (toggle_button)' failed
(evolution:5073): 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:5073): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8912020'
(evolution:5073): GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance `0x8912140'
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3a01069 specified for 0x3a01aa0 (Delete acc).
(evolution:5073): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed
--------------------------------------------------

Comment 1 Tobias Mueller 2007-07-17 18:20:04 UTC

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!

Comment 2 Suman Manjunath 2007-09-21 17:25:27 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 460409 ***