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 560049 - crash in Document Viewer: Just opened a PDF file.
crash in Document Viewer: Just opened a PDF file.
Status: RESOLVED DUPLICATE of bug 543942
Product: evince
Classification: Core
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-09 18:28 UTC by power3d
Modified: 2008-11-10 18:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description power3d 2008-11-09 18:28:10 UTC
Version: 2.22.2

What were you doing when the application crashed?
Just opened a PDF file.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Amaranth
Icon Theme: Amaranth

Memory status: size: 82857984 vsize: 82857984 resident: 61583360 share: 13381632 rss: 61583360 rss_rlim: 4294967295
CPU usage: start_time: 1226255250 rtime: 162 utime: 146 stime: 16 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/evince'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6a48700 (LWP 4279)]
[New Thread 0xb68c5b90 (LWP 4280)]
0xb7ee9424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6a48700 (LWP 4279))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 poppler_attachment_save_to_callback
    from /usr/lib/libpoppler-glib.so.3
  • #8 pdf_document_get_attachments
    at /build/buildd/evince-2.22.2/./backend/pdf/ev-poppler.cc line 394
  • #9 ev_document_get_attachments
    at /build/buildd/evince-2.22.2/./libdocument/ev-document.c line 206
  • #10 ev_sidebar_attachments_set_document
    at /build/buildd/evince-2.22.2/./shell/ev-sidebar-attachments.c line 636
  • #11 ev_sidebar_set_document
    at /build/buildd/evince-2.22.2/./shell/ev-sidebar.c line 511
  • #12 ev_window_setup_document
    at /build/buildd/evince-2.22.2/./shell/ev-window.c line 1126
  • #13 g_idle_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 4090
  • #14 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #15 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #16 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #17 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #18 main
    at /build/buildd/evince-2.22.2/./shell/main.c line 401
  • #0 __kernel_vsyscall


----------- .xsession-errors (561 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** (totem:4005): CRITICAL **: bacon_video_widget_get_aspect_ratio: assertion `bvw != NULL' failed
** (totem:4005): CRITICAL **: bacon_video_widget_set_aspect_ratio: assertion `bvw != NULL' failed
(totem:4005): Gtk-CRITICAL **: gtk_widget_is_focus: assertion `GTK_IS_WIDGET (widget)' failed
--------------------------------------------------
Comment 1 palfrey 2008-11-10 18:32:04 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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