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 448594 - crash in Tasks: closing evo
crash in Tasks: closing evo
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: Tasks
unspecified
Other All
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-06-17 21:09 UTC by Nicolas Mailhot
Modified: 2007-06-18 11:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Nicolas Mailhot 2007-06-17 21:09:34 UTC
Version: 2.12

What were you doing when the application crashed?
closing evo


Distribution: Fedora release 7.89 (Rawhide)
Gnome Release: 2.19.3 2007-06-04 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22-0.16.rc4.cfs17.fc8.nim #1 SMP PREEMPT Sun Jun 17 07:56:30 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 622518272 vsize: 622518272 resident: 83619840 share: 50331648 rss: 83619840 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182107117 rtime: 1362 utime: 1186 stime: 176 cutime:23 cstime: 14 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evolution'

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47421288979488 (LWP 4906)]
[New Thread 1082132816 (LWP 8380)]
[New Thread 1115703632 (LWP 8350)]
[New Thread 1099184464 (LWP 8069)]
0x0000003d3640d89f in __libc_waitpid (pid=8383, stat_loc=0x7fff8a65d82c, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

Thread 2 (Thread 1082132816 (LWP 8380))

  • #0 __lll_mutex_lock_wait
    from /lib64/libpthread.so.0
  • #1 _L_mutex_lock_103
    from /lib64/libpthread.so.0
  • #2 __pthread_mutex_lock
    at pthread_mutex_lock.c line 81
  • #3 <signal handler called>
  • #4 __pthread_mutex_lock
    at pthread_mutex_lock.c line 46
  • #5 PR_Lock
    at ../mozilla/nsprpub/pr/src/pthreads/ptsynch.c line 206
  • #6 _pt_thread_death
    at ../mozilla/nsprpub/pr/src/pthreads/ptthread.c line 804
  • #7 __nptl_deallocate_tsd
    at pthread_create.c line 153
  • #8 start_thread
    at pthread_create.c line 303
  • #9 clone
    from /lib64/libc.so.6
0x0000003d3640d89f	41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
The program is running.  Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (1433 sec old) ---------------------
(evolution:4906): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:4906): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:4906): e-activity-handler.c-WARNING **: EActivityHandler: unknown operation 10922
(evolution:4906): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
(evolution:4906): e-activity-handler.c-WARNING **: e_activity_handler_operation_finished: Unknown activity 10922
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-06-18 11:52:02 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 445309 ***