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 533578 - crash in Document Viewer: I was reading a pdf docu...
crash in Document Viewer: I was reading a pdf docu...
Status: RESOLVED DUPLICATE of bug 316907
Product: evince
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-17 15:21 UTC by sancio86
Modified: 2008-05-18 08:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description sancio86 2008-05-17 15:21:11 UTC 
Version: 2.20.2

What were you doing when the application crashed?
I was reading a pdf document, continuosly selecting and deselecting part of text.
Document: official FIBA basketball rules 2008, found on FIBA.com


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.22-3-k7 #1 SMP Sun Feb 10 21:04:14 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 84058112 vsize: 84058112 resident: 60506112 share: 12349440 rss: 60506112 rss_rlim: 4294967295
CPU usage: start_time: 1211036047 rtime: 12096 utime: 11389 stime: 707 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6abd940 (LWP 3885)]
[New Thread 0xb690fb90 (LWP 3886)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 197966

Thread 1 (Thread 0xb6abd940 (LWP 3885))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 TextLine::visitSelection
    from /usr/lib/libpoppler.so.2
  • #7 TextBlock::visitSelection
    from /usr/lib/libpoppler.so.2
  • #8 TextPage::visitSelection
    from /usr/lib/libpoppler.so.2
  • #9 TextPage::getSelectionRegion
    from /usr/lib/libpoppler.so.2
  • #10 TextOutputDev::getSelectionRegion
    from /usr/lib/libpoppler.so.2
  • #11 poppler_page_get_selection_region
    from /usr/lib/libpoppler-glib.so.2
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (288 sec old) ---------------------
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400b81 (Vignette -)
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400b81 (Vignette -)
Avviso del window manager: 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)
--------------------------------------------------
Comment 1 Gianluca Borello 2008-05-18 08:44:53 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 316907 ***