Version: 2.24.2

What were you doing when the application crashed?
crashes opening any pdf file with evince when using i810 driver


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.2 2008-11-25 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.5-117.fc10.i686 #1 SMP Tue Nov 18 12:19:59 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 83259392 vsize: 83259392 resident: 18751488 share: 11554816 rss: 18751488 rss_rlim: 18446744073709551615
CPU usage: start_time: 1231431598 rtime: 43 utime: 33 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb7f5d750 (LWP 31581)]
[New Thread 0xb5675b90 (LWP 31583)]
[New Thread 0xb61f7b90 (LWP 31582)]
0x00110416 in __kernel_vsyscall ()

+ Trace 211389

----------- .xsession-errors (173068 sec old) ---------------------
W: main.c: High-priority scheduling enabled in configuration but not allowed by policy.
W: core-util.c: setpriority(): Permission denied
E: main.c: Daemon startup failed.
(gnome-keyring-daemon-wrapper:3287): EggSMClient-WARNING **: Received XSMP SaveYourself message in state save-yourself-done: client or server error
bluetooth-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
gpk-update-icon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
Window manager warning: Fatal IO error 11 (Resource temporarily unavailable) on display ':0.0'.
gnome-terminal: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
The application 'nautilus' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------