the program itself behaves normally here on one user, but when awaking from
suspend to disk or suspend to ram (when system idles for one night on another
user) the program shows the account as not connected, searching. 

When telling to connect explicitly it does not work, however, when exiting the
program and opening it again it connects at once problem free. 
If there is a log or setting were I can see what could be the cause, please
advise. 
I set this to minor because once understood you have to just restart it, it is
not really an issue. However,for some user (depending on use case) it may be an
annoyance. 

What the program does: after idling long time on another user account, the
application does not manage to log into the voip account, searching constantly
to connect. 

What the program should do: normal reconnect when the user becomes active,
according to the settings of the respective account.

Reproducible: always

Network on this machine is via wicked.