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 475585 - crash in Tasks:
crash in Tasks:
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-09-10 20:16 UTC by manmathan.kumarathurai
Modified: 2007-09-21 18:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description manmathan.kumarathurai 2007-09-10 20:16:44 UTC
Version: 2.10

What were you doing when the application crashed?



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 21:50:50 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: 561901568 vsize: 561901568 resident: 41127936 share: 24346624 rss: 41127936 rss_rlim: 18446744073709551615
CPU usage: start_time: 1189454020 rtime: 673 utime: 584 stime: 89 cutime:133 cstime: 38 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 46912496418960 (LWP 24196)]
[New Thread 1084229968 (LWP 25289)]
[New Thread 1136945488 (LWP 24275)]
(no debugging symbols found)
0x000000343840d97f in waitpid () from /lib64/libpthread.so.0

Thread 2 (Thread 1084229968 (LWP 25289))

  • #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 pthread_mutex_lock
    from /lib64/libpthread.so.0
  • #5 PR_Lock
    from /usr/lib64/libnspr4.so
  • #6 ??
    from /usr/lib64/libnspr4.so
  • #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 (700 sec old) ---------------------
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x46062f9 (thebautyfu)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x46062f9 (thebautyfu)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x46062f9 (thebautyfu)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4e00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4e00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5200003 specified for 0x5200078 ().
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:24196): DEBUG: mailto URL command: evolution --component=mail %s
** (evolution:24196): DEBUG: mailto URL program: evolution
--------------------------------------------------
Comment 1 Suman Manjunath 2007-09-17 04:42:11 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 ***