# ThinLinc closing on its own on new Mac unless I open context menu **URL:** \ **Category:** Community Support\ **Tags:** bug, linux\ **Created:** [4 November 2024 16:48 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153 "2024-11-04T16:48:19Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Artemy\_Vinogradov](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/artemy_vinogradov/32/565_2.png) [@Artemy\_Vinogradov](https://community.thinlinc.com/u/Artemy_Vinogradov)\ **Post date:** [4 November 2024 16:48 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/1 "2024-11-04T16:48:19Z")
Hello, I have been using ThinLinc for a few years now for my job to connect to our server and do my work on a Linux OS installed on the server. I recently upgraded my computer from a Windows 10 Laptop to a MacOS Mini Mac, and now that I have ThinLinc installed, I have been having a very strange issue. When I open ThinLinc as I usually do, it opens without any issues. However, if I do nothing, without fail the session will end on its own and give me the “ThinLinc closed within 10 seconds” popup as it usually does. However, if I open the context menu over the ThinLinc client (in my case, I have it bound to F7), it will not close itself if I leave it open for ~3 seconds. I can then close the context menu and then continue working as I usually would. I am not sure what is causing this issue. If I open the context menu and then close it, if enough time has not passed, the client will still close regardless. If I could get some help with this issue, I would greatly appreciate it! Thank you so much. ---
**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\ **Post date:** [4 November 2024 20:25 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/2 "2024-11-04T20:25:50Z")
Hi @Artemy_Vinogradov, welcome to the forum. The error you describe sounds strange. Please try starting the ThinLinc client with the “-d5” flag to [enable verbose debugging](https://www.cendio.com/resources/docs/tag/client_cmdline.html?highlight=debug#cmdoption-d), and check the [resulting log file](https://www.cendio.com/resources/docs/tag/client_logfile_placement.html#client-logfile-placement) for clues. If it’s not clear what the problem is, please feel free to post the log messages here and we can have a look for you. ---
**Author:** ![Artemy\_Vinogradov](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/artemy_vinogradov/32/565_2.png) [@Artemy\_Vinogradov](https://community.thinlinc.com/u/Artemy_Vinogradov)\ **Post date:** [4 November 2024 20:50 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/3 "2024-11-04T20:50:42Z")
Hi Aaron, thank you very much. I would like to try your suggestion, but I am having trouble starting ThinLinc from the terminal. Usually, I just use the executable client to start the connection. However, the tlclient command does not seem to exist on my machine even though I have ThinLinc installed. How can I get the tlclient command to work on my machine? ---
**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\ **Post date:** [4 November 2024 21:31 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/4 "2024-11-04T21:31:27Z")
@samuel do you know what the path is for `tlclient` on Mac OS? I don’t have a machine available to check unfortunately. ---
**Author:** ![samuel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/samuel/32/335_2.png) [@samuel](https://community.thinlinc.com/u/samuel)\ **Post date:** [5 November 2024 10:36 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/5 "2024-11-05T10:36:55Z")
`/Applications/ThinLinc Client.app/Contents/MacOS/tlclient` ---
**Author:** ![Artemy\_Vinogradov](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/artemy_vinogradov/32/565_2.png) [@Artemy\_Vinogradov](https://community.thinlinc.com/u/Artemy_Vinogradov)\ **Post date:** [5 November 2024 18:25 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/6 "2024-11-05T18:25:22Z")
Yes, I have access to that file and the permissions are as follow: -rwxr-xr-x. However, trying to run tlclient does not seem to work even while in that directory. I would like to attach a copy of my resulting log file from ~/.thinlinc/tlclient.log as well as on the server from /var/opt/thinlinc/sessions/~myname~/last/xinit.log. How can I do so on this forum? Thank you again for your help. ---
**Author:** ![aaron](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/aaron/32/13_2.png) [@aaron](https://community.thinlinc.com/u/aaron)\ **Post date:** [5 November 2024 20:30 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/7 "2024-11-05T20:30:47Z")
> [@Artemy\_Vinogradov](#): > > However, trying to run tlclient does not seem to work even while in that directory. Could you explain in more detail what doesn’t work? Regarding log files, you can just copy/paste the relevant lines of text here, but check for any sensitive information first. ---
**Author:** ![Artemy\_Vinogradov](https://dub1.discourse-cdn.com/flex005/user_avatar/community.thinlinc.com/artemy_vinogradov/32/565_2.png) [@Artemy\_Vinogradov](https://community.thinlinc.com/u/Artemy_Vinogradov)\ **Post date:** [8 November 2024 18:34 UTC](https://community.thinlinc.com/t/thinlinc-closing-on-its-own-on-new-mac-unless-i-open-context-menu/1153/8 "2024-11-08T18:34:41Z")
I have resolved the issue, it was due to a conflicting software program that closes Mac services automatically when I exit out of all windows for that program. I suppose it thought when the ThinLinc client logs in, it is closed, so the service itself was closed by the program unless it was in use via the context menu. Thank you for the help!