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 536164 - crash in Document Viewer:
crash in Document Viewer:
Status: RESOLVED DUPLICATE of bug 415714
Product: evince
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-02 05:49 UTC by Jason Coplen
Modified: 2008-06-02 08:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Jason Coplen 2008-06-02 05:49:33 UTC
Version: 2.22.1.1

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Tue May 27 15:38:35 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 90431488 vsize: 90431488 resident: 69795840 share: 15187968 rss: 69795840 rss_rlim: 4294967295
CPU usage: start_time: 1212384289 rtime: 405 utime: 346 stime: 59 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c4b940 (LWP 5885)]
[New Thread 0xb6ac9b90 (LWP 5886)]
(no debugging symbols found)
0xb7fab424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6c4b940 (LWP 5885))

  • #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.3
  • #7 poppler_document_get_attachments
    from /usr/lib/libpoppler-glib.so.3
  • #8 ??
    from /usr/lib/evince/backends/libpdfdocument.so
  • #9 ev_document_get_attachments
    from /usr/lib/libevbackend.so.0
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (892 sec old) ---------------------
(gnome-appearance-properties:6138): Gtk-WARNING **: Theme directory scalable/animations/small/16x16 of theme default.kde4 has no size field
(gnome-appearance-properties:6138): Gtk-WARNING **: Theme directory scalable/animations/small/22x22 of theme default.kde4 has no size field
** (gnome-settings-daemon:5413): WARNING **: Failed to open file '/etc/gnome/config/General.ad': No such file or directory
/home/jason/.config/qtcurve.gtk-icons:8: Unable to locate image file in pixmap_path: "16x16/actions/about_kde.png"
/home/jason/.config/qtcurve.gtk-icons:9: Unable to locate image file in pixmap_path: "22x22/actions/about_kde.png"
/home/jason/.config/qtcurve.gtk-icons:10: Unable to locate image file in pixmap_path: "32x32/actions/about_kde.png"
/home/jason/.config/qtcurve.gtk-icons:11: Unable to locate image file in pixmap_path: "16x16/actions/about_kde.png"
/home/jason/.config/qtcurve.gtk-icons:12: Unable to locate image file in pixmap_path: "16x16/actions/about_kde.png"
/home/jason/.config/qtcurve.gtk-icons:13: Unable to locate image file in pixmap_path: "32x32/actions/about_kde.png"
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jason Coplen 2008-06-02 05:55:56 UTC
Ok, I forgot to mention (because bug-buddy told me the crash was in clearlooks and not this file - I think that is a bug in itself) that I already had one instance of evince open when this crashed. It does that fine in XFCE, but in Gnome it crashes.
Comment 2 Carlos Garcia Campos 2008-06-02 08:19:00 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 ***