Version: 0.6.0

What were you doing when the application crashed?
Opening a document identifying itself as a pdf.

The frame title read "Microsoft Word - foo.doc (foo.pdf)" so the document might not actually be a pdf.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2869.fc6 #1 SMP Wed Dec 20 14:51:46 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled
----------- .xsession-errors ---------------------
The program '<unknown>' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 24182 error_code 3 request_code 2 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
** WARNING **: alsa_free(): snd_pcm_start() failed: Broken pipe
** WARNING **: alsa_free(): snd_pcm_start() failed: Broken pipe
** (bug-buddy:26576): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------

Memory status: size: 82407424 vsize: 0 resident: 82407424 share: 0 rss: 14016512 rss_rlim: 0
CPU usage: start_time: 1168514476 rtime: 0 utime: 22 stime: 0 cutime:19 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0

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

(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 -1208403424 (LWP 26572)]
[New Thread -1210504304 (LWP 26574)]
(no debugging symbols found)
0x00bab402 in __kernel_vsyscall ()

+ Trace 101224