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 522480 - crash in Document Viewer:
crash in Document Viewer:
Status: RESOLVED DUPLICATE of bug 415714
Product: evince
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-14 18:31 UTC by steve
Modified: 2008-03-15 17:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description steve 2008-03-14 18:31:27 UTC
Version: 2.20.2

What were you doing when the application crashed?



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

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Wasp
Icon Theme: Wasp

Memory status: size: 39956480 vsize: 39956480 resident: 18120704 share: 13242368 rss: 18120704 rss_rlim: 4294967295
CPU usage: start_time: 1205519467 rtime: 48 utime: 44 stime: 4 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 0xb6ad26c0 (LWP 10693)]
[New Thread 0xb6928b90 (LWP 10694)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6ad26c0 (LWP 10693))

  • #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 Catalog::embeddedFile
    from /usr/lib/libpoppler.so.2
  • #7 poppler_document_get_attachments
    from /usr/lib/libpoppler-glib.so.2
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30e9473 (investor p)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30ef1d6 (investor p)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30ef1d6 (investor p)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30ef1d6 (investor p)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30ef1d6 (investor p)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x30ef1d6 (investor p)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Corrupt JPEG data: premature end of data segment
Error: Unterminated string
--------------------------------------------------
Comment 1 Damien Durand 2008-03-15 17:58:41 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 415714 ***