GNOME Bugzilla – Bug 519099
crash in Document Viewer: When evince crash, I ope...
Last modified: 2008-02-27 18:12:10 UTC
Version: 2.20.2 What were you doing when the application crashed? When evince crash, I open a document pdf in command line under root account, the document was on a cdrom and cmd line was with wildcard(*). Quand evnce s'est arreté, j'ouvrais un document pdf en ligne de commande sous le compte root, le document est sur un cdrom et la ligne de commande utilisait un wildcard(*). Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-amd64 #1 SMP Tue Feb 12 09:22:35 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 294952960 vsize: 294952960 resident: 28418048 share: 13840384 rss: 28418048 rss_rlim: 18446744073709551615 CPU usage: start_time: 1204137080 rtime: 65 utime: 52 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 0x2b99b701dcd0 (LWP 10784)] [New Thread 0x40800950 (LWP 10785)] (no debugging symbols found) 0x00002b99b21f534f in waitpid () from /lib/libpthread.so.0
+ Trace 190638
Thread 1 (Thread 0x2b99b701dcd0 (LWP 10784))
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 ***