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 516914 - crash in Document Viewer: randomly clicking and hi...
crash in Document Viewer: randomly clicking and hi...
Status: RESOLVED DUPLICATE of bug 501673
Product: evince
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-16 22:40 UTC by kmlarose
Modified: 2008-02-22 11:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description kmlarose 2008-02-16 22:40:21 UTC 
Version: 2.20.2

What were you doing when the application crashed?
randomly clicking and highlighting


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: BlueHeart
Icon Theme: SphereCrystal

Memory status: size: 318001152 vsize: 318001152 resident: 60887040 share: 14258176 rss: 60887040 rss_rlim: 18446744073709551615
CPU usage: start_time: 1203188836 rtime: 816 utime: 660 stime: 156 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ba5ea9d9d20 (LWP 13544)]
[New Thread 0x40800950 (LWP 13545)]
(no debugging symbols found)
0x00002ba5e5bb134f in waitpid () from /lib/libpthread.so.0

+ Trace 189434

Thread 1 (Thread 0x2ba5ea9d9d20 (LWP 13544))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 TextLine::visitSelection
    from /usr/lib/libpoppler.so.2
  • #6 TextBlock::visitSelection
    from /usr/lib/libpoppler.so.2
  • #7 TextPage::visitSelection
    from /usr/lib/libpoppler.so.2
  • #8 TextPage::getSelectionRegion
    from /usr/lib/libpoppler.so.2
  • #9 poppler_page_get_selection_region
    from /usr/lib/libpoppler-glib.so.2
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
  • #19 __libc_start_main
    from /lib/libc.so.6
  • #20 ??
  • #21 ??
  • #22 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (157538 sec old) ---------------------
(npviewer.bin:10148): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
(npviewer.bin:10148): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
(npviewer.bin:10148): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
(npviewer.bin:10148): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
(npviewer.bin:10148): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so: wrong ELF class: ELFCLASS64
(gedit:6444): Gdk-WARNING **: /build/buildd/gtk+2.0-2.12.7/gdk/x11/gdkproperty-x11.c:318 invalid X atom: -1328960768
(gedit:6444): Gdk-WARNING **: /build/buildd/gtk+2.0-2.12.7/gdk/x11/gdkproperty-x11.c:318 invalid X atom: -1328960752
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-02-22 11:32:12 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 501673 ***