Report tab displays all white - worked last time (Aug 2016)

[Rufus]

> gnucash.trace

/tmp/gnucash.trace does not exist on that path or anywhere else in the
system according to "locate" and "recoll"; although I just began using
the latter and may not have a handle on what the filters are doing.

That's after starting from console:
"gnucash --debug --extra"

Does that mean gnucash did not trigger any trace output? Totally clean
run despite throwing a python error to stdout (see previous post)?

On an aside, does gnucash use yelp to display "Help" and maybe other
stuff? I found a reference to this elsewhere, but it was a few years
old. Suse apparently does not install yelp by default, so I installed it
but it doesn't appear to make any difference to the report display problem.

Rufus



On 04/06/2017 01:43 PM, John Ralls wrote:
> 
>> On Apr 6, 2017, at 11:37 AM, Rufus <rlaggren at gmail.com> wrote:
>>
>> John
>>
>>> gnucash trace...
>>
>> What does that involve? Not familiar. CLI parameters?
>>
>>> more messages from console...
>>
>> That was all of it that showed when starting GC. I did not actually do
>> anything at all in GC, just started the program, so perhaps more msg's
>> would appear... However, the report tab opened as part of start-up (it
>> was blank) so I would think that any operations that generate the report
>> would have been run as part of GC's startup procedure - and thus would
>> have produced complaints at that time if it was going to.
>>
>> Want to mention that Edit/ReportOptions dialog looks and apparently
>> works as expected.
>>
>> It sounds like I have the python perqs (somewhere on the system,
>> anyway); and the webkit stuff looks like the files are then, anyway.
>> I'll look into the trace when I get time this evening.
> 
> 
> Rufus,
> 
> Please remember to copy the list on all replies.
> 
> See http://wiki.gnucash.org/wiki/Tracefile
> 
> Yes, if a report tab opened then any console errors should have showed up there.
> 
> Regards,
> John Ralls
>