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 319446 - Crash when highlighting text in PDF
Crash when highlighting text in PDF
Status: RESOLVED DUPLICATE of bug 315552
Product: evince
Classification: Core
Component: general
0.4.x
Other other
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-10-21 18:58 UTC by Phil M.
Modified: 2005-11-10 01:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Phil M. 2005-10-21 18:58:36 UTC
Distribution: Debian testing/unstable
Package: evince
Severity: normal
Version: GNOME2.10.2 0.4.x
Gnome-Distributor: Debian
Synopsis: Crash when highlighting text in PDF
Bugzilla-Product: evince
Bugzilla-Component: general
Bugzilla-Version: 0.4.x
BugBuddy-GnomeVersion: 2.0 (2.10.1)
Description:
Description of the crash:
I had highlighted some text in a PDF document (about 2.5 lines), and
GNOME notified me that evince had crashed, and launched Bug Buddy.

Steps to reproduce the crash:
No attempt made (yet?)

Expected Results:
Text is highlighted, for whatever purpose (visibility, copying)

How often does this happen?
Haven't used current version (0.4.0) enough to tell.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' 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)
(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)
[Thread debugging using libthread_db enabled]
[New Thread -1228663104 (LWP 7092)]
[New Thread -1228797008 (LWP 7094)]
(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)
0xb70b9c41 in waitpid () from /lib/tls/libc.so.6

Thread 1 (Thread -1228663104 (LWP 7092))

  • #0 waitpid
    from /lib/tls/libc.so.6
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 CairoFont::CairoFont
    from /usr/lib/libpoppler.so.0
  • #4 CairoFontEngine::getFont
    from /usr/lib/libpoppler.so.0
  • #5 CairoOutputDev::updateFont
    from /usr/lib/libpoppler.so.0
  • #6 TextSelectionPainter::visitWord
    from /usr/lib/libpoppler.so.0
  • #7 TextWord::visitSelection
    from /usr/lib/libpoppler.so.0
  • #8 TextLine::visitSelection
    from /usr/lib/libpoppler.so.0
  • #9 TextBlock::visitSelection
    from /usr/lib/libpoppler.so.0
  • #10 TextPage::visitSelection
    from /usr/lib/libpoppler.so.0
  • #11 TextPage::drawSelection
    from /usr/lib/libpoppler.so.0
  • #12 TextOutputDev::drawSelection
    from /usr/lib/libpoppler.so.0
  • #13 poppler_page_render_selection
    from /usr/lib/libpoppler-glib.so.0
  • #14 pdf_selection_render_selection
  • #15 ev_selection_render_selection
  • #16 ev_pixbuf_cache_get_selection_pixbuf
  • #17 ev_view_rotate_right
  • #18 g_child_watch_add
    from /usr/lib/libglib-2.0.so.0
  • #19 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #21 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #22 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 main
  • #0 waitpid
    from /lib/tls/libc.so.6




------- Bug moved to this database by unknown@gnome.bugs 2005-10-21 18:58 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was bugbuddy@millenix.mailshell.com.

Comment 1 Nickolay V. Shmyrev 2005-11-10 01:06:30 UTC
Sorry for long delay and thanks for reporting about it. It seems like a known
problem. We are working on it.

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