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 422816 - crash in Document Viewer: downloading a document f...
crash in Document Viewer: downloading a document f...
Status: RESOLVED DUPLICATE of bug 412675
Product: evince
Classification: Core
Component: general
0.8.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-25 22:25 UTC by mike.reeves
Modified: 2007-03-26 09:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description mike.reeves 2007-03-25 22:25:00 UTC 
Version: 0.8.0

What were you doing when the application crashed?
downloading a document from intel


Distribution: Fedora release 6.92 (Rawhide)
Gnome Release: 2.18.0 2007-03-20 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.3017.fc7 #1 SMP Thu Mar 22 23:00:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299902
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Echo

Memory status: size: 379596800 vsize: 379596800 resident: 15532032 share: 9662464 rss: 15532032 rss_rlim: 18446744073709551615
CPU usage: start_time: 1174861351 rtime: 28 utime: 19 stime: 9 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496356864 (LWP 3888)]
[New Thread 1084229952 (LWP 3889)]
(no debugging symbols found)
0x0000003b0220d83f in waitpid () from /lib64/libpthread.so.0

+ Trace 122217

Thread 1 (Thread 46912496356864 (LWP 3888))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__VOID
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 Catalog::embeddedFile
    from /usr/lib64/libpoppler.so.1
  • #4 poppler_document_get_attachments
    from /usr/lib64/libpoppler-glib.so.1
  • #5 ??
  • #6 ??
  • #7 ev_sidebar_set_document
  • #8 ??
  • #9 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #10 g_cclosure_marshal_VOID__VOID
    from /lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #13 ??
  • #14 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib64/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/swamp-vmm:/tmp/.ICE-unix/2922
position: 0 0 1024 768
effective alpha: 255
free
You can not run beagle as root.  Beagle is designed to run from your own
user account.  If you want to create multiuser or system-wide indexes, use
the beagle-build-index tool.
You can override this setting using the beagle-config or beagle-settings tools.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3400003 (Evince Doc)
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 0x3200003 (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-03-26 09:22:18 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 412675 ***