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 448974 - Crash after slecting all of a 6-page pdf document
Crash after slecting all of a 6-page pdf document
Status: RESOLVED DUPLICATE of bug 348702
Product: evince
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-19 02:24 UTC by jeff.hall
Modified: 2007-06-20 01:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description jeff.hall 2007-06-19 02:24:55 UTC 
From: Jeff Hall <jeff.hall@pinoakcorp.com>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.10.0
Subject: Crash after slecting all of a 6-page pdf document

Distribution: Fedora Core release 4 (Stentz)
Package: evince
Severity: normal
Version: GNOME2.10.0 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: Crash after slecting all of a 6-page pdf document
Bugzilla-Product: evince
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I did "select all" on a pdf document to see if it was comprised of text
or just full-page images.

Steps to reproduce the crash:
1. So "select all" 
2. see blank screen, hit ESC
3. try to change pages

Expected Results:
The application crashes

How often does this happen?
Just saw it this time, actually.

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496407264 (LWP 22803)]
[New Thread 1084229984 (LWP 22804)]
(no debugging symbols found)
0x0000003452c0bf99 in waitpid () from /lib64/libpthread.so.0

+ Trace 142025

Thread 1 (Thread 46912496407264 (LWP 22803))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_type_check_instance_is_a
    from /usr/lib64/libgobject-2.0.so.0
  • #4 g_object_unref
    from /usr/lib64/libgobject-2.0.so.0
  • #5 g_object_set_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #6 g_object_set
    from /usr/lib64/libgobject-2.0.so.0
  • #7 ev_window_open_uri
  • #8 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #9 g_signal_stop_emission
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #12 ev_document_types_add_filters
  • #13 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #14 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 main 




------- Bug created by bug-buddy at 2007-06-19 02:24 -------
Comment 1 Pedro Villavicencio 2007-06-20 01:59:28 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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