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 558022 - crash in Document Viewer: using the keyboard to sc...
crash in Document Viewer: using the keyboard to sc...
Status: RESOLVED DUPLICATE of bug 535143
Product: evince
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-26 22:25 UTC by charlie.elverson
Modified: 2008-10-28 21:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description charlie.elverson 2008-10-26 22:25:24 UTC 
Version: 2.22.2

What were you doing when the application crashed?
using the keyboard to scroll through a PDF


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Industrial
Icon Theme: SphereCrystal

Memory status: size: 71979008 vsize: 71979008 resident: 51539968 share: 13103104 rss: 51539968 rss_rlim: 4294967295
CPU usage: start_time: 1225059944 rtime: 1721 utime: 1618 stime: 103 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b98700 (LWP 6773)]
[New Thread 0xb6a15b90 (LWP 6774)]
0xb7fb3424 in __kernel_vsyscall ()

+ Trace 208742

Thread 2 (Thread 0xb6a15b90 (LWP 6774))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #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 poppler_page_render
    from /usr/lib/libpoppler-glib.so.3
  • #15 ??
    from /usr/lib/evince/backends/libpdfdocument.so
  • #16 ev_document_render
    from /usr/lib/libevbackend.so.0
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 IA__g_slice_free1
    at /tmp/buildd/glib2.0-2.16.6/glib/gslice.c line 423
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ?? 


----------- .xsession-errors (36 sec old) ---------------------
** Message: GetValue variable 2 (2)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2200003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Susana 2008-10-28 21:16:07 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 535143 ***