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 513477 - crash in Tasks: closing acrobar reader 8
crash in Tasks: closing acrobar reader 8
Status: RESOLVED DUPLICATE of bug 445309
Product: evolution
Classification: Applications
Component: BugBuddyBugs
unspecified
Other All
: High critical
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-01-31 16:31 UTC by suroy
Modified: 2008-02-20 06:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description suroy 2008-01-31 16:31:27 UTC 
Version: 2.10

What were you doing when the application crashed?
closing acrobar reader 8


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.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 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: 126332928 vsize: 126332928 resident: 46071808 share: 32464896 rss: 46071808 rss_rlim: 4294967295
CPU usage: start_time: 1201794972 rtime: 2712 utime: 2510 stime: 202 cutime:3229 cstime: 230 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 -1208936736 (LWP 10006)]
[New Thread -1295578224 (LWP 10585)]
[New Thread -1268782192 (LWP 10032)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 187611

Thread 2 (Thread -1295578224 (LWP 10585))

  • #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 (311 sec old) ---------------------
report junk?? Hi! I Mary from Alaska
report junk?? Hi!
report junk?? Good afternoon!
report junk?? Hello!
report junk?? Guaranteed gigantic boner!
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800056 (COMMAT2365)
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 0x3800056 (COMMAT2365)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Akhil Laddha 2008-02-20 06:53:38 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 ***