GNOME Bugzilla – Bug 483920
crash in Document Viewer: Trying to launch the evi...
Last modified: 2007-10-06 09:13:55 UTC
Version: 0.9.0 What were you doing when the application crashed? Trying to launch the evince viewer on a PDF file that I have (the description of Dell's Latitude D520). The distribution of this machine is not Ubuntu anymore. I've been using Debian's sid for many months (I guess that I used Ubuntu just for installation and the first week). I have seen similar crashes with eog, while I was opening many photos. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.20.0 2007-09-21 (Debian) BugBuddy Version: 2.20.0 System: Linux 2.6.23-rc6-1 #1 SMP PREEMPT Mon Sep 17 16:26:01 BRT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 290144256 vsize: 290144256 resident: 35389440 share: 12767232 rss: 35389440 rss_rlim: 18446744073709551615 CPU usage: start_time: 1191624581 rtime: 274 utime: 250 stime: 24 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 0x2b3f3e67c1d0 (LWP 10787)] [New Thread 0x40800950 (LWP 10788)] (no debugging symbols found) 0x00002b3f3762dc7f in waitpid () from /lib/libpthread.so.0
+ Trace 168144
Thread 1 (Thread 0x2b3f3e67c1d0 (LWP 10787))
----------- .xsession-errors (9660 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... --------------------------------------------------
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 ***