kmymoney-5.1-479 appimage and later hang at tips window.

[Jack]

On 5/14/23 15:59, Harry G McGavran Jr via KMyMoney wrote:
> Jack wrote:
>> I just tried again, and get the same output as you do, but after that
>> the program appears.  When it hangs for you, what is happening?
> After the console output from the spawning xterm window, I get no
> further response, even for an hour or more...
I don't see any xterm window.  Do you just mean the xterm from which you 
launch the appimag?
>> Specifically, if you run top or look at a performance monitor, is KMM
>> using any resources?
> No, no resources from KMM are apparent when this happens.
So it's not using any CPU?  If you do "ps auxf" and look for the 
kmymoney processes, can you tell what state it is in?
>> A bit more effort might be to launch KMM under gdb, and then interrupt it when it appears hung and generate a
>> backtrace.
> I did play with gdb, but I never got any symbol info when
> running gdb in the exracted directory of the appimage.
>
> I would get a number of "LWP" spawned threads a few of which
> would later terminate on the own and others would spawn.
>
> Interupting KMM and doing a "backtrace" yielded two stack frames
> with no data references because of the lack of symbols.
I wouldn't expect any debug symbols in the appimage, but you should 
still get a full backtrace, at least mentioning all the files involved.  
At least post the two entry backtrace you got, just in case it might 
provide some hint.
> That meant gdb didn't really give me clues.  At this point
> I don't know how to get symbols from the appimage directory, there
> probably are none.
>> Another possibility is to use strace, but the output is
>> likely to be voluminous, but hopefully it might show what it's
>> getting
>> stuck on or if it's waiting for something that is just not happening.>
>>
>> As Thomas said, there were no code changes between the version that
>> worked for you and the latest version, so something else must have
>> changed, although I can't think of anything that would cause this
>> issue,
>> as the appimage should be fully self-contained.   Can you think of
>> anything that was upgraded since it last ran correctly for you?
> I played with strace but its output was too voluminous!

Try capturing that output to a file.  Then you can search for the last 
output you get from a regular launch, and then look for any issues in 
the next dozen or hundred lines.

One thing I'd love to figure out - whether it's trying and failing to 
create and display the main window, or if something is failing before 
that so it's not even trying.  If you do "man ld" and look at the 
section on LD_DEBUG, it might be worth trying one or several of the 
settings for that variable, but I'm pretty much grabbing at straws here.

> I'm not familiar enough with the changes since 476 to know if there
> might be something that would cause this.
If you know the dates of the various appimages, you can clone the git 
repo and look in the log for any commits during that time period.
>    I'd really like to get a
> copy of 476 just to try it again.  It never occurred to me to keep the
> old one until I was happy with the new one.  I know better than to do
> this, but have never had problems with KMM before now, so I just got
> sloppy about it.