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 478672 - crash in Document Viewer: Opening pb.book
crash in Document Viewer: Opening pb.book
Status: RESOLVED DUPLICATE of bug 456255
Product: evince
Classification: Core
Component: general
0.8.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-20 17:30 UTC by noemail
Modified: 2007-09-20 20:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description noemail 2007-09-20 17:30:41 UTC
Version: 0.8.2

What were you doing when the application crashed?
Opening pb.book


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 60919808 vsize: 60919808 resident: 32497664 share: 16146432 rss: 32497664 rss_rlim: 4294967295
CPU usage: start_time: 1190308669 rtime: 88 utime: 75 stime: 13 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 -1209084192 (LWP 4805)]
[New Thread -1211184240 (LWP 4806)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1209084192 (LWP 4805))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 poppler_attachment_save_to_callback
    from /usr/lib/libpoppler-glib.so.1
  • #5 ??
  • #6 ev_document_get_attachments
  • #7 ??
  • #8 ev_sidebar_set_document
  • #9 ??
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
/media/ESCD(7515449)/index.html: line 4: META: No such file or directory
/media/ESCD(7515449)/index.html: line 5: META: No such file or directory
/media/ESCD(7515449)/index.html: line 6: link: No such file or directory
/media/ESCD(7515449)/index.html: line 7: /HEAD: No such file or directory
/media/ESCD(7515449)/index.html: line 8: BODY: No such file or directory
/media/ESCD(7515449)/index.html: line 9: 
: Read-only file system
/media/ESCD(7515449)/index.html: line 10: table: No such file or directory
/media/ESCD(7515449)/index.html: line 11: tr: No such file or directory
/media/ESCD(7515449)/index.html: line 12: syntax error near unexpected token `<'
/media/ESCD(7515449)/index.html: line 12: `			<td height="200"></td>
'
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
/usr/lib/vmware/bin/vmware: /usr/lib/vmware/lib/libpng12.so.0/libpng12.so.0: no version information available (required by /usr/lib/libcairo.so.2)
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Carlos Garcia Campos 2007-09-20 20:45:22 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 456255 ***