Fwd: reports - all blank suddenly

[Geert Janssens]

Thanks,

There is clearly nothing in the trace files suggesting a problem with report generation. The perl 
error is harmless.

My first guess is still a variation of https://bugzilla.gnome.org/show_bug.cgi?id=645273

Yesterday Chris Good slightly improved the wording of the FAQ I first pointed you at. What fixes 
it appears to be to change the browser preference at least once.

I wonder if maybe some anti-virus application is interfering. Can you try to temporarily disable 
it ?

If none of that helps, I'll have to defer your question to other Windows users on this list (I'm on 
linux myself).

Good luck,

Geert

On Saturday 19 December 2015 08:57:29 __ wrote:
> That's what I get when after opening GC, trying to make an "account
> report" (which again was just a blank page)
> 
> >>  * 08:47:15  WARN <gnc.app-utils> Could not spawn perl: Failed to
> 
> execute child process (No such file or directory)
> 
> maybe that's just it?  "could not spawn per?"
> 
> an older trace file (not sure whether I tried to use reports in that
> session though) looks like this
> 
> * 10:30:34  WARN <gnc.app-utils> Could not spawn perl: Failed to
> execute child process (No such file or directory)
> * 10:32:46  WARN <gnc.engine> Got a NULL guid_list but the
> QofGuidMatch is not MATCH_NULL (but instead 2). In other words, the
> list of GUID matches is empty but it must contain something
> non-empty.
> * 10:34:33  WARN <gnc.engine> Got a NULL guid_list but the
> QofGuidMatch is not MATCH_NULL (but instead 2). In other words, the
> list of GUID matches is empty but it must contain something
> non-empty.
> * 10:48:13  WARN <gnc.engine> Got a NULL guid_list but the
> QofGuidMatch is not MATCH_NULL (but instead 2). In other words, the
> list of GUID matches is empty but it must contain something
> non-empty.
> * 10:53:39  WARN <gnc.engine> Got a NULL guid_list but the
> QofGuidMatch is not MATCH_NULL (but instead 2). In other words, the
> list of GUID matches is empty but it must contain something
> non-empty.
> * 11:11:23  CRIT <Gdk> inner_clipboard_window_procedure: assertion
> 'success' failed
> * 11:22:58  CRIT <Gdk> inner_clipboard_window_procedure: assertion
> 'success' failed
> * 11:32:06  CRIT <Gdk> inner_clipboard_window_procedure: assertion
> 'success' failed
> * 11:32:22  CRIT <Gdk> inner_clipboard_window_procedure: assertion
> 'success' failed
> * 12:25:49  CRIT <Gdk> inner_clipboard_window_procedure: assertion
> 'success' failed
> 
> I am not really sure when this problem actually came up but I don;t
> think there is any trace files left from the times where it still
> worked. So I have nothing to compare it to