Bug 475393 – crash in Tasks: i don't know, i just try...

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 475393 - crash in Tasks: i don't know, i just try...


Summary:	crash in Tasks: i don't know, i just try...


Status:	RESOLVED DUPLICATE of bug 405646

Product:	evolution
Classification:	Applications
Component:	Tasks
Version:	2.10.x (obsolete)
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-09-10 08:55 UTC by lq8178
Modified:	2007-10-07 18:17 UTC

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

Description lq8178 2007-09-10 08:55:22 UTC

Version: 2.10

What were you doing when the application crashed?
i don't know, i just try close the application


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 133951488 vsize: 133951488 resident: 55214080 share: 41439232 rss: 55214080 rss_rlim: 4294967295
CPU usage: start_time: 1189414084 rtime: 740 utime: 683 stime: 57 cutime:31 cstime: 11 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 4945)]
[New Thread -1274135664 (LWP 5049)]
[New Thread -1237988464 (LWP 5004)]
[New Thread -1247810672 (LWP 4968)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 161738

Thread 4 (Thread -1247810672 (LWP 4968))

#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 ---------------------
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1807791
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x18073fa
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x18073fa
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  158
  Minor opcode:  6
  Resource id:  0x69
--------------------------------------------------

Comment 1 Lucky Wankhede 2007-09-17 08:27:04 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!

Comment 2 Tobias Mueller 2007-10-07 18:17:49 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 405646 ***