Closed fribeiro-keeps closed 1 year ago
That certainly sounds possible! Have you checked the client logs? If we are lucky an error might have been logged before it crashed.
So far I have been unable to reproduce your issue. Can you give me precise steps in order to reproduce it?
I've tried to initialize the containers without Timezones variables (LIBKI_TZ and TZ) and all the dates are matching. However, the client still crashes. Now I installed the latest version v23.05. The log file is here. Log_2023_05_02__11_30_25_247.txt
Steps to reproduce: Run the Setup Wizard; Configure Scheme (http), Host (my server IP), Port (3000); Specify Location and Client name; Do not start Libki client automatically; Nothing (just redisplay the Libki login screen); Introduce the Password; Destination Location (C:\Program Files (x86)\Libki); Click in Install; Finish;
I'm still trying to understand when your client is crashing. I think you are saying that you if you simply log in to the client and wait one minute, it crashes when the timer is decremented. Do you see the change in the number before it crashes?
The last line in your log file is
2023-05-02T11:31:33 [Debug] ENTER TimerWindow::showSystemTrayIconTimeLeftMessage
so I will presume the crash happens within that method.
Can you tell me what your ClientTimeNotificationFrequency and ClientTimeWarningThreshold are set to? I'm having a git check that if clientTimeNotificationFrequency is set to 0 it will crash.
Yes, I see the number changing before it crashes. Both of those setting are empty.
Can you try setting those both to "5" and let me know if it continues to crash?
That did the trick :+1: Libki client doesn't crash with those settings
excellent! Now I have to find out why the defaults aren't working 😁
Thanks for your help! For now I will use this settings :smile:
Using client v2.2.20.0, the app stops working when reducing the session time for the first time. E.g. The clock starts with 45 minutes and when updates to 44, the client crashes. I can see the error at Windows Event Viewer but the error details doesn't help much.
I wonder if this is caused by the date differences.