Bug 448662 – crash in Tasks: closing app with X butto...

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 448662 - crash in Tasks: closing app with X butto...


Summary:	crash in Tasks: closing app with X butto...


Status:	RESOLVED DUPLICATE of bug 432796

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-06-18 03:29 UTC by evanesce69
Modified:	2007-06-18 20:58 UTC

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

Description evanesce69 2007-06-18 03:29:17 UTC

Version: 2.10

What were you doing when the application crashed?
closing app with X button



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 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: 648515584 vsize: 648515584 resident: 65642496 share: 43835392 rss: 65642496 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182136960 rtime: 349 utime: 293 stime: 56 cutime:2 cstime: 12 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 46912496496224 (LWP 28100)]
[New Thread 1126455632 (LWP 28144)]
[New Thread 1084229968 (LWP 28120)]
(no debugging symbols found)
0x00000037ca00d89f in waitpid () from /lib64/libpthread.so.0

+ Trace 141784

Thread 3 (Thread 1084229968 (LWP 28120))

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



----------- .xsession-errors (6 sec old) ---------------------
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x14180e8
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1418405
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x1418405
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x4d
--------------------------------------------------

Comment 1 André Klapper 2007-06-18 20:58:23 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 432796 ***