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 527810 - crash in Document Viewer: Tried to scroll in the 2...
crash in Document Viewer: Tried to scroll in the 2...
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-04-13 01:26 UTC by kengruven+crash
Modified: 2008-04-15 07:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description kengruven+crash 2008-04-13 01:26:50 UTC 
Version: 2.20.2

What were you doing when the application crashed?
Tried to scroll in the 2007 1040EZ instructions PDF.


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

System: Linux 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Mist

Memory status: size: 339976192 vsize: 339976192 resident: 129380352 share: 14684160 rss: 129380352 rss_rlim: 18446744073709551615
CPU usage: start_time: 1208048649 rtime: 688 utime: 646 stime: 42 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 0x2ad18b898ec0 (LWP 1221)]
[New Thread 0x40800950 (LWP 1222)]
0x00002ad186671edf in waitpid () from /lib/libpthread.so.0

+ Trace 195086

Thread 1 (Thread 0x2ad18b898ec0 (LWP 1221))

  • #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 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
  • #18 ??
  • #19 __libc_start_main
    from /lib/libc.so.6
  • #20 ??
  • #21 ??
  • #22 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (1224471 sec old) ---------------------
(gecko:10717): Pango-WARNING **: Error loading GPOS table 5503
(gecko:10717): Pango-WARNING **: Error loading GPOS table 5503
(gecko:10717): Pango-WARNING **: Error loading GPOS table 5503
(gecko:10717): Pango-WARNING **: Error loading GPOS table 5503
(gecko:10717): Pango-WARNING **: Error loading GSUB table 28333
(gecko:10717): Pango-WARNING **: Error loading GPOS table 5503
(gecko:10717): Pango-WARNING **: Error loading GSUB table 28333
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-13 08:21:27 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 ***
Comment 2 kengruven+crash 2008-04-14 21:22:37 UTC 
I'm confused.  Was that a typo?

- My bug is in GNOME 2.20, on Debian unstable, which has Poppler 0.6.4, and is a crash when trying to scroll in a static document.

- GNOME bug 316907 (fd.o bug 4649) is a bug in GNOME 2.10 when trying to enter text into a document, and was fixed in Poppler 0.5.4, over 18 months ago.

If this is really the same bug (the symptoms look different, but I didn't look very closely yet), should we ask the fd.o folks to reopen 4649?
Comment 3 Nickolay V. Shmyrev 2008-04-15 01:52:33 UTC 
> If this is really the same bug (the symptoms look different, but I didn't look
very closely yet), should we ask the fd.o folks to reopen 4649?

yes please. Poppler still crashes in VisitSelection, it shouldn't be so.
Comment 4 Gianluca Borello 2008-04-15 07:00:15 UTC 
@Nickolay: so when someone reports a bug with that stacktrace, shall we open a new bug on freedesktop or can i continue to mark it as a dup of bug 316907? stacktrace are very similar!
Comment 5 Gianluca Borello 2008-04-15 07:03:53 UTC 
from what I see, this bug has already been reported on https://bugs.freedesktop.org/show_bug.cgi?id=12589, so imho there is not a problem if we continue to mark them as a dup of 316907, but tell me exactly what you want to do