AlexandrePTJ / kemai

Kimai desktop client
MIT License
88 stars 25 forks source link

Brew'd app not starting #103

Open kevinpapst opened 11 months ago

kevinpapst commented 11 months ago

Just tried the tap and the cask installation was easy (if you know how to get around th security warnings). But the first start resulted in a "bouncing app icon" for about a minute.

I forced shutdown of the app and restarted: again bouncing and bouncing and bouncing (in the app tray). Finally it stopped bouncing, but there is no app window (nor any "quick-start" dropdown - not sure how the apps/icons ion the upper right toolbar are called).

How to debug what is wrong?

AlexandrePTJ commented 11 months ago

Log files are stored in /Users//Library/Application Support/Kemai/Kemai. Please post content.

kevinpapst commented 11 months ago

Not existing:

Bildschirmfoto 2023-07-23 um 20 47 16

🤷

I had Kemai manually installed before. Could it be, that there is some kind of "leftover" from the old one that is now blocking?

out

AlexandrePTJ commented 11 months ago

Yes it could be a leftover from a previous version. Config file should be located at : /Users/kevin/Library/Preferences/Kemai. First versions use ini file, now it is a json. I may have missed something during the migration process.

kevinpapst commented 11 months ago

Nope, this directory is also not existing:

Bildschirmfoto 2023-07-23 um 22 25 18

Any other idea?

brew remove kemai
brew install kemai

did not change anything...

kruegge82 commented 9 months ago

for me is also not working in MacOs Ventura 13.5.2 my app icon is not bouncing but i get also no error or window in ApplicationSupport also no Kemai folder

maxguru commented 6 months ago

I was having a similar issue on Gentoo Linux after upgrading to the latest version (hang/freeze on startup with no sign of life), however, it seems to have resolved itself after I fiddled around with older versions. Not sure what was causing it, maybe old version data was causing an infinite loop in the new version of the app until I ran older versions that somehow corrected it.