Bug 574279 – crash in Document Viewer: scrolling down a pdf doc

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 574279 - crash in Document Viewer: scrolling down a pdf doc


Summary:	crash in Document Viewer: scrolling down a pdf doc


Status:	RESOLVED DUPLICATE of bug 555375

Product:	evince
Classification:	Core
Component:	general
Version:	2.22.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evince Maintainers
QA Contact:	Evince Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-03-05 14:57 UTC by jasonmclach
Modified:	2009-03-05 15:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description jasonmclach 2009-03-05 14:57:27 UTC

Version: 2.22.2

What were you doing when the application crashed?
scrolling down a pdf doc


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

System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 456151040 vsize: 456151040 resident: 125964288 share: 15278080 rss: 125964288 rss_rlim: 18446744073709551615
CPU usage: start_time: 1236263270 rtime: 1553 utime: 1408 stime: 145 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 0x7f55e527a780 (LWP 5243)]
[New Thread 0x42240950 (LWP 5244)]
(no debugging symbols found)
0x00007f55df7f7b66 in poll () from /lib/libc.so.6

+ Trace 213195

Thread 2 (Thread 0x42240950 (LWP 5244))

#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 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 Form::findWidgetByRef
from /usr/lib/libpoppler.so.3
#7 AnnotWidget::initialize
from /usr/lib/libpoppler.so.3
#8 AnnotWidget::AnnotWidget
from /usr/lib/libpoppler.so.3
#9 Annots::createAnnot
from /usr/lib/libpoppler.so.3
#10 Annots::Annots
from /usr/lib/libpoppler.so.3
#11 Page::displaySlice
from /usr/lib/libpoppler.so.3
#12 ??
from /usr/lib/libpoppler-glib.so.3
#13 ??
from /usr/lib/evince/backends/libpdfdocument.so
#14 ??
#15 ??
#16 ??
#17 ??
from /usr/lib/libglib-2.0.so.0
#18 start_thread
from /lib/libpthread.so.0
#19 clone
from /lib/libc.so.6
#20 ??



----------- .xsession-errors (340 sec old) ---------------------
** (nm-applet:4850): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.36" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4850): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.36" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4850): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.36" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4850): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.36" is not allowed to own the service "org.freedesktop.Networ
** (nm-applet:4850): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.36" is not allowed to own the service "org.freedesktop.Networ
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 palfrey 2009-03-05 15:02:40 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 555375 ***