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 360060 - Crash Selecting Any Text in a Specific PDF
Crash Selecting Any Text in a Specific PDF
Status: RESOLVED DUPLICATE of bug 316907
Product: evince
Classification: Core
Component: general
0.5.x
Other All
: Normal critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-06 02:48 UTC by Stu Hood
Modified: 2006-10-06 03:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
A Problematic PDF (236.78 KB, application/pdf)
2006-10-06 02:50 UTC, Stu Hood 		Details

Description Stu Hood 2006-10-06 02:48:57 UTC 
Steps to reproduce:
1. Open the attached file
2. Try to select text
3. ..crash


Stack trace:
Backtrace was generated from '/usr/bin/evince'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1208400192 (LWP 31301)]
[New Thread -1209914448 (LWP 31303)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74827

Thread 1 (Thread -1208400192 (LWP 31301))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 CairoFont::create
    from /usr/lib/libpoppler-glib.so.1
  • #5 CairoFontEngine::getFont
    from /usr/lib/libpoppler-glib.so.1
  • #6 CairoOutputDev::updateFont
    from /usr/lib/libpoppler-glib.so.1
  • #7 TextSelectionPainter::visitWord
    from /usr/lib/libpoppler.so.1
  • #8 TextWord::visitSelection
    from /usr/lib/libpoppler.so.1
  • #9 TextLine::visitSelection
    from /usr/lib/libpoppler.so.1
  • #10 TextBlock::visitSelection
    from /usr/lib/libpoppler.so.1
  • #11 TextPage::visitSelection
    from /usr/lib/libpoppler.so.1
  • #12 TextPage::drawSelection
    from /usr/lib/libpoppler.so.1
  • #13 TextOutputDev::drawSelection
    from /usr/lib/libpoppler.so.1
  • #14 poppler_page_render_selection
    from /usr/lib/libpoppler-glib.so.1
  • #15 pdf_selection_render_selection
  • #16 ev_selection_render_selection
  • #17 ev_pixbuf_cache_get_selection_pixbuf
  • #18 ev_view_rotate_right
  • #19 g_idle_dispatch
    at gmain.c line 3796
  • #20 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #21 g_main_context_iterate
    at gmain.c line 2547
  • #22 IA__g_main_loop_run
    at gmain.c line 2751
  • #23 IA__gtk_main
    at gtkmain.c line 1026
  • #24 main
  • #0 __kernel_vsyscall 

Other information:
Comment 1 Stu Hood 2006-10-06 02:50:54 UTC 
Created attachment 74107 [details]
A Problematic PDF
Comment 2 Elijah Newren 2006-10-06 02:52:12 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 316907 ***
Comment 3 Stu Hood 2006-10-06 02:56:45 UTC 
Hmm... maybe its just me, but the stack trace for that bug doesn't look anything like this one. Is that just a catch-all bug?

The trace is from Ubuntu Dapper with Evince 0.5.3, but also occurs with Evince 0.6.0 in Edgy.
Comment 4 Elijah Newren 2006-10-06 03:07:12 UTC 
(In reply to comment #3)
> Hmm... maybe its just me, but the stack trace for that bug doesn't look
> anything like this one. Is that just a catch-all bug?
> 
> The trace is from Ubuntu Dapper with Evince 0.5.3, but also occurs with Evince
> 0.6.0 in Edgy.

Check out the stack traces in bug 357797, bug 357779, bug 356675, and bug 356595, for examples.  All are with evince 0.6.0 and using GNOME 2.16.x (two of the bugs come from FC6 test releases, while two are with Ubuntu edgy previews).  I'm not an evince maintainer, but I do think this is a duplicate considering those other bugs.  I'll be happy to reopen and let an evince maintainer have a look if think I may have made a mistake, however.