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 573956 - crash in Document Viewer: usando icewasel (con var...
crash in Document Viewer: usando icewasel (con var...
Status: RESOLVED DUPLICATE of bug 543942
Product: evince
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-03 18:06 UTC by hlsergio
Modified: 2009-03-03 19:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description hlsergio 2009-03-03 18:06:06 UTC
Version: 2.20.2

What were you doing when the application crashed?
usando icewasel (con varias pestañas abiertas, la activa en google reader) abri el pdf recien bajado y aparecio este error.

using iceweasel (several tabs opened, the active one was google reader) and then switched to the download manager and try to open the recently downloaded file, that was the moment when the bug appeared.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 54095872 vsize: 54095872 resident: 21106688 share: 13443072 rss: 21106688 rss_rlim: 4294967295
CPU usage: start_time: 1236103972 rtime: 65 utime: 60 stime: 5 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 0xb69ea720 (LWP 4942)]
[New Thread 0xb6819b90 (LWP 4943)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb69ea720 (LWP 4942))

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


----------- .xsession-errors (257 sec old) ---------------------
Error (2443699): Illegal character <f8> in hex string
Error (2443701): Illegal character <c3> in hex string
Error (2443702): Illegal character <3a> in hex string
Error (2443703): Illegal character <68> in hex string
Error (2443704): Illegal character <3f> in hex string
Error (2443706): Illegal character <d2> in hex string
Error (2443708): Illegal character <3b> in hex string
Error (2443709): Illegal character <15> in hex string
Error (2443710): Illegal character <86> in hex string
Error (2443711): Illegal character <3d> in hex string
Error (2443712): Illegal character <e7> in hex string
Error (2443713): Illegal character <1b> in hex string
Error (2443714): Illegal character <a4> in hex string
Error (2443715): Illegal character <72> in hex string
Corrupt JPEG data: premature end of data segment
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2009-03-03 19:57:15 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 543942 ***