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 463791 - crash in Document Viewer:
crash in Document Viewer:
Status: RESOLVED DUPLICATE of bug 415714
Product: evince
Classification: Core
Component: general
0.8.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-05 22:28 UTC by email
Modified: 2007-08-06 07:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description email 2007-08-05 22:28:15 UTC
Version: 0.8.2

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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Fedora

Memory status: size: 73940992 vsize: 73940992 resident: 36372480 share: 14475264 rss: 36372480 rss_rlim: 4294967295
CPU usage: start_time: 1186359403 rtime: 447 utime: 354 stime: 93 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208702416 (LWP 7546)]
[New Thread -1210967152 (LWP 7547)]
(no debugging symbols found)
0x006ba402 in __kernel_vsyscall ()

Thread 1 (Thread -1208702416 (LWP 7546))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 Catalog::embeddedFile
    from /usr/lib/libpoppler.so.1
  • #5 poppler_document_get_attachments
    from /usr/lib/libpoppler-glib.so.1
  • #6 ??
  • #7 ev_document_get_attachments
  • #8 ??
  • #9 ev_sidebar_set_document
  • #10 ??
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (2467 sec old) ---------------------
7117] 01:37:04: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:04: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:04: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:04: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:04: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:04: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:04: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:07: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:07: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:07: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:07: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:07: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
7117] 01:37:07: ERROR: Current font has no glyphs and I couldn't find another font with glyphs... :(
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Carlos Garcia Campos 2007-08-06 07:51:33 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 415714 ***