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 576769 - crash in Document Viewer: Opening a document
crash in Document Viewer: Opening a document
Status: RESOLVED DUPLICATE of bug 555375
Product: evince
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-25 21:14 UTC by vlad.seghete
Modified: 2009-03-26 02:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description vlad.seghete 2009-03-25 21:14:23 UTC
Version: 2.22.2

What were you doing when the application crashed?
Opening a document


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: gnome

Memory status: size: 44736512 vsize: 44736512 resident: 20156416 share: 11665408 rss: 20156416 rss_rlim: 4294967295
CPU usage: start_time: 1238015571 rtime: 34 utime: 30 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6ad86c0 (LWP 13384)]
[New Thread 0xb693db90 (LWP 13385)]
0xb7f35424 in __kernel_vsyscall ()

Thread 2 (Thread 0xb693db90 (LWP 13385))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 382
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 Form::findWidgetByRef
    from /usr/lib/libpoppler.so.3
  • #8 AnnotWidget::initialize
    from /usr/lib/libpoppler.so.3
  • #9 AnnotWidget::AnnotWidget
    from /usr/lib/libpoppler.so.3
  • #10 Annots::createAnnot
    from /usr/lib/libpoppler.so.3
  • #11 Annots::Annots
    from /usr/lib/libpoppler.so.3
  • #12 Page::displaySlice
    from /usr/lib/libpoppler.so.3
  • #13 ??
    from /usr/lib/libpoppler-glib.so.3
  • #14 pdf_document_thumbnails_get_thumbnail
    at /build/buildd/evince-2.22.2/./backend/pdf/ev-poppler.cc line 1272
  • #15 ev_document_thumbnails_get_thumbnail
    at /build/buildd/evince-2.22.2/./libdocument/ev-document-thumbnails.c line 58
  • #16 ev_job_thumbnail_run
    at /build/buildd/evince-2.22.2/./shell/ev-jobs.c line 435
  • #17 handle_job
    at /build/buildd/evince-2.22.2/./shell/ev-job-queue.c line 129
  • #18 ev_render_thread
    at /build/buildd/evince-2.22.2/./shell/ev-job-queue.c line 264
  • #19 g_thread_create_proxy
    at gthread.c line 635
  • #20 start_thread
    from /lib/i686/cmov/libpthread.so.0
  • #21 clone
    from /lib/i686/cmov/libc.so.6


----------- .xsession-errors (160103 sec old) ---------------------
(rhythmbox:17591): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:17591): RhythmDB-CRITICAL **: rhythmdb_entry_get_string: assertion `entry != NULL' failed
(rhythmbox:17591): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
(rhythmbox:17591): RhythmDB-CRITICAL **: rhythmdb_entry_ref: assertion `entry->refcount > 0' failed
(rhythmbox:17591): RhythmDB-CRITICAL **: rhythmdb_entry_get_double: assertion `entry != NULL' failed
(rhythmbox:17591): RhythmDB-CRITICAL **: rhythmdb_entry_unref: assertion `entry != NULL' failed
(rhythmbox:17591): Rhy
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-03-26 02:10:30 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 555375 ***