From:  alfredo.pons@gmail.com
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.10.0
Subject: Evince always crash

Distribution: Fedora Core release 4 (Stentz)
Package: evince
Severity: critical
Version: GNOME2.10.0 0.4.x
Gnome-Distributor: Red Hat, Inc
Synopsis: Evince always crash
Bugzilla-Product: evince
Bugzilla-Component: general
Bugzilla-Version: 0.4.x
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I use Fedora Core 4 and I never can execute Evince, crash always. I
don't know the problem to this.
(I'm sorry, my English is bad. I'm spanish).

Steps to reproduce the crash:
1. Only one step. I execute Evince and crash always.
2.
3.

Expected Results:


How often does this happen?
Always.

Additional Information:
I use kernel  2.6.14-1.1653_FC4  now. But,when I
used other kernels, Evince crash too.
Other librarys that I have:
libgnomeui-2.10.0-1
glibc-2.3.5-10.3
gnome-print-0.37-11
libgnomeprintui22-devel-2.10.1-1
libgnomedb-1.2.0-3.1
...


Debugging Information:

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)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208940864 (LWP 3867)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0x00569402 in __kernel_vsyscall ()

+ Trace 64768

------- Bug created by bug-buddy at 2005-12-22 22:10 -------


Bugreport had an attachment. This cannot be imported to Bugzilla.
Contact bugmaster@gnome.org if you are willing to write a patch for this.