GNOME Bugzilla – Bug 375529
Crash on assersion while initializing search for document without it
Last modified: 2007-02-07 20:58:27 UTC
Version: 0.6.0 What were you doing when the application crashed? Initializing search in a postscript document. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors --------------------- ** (eggcups:2492): WARNING **: IPP request failed with status 1030 ** (eggcups:2492): WARNING **: IPP request failed with status 1030 ** (eggcups:2492): WARNING **: IPP request failed with status 1030 ** (eggcups:2492): WARNING **: IPP request failed with status 1030 ** (eggcups:2492): WARNING **: IPP request failed with status 1030 ** (eggcups:2492): WARNING **: IPP request failed with status 1030 ** (eggcups:2492): WARNING **: IPP request failed with status 1030 ** (eggcups:2492): WARNING **: IPP request failed with status 1030 -------------------------------------------------- Memory status: size: 120750080 vsize: 0 resident: 120750080 share: 0 rss: 37052416 rss_rlim: 0 CPU usage: start_time: 1163600945 rtime: 0 utime: 168 stime: 0 cutime:138 cstime: 0 timeout: 30 it_real_value: 0 frequency: 159 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 -1208207648 (LWP 3137)] [New Thread -1210467440 (LWP 3138)] (no debugging symbols found) 0x0044f402 in __kernel_vsyscall ()
+ Trace 86666
Thread 1 (Thread -1208207648 (LWP 3137))
Looks like we really have assertion fail on enabled search for documents without it.
*** Bug 377543 has been marked as a duplicate of this bug. ***
It should be fixed already *** This bug has been marked as a duplicate of 358648 ***
*** Bug 405326 has been marked as a duplicate of this bug. ***