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 563874 - crash in Document Viewer:
crash in Document Viewer:
Status: RESOLVED DUPLICATE of bug 555375
Product: evince
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-09 16:27 UTC by zemerkos
Modified: 2008-12-09 18:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description zemerkos 2008-12-09 16:27:38 UTC 
Version: 2.22.2

What were you doing when the application crashed?



Distribution: Red Hat Linux release 4
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-64-net1 #2 SMP PREEMPT Mon Feb 25 10:58:47 IST 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 431439872 vsize: 431439872 resident: 136990720 share: 14909440 rss: 136990720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1228840010 rtime: 1737 utime: 1501 stime: 236 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 47631527106432 (LWP 6596)]
[New Thread 1082132816 (LWP 6597)]
(no debugging symbols found)
0x00002b520facb336 in poll () from /lib/tls/libc.so.6

+ Trace 210642

Thread 2 (Thread 1082132816 (LWP 6597))

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


----------- .xsession-errors (33 sec old) ---------------------
Unsupported movie property id with value "flash_object"
Unsupported movie property style with value "position: absolute; top: 1px; left: 1px; height: 1px; width: 1px;"
Unsupported movie property quality with value "high"
Unsupported movie property pluginspage with value "http://www.macromedia.com/go/getflashplayer"
unhandled event 19
Loading stream: http://mail.google.com/mail/im/media-api.swf?ver=1.1.1
Loading stream: http://mail.google.com/mail/im/sound.swf
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
(bug-buddy:5541): libebook-WARNING **: Can't find installed BookFactories
(bug-buddy:5541): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1c00003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 palfrey 2008-12-09 18:56:32 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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