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 429851 - crash in Document Viewer: reading a pdf file
crash in Document Viewer: reading a pdf file
Status: RESOLVED DUPLICATE of bug 362110
Product: evince
Classification: Core
Component: general
0.6.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-15 02:05 UTC by smoke.v
Modified: 2007-04-15 02:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description smoke.v 2007-04-15 02:05:57 UTC 
Version: 0.6.1

What were you doing when the application crashed?
reading a pdf file


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 121606144 vsize: 0 resident: 121606144 share: 0 rss: 56483840 rss_rlim: 0
CPU usage: start_time: 1176602576 rtime: 0 utime: 1373 stime: 0 cutime:1242 cstime: 0 timeout: 131 it_real_value: 0 frequency: 0

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)
[Thread debugging using libthread_db enabled]
[New Thread -1229187408 (LWP 7767)]
[New Thread -1230718048 (LWP 7769)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 127854

Thread 1 (Thread -1229187408 (LWP 7767))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 poppler_page_render_selection
    from /usr/lib/libpoppler-glib.so.1
  • #5 pdf_selection_render_selection
  • #6 _egg_marshal_VOID__INT_INT
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall 






Comment 1


Pedro Villavicencio





          2007-04-15 02:17:21 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 362110 ***