GNOME Bugzilla – Bug 646385
crash in Document Viewer: opening an IRS pdf fill ...
Last modified: 2011-04-01 00:33:10 UTC
Version: 2.30.3 What were you doing when the application crashed? opening an IRS pdf fill in form. Distribution: Debian 6.0.1 Gnome Release: 2.30.2 2010-11-12 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 130211840 vsize: 130211840 resident: 21282816 share: 13656064 rss: 21282816 rss_rlim: 18446744073709551615 CPU usage: start_time: 1301607109 rtime: 3946 utime: 3504 stime: 442 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 0xb27b2b70 (LWP 26165)] 0xb77d8424 in __kernel_vsyscall ()
+ Trace 226521
Thread 1 (Thread 0xb688c9f0 (LWP 26163))
A debugging session is active. Inferior 1 [process 26163] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (59672 sec old) --------------------- (epiphany-browser:21804): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed (epiphany-browser:21804): Gtk-CRITICAL **: gtk_tree_model_filter_real_unref_node: assertion `elt->ref_count > 0' failed The program 'epiphany-browser' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 98744 error_code 9 request_code 55 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog (evolution-alarm-notify:2035): evolution-alarm-notify-WARNING **: alarm.c:252: Requested removal of nonexistent alarm! --------------------------------------------------
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 bug 602405 ***