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 463792 - crash in Document Viewer:
crash in Document Viewer:
Status: RESOLVED DUPLICATE of bug 456255
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:30 UTC by email
Modified: 2007-08-06 10:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description email 2007-08-05 22:30:04 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: 80068608 vsize: 80068608 resident: 42348544 share: 15810560 rss: 42348544 rss_rlim: 4294967295
CPU usage: start_time: 1186360580 rtime: 210 utime: 124 stime: 86 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 -1209157072 (LWP 7611)]
[New Thread -1211421808 (LWP 7614)]
(no debugging symbols found)
0x00dc8402 in __kernel_vsyscall ()

Thread 1 (Thread -1209157072 (LWP 7611))

  • #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 poppler_attachment_save_to_callback
    from /usr/lib/libpoppler-glib.so.1
  • #5 ??
  • #6 ev_document_get_attachments
  • #7 ??
  • #8 ev_sidebar_set_document
  • #9 ??
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (3646 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 Iestyn Pryce 2007-08-06 10:39:38 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 456255 ***