Bug 519601 – crash in Tasks: closing evolution

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 519601 - crash in Tasks: closing evolution


Summary:	crash in Tasks: closing evolution


Status:	RESOLVED DUPLICATE of bug 445309

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:	2008-02-29 19:26 UTC by dnh
Modified:	2008-03-04 23:09 UTC

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

Description dnh 2008-02-29 19:26:26 UTC

Version: 2.10

What were you doing when the application crashed?
closing evolution


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

System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 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: 133464064 vsize: 133464064 resident: 51060736 share: 35008512 rss: 51060736 rss_rlim: 4294967295
CPU usage: start_time: 1204303102 rtime: 4319 utime: 4063 stime: 256 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 -1208846624 (LWP 31422)]
[New Thread -1239041136 (LWP 32383)]
[New Thread -1290368112 (LWP 31659)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 190874

Thread 2 (Thread -1239041136 (LWP 32383))

#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 pthread_mutex_lock
from /lib/libpthread.so.0
#7 PR_Lock
from /usr/lib/libnspr4.so
#8 ??
from /usr/lib/libnspr4.so
#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 (11 sec old) ---------------------
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x3a00013
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x602cf3
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x603010
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x280006f
--------------------------------------------------

Comment 1 André Klapper 2008-03-04 23:09:02 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 445309 ***