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 392987 - crash in Document Viewer: started evince from comm...
crash in Document Viewer: started evince from comm...
Status: RESOLVED DUPLICATE of bug 374750
Product: evince
Classification: Core
Component: general
0.6.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-05 02:01 UTC by Iain Buchanan
Modified: 2007-01-05 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Iain Buchanan 2007-01-05 02:01:38 UTC
Version: 0.6.1

What were you doing when the application crashed?
started evince from command line, crashed straight away.


Distribution: Gentoo Base System version 1.12.8
Gnome Release: 2.16.2 2006-12-14 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 43069440 vsize: 0 resident: 43069440 share: 0 rss: 12402688 rss_rlim: 0
CPU usage: start_time: 1167962434 rtime: 0 utime: 25 stime: 0 cutime:23 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1228072768 (LWP 1198)]
[New Thread -1229333616 (LWP 1199)]
0xb7fb6410 in ?? ()

Comment 1 Iain Buchanan 2007-01-05 02:06:01 UTC
trying to get a more useful trace :)
Comment 2 Iain Buchanan 2007-01-05 02:24:47 UTC
OK here's a better trace.  It SEG faults about once every 3 or 4 times, regardless of the pdf I'm opening.  I _think_ it's something to do with the thumbnails, as after bug-buddy has started, I can still look through the pdf, but there are no thumbnails.

I can get around it by running:
$ evince & evince a.pdf

this still doesn't look complete, what else can I recompile?

(gdb) run '/home/iain/Desktop/a.pdf'  
Starting program: /usr/bin/evince '/home/iain/Desktop/a.pdf'
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread -1228318528 (LWP 19927)]
[New Thread -1229579376 (LWP 19928)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1228318528 (LWP 19927)]
0xb709ff6a in FcCompare () from /usr/lib/libfontconfig.so.1
(gdb) thread apply all bt

Thread 2 (Thread -1229579376 (LWP 19928))

  • #0 NameToCharCode::hash
    from /usr/lib/libpoppler.so.1
  • #1 NameToCharCode::add
    from /usr/lib/libpoppler.so.1
  • #2 GlobalParams::GlobalParams
    from /usr/lib/libpoppler.so.1
  • #3 poppler_document_new_from_file
    from /usr/lib/libpoppler-glib.so.1
  • #4 pdf_document_load
  • #5 ev_document_load
  • #6 ev_document_factory_get_document
  • #7 ev_job_xfer_run
  • #8 handle_job
  • #9 ev_render_thread
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??

Thread 1 (Thread -1228318528 (LWP 19927))

  • #0 FcCompare
    from /usr/lib/libfontconfig.so.1
  • #1 IA__FcFontSetSort
    from /usr/lib/libfontconfig.so.1
  • #2 IA__FcFontSort
    from /usr/lib/libfontconfig.so.1
  • #3 pango_fc_font_map_load_fontset
    from /usr/lib/libpangoft2-1.0.so.0
  • #4 pango_font_map_load_fontset
  • #5 itemize_state_process_run
    from /usr/lib/libpango-1.0.so.0
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 itemize_state_init
    from /usr/lib/libpango-1.0.so.0

Comment 3 Carlos Garcia Campos 2007-01-05 10:51:26 UTC
Looks like another crash in fontconfig. 
Does it happens every time with the same pdf file? If so, could you attach such a pdf file to this bug? A longer backtrace would help too. 
Thanks you very much for the report. 

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 374750 ***