-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kinto.sh does not start automatically on Windows 11 #883
Comments
More details. The IT people are telling me that kinto should not appear in the taskbar upon reboot. So I opened this as a bug, just in case it isn't supposed to do that, but I can't imagine that it would not start automatically in normal cases. I strongly believe that there is some authorization restriction preventing this. So, I think what I need to know is what auth/authz is needed to have this start automatically on Windows 11. |
Hey, it's me, from Toshy. I have used Kinto on Win11 without any issues. It does show up in the system tray, just like it did in Win10. But it was just a personal system, and the user was an administrator. Could be a permissions issue if your Win11 user is not an admin. This is totally unrelated to your previous issue with Toshy on RHEL, and I would have no idea how to fix the Windows version of Kinto. But it's definitely supposed to start automatically and show up in the tray, with a "k" icon like its Linux version.
Did you mean, "should appear"? Otherwise this sentence is confusing without further context. |
@RedBearAK Thanks for the response and confirmation. As for your comment about "kinto should not appear in the taskbar", that is what I meant. The full context of that sentence
@rbreaves or any other contributor, do you all have any suggestions on what needs to change to allow kinto to start automatically? |
That was my other possible interpretation. But I would think that would mean it may be difficult to get Kinto to autostart at login, if you aren't the one that has control over what gets allowed to autostart. They may be applying a policy that blocks things from being added as autostart items or services, or just stops them from running. I assume that you are able to get Kinto to start manually, even though that hasn't been stated explicitly in this thread. You may be stuck with that because of your managed IT environment. Kind of the like the permission issues with RHEL. |
@RedBearAK Thanks again for the info. When I install kinto.sh, it starts and runs ok. I didn't see how to start it manually. Maybe I just missed a simple step? As for the auto start issue, I think that the IT guys are willing to make the policy changes to allow auto start. They just need to know what to change. |
I doubt you missed anything, it's probably just being blocked by a policy setting. Only the IT people might know what they did to cause that.
Maybe you can use the technique I always used when I was working on new customizations of the Kinto AHK config file in Windows. There's a file called Once upon a time I somehow put a shortcut to that on the Win11 taskbar as if it was an application, but at some point after some Win11 updates the ability to do that seemed to disappear. So I mostly settled on having a shortcut to the file on the desktop, and also since I was using it a lot it would show up in the Start menu as a recent file. If Kinto works fine after installing, it should mean that you can manually launch it with that script. I'm not aware of a more convenient way to launch it. I don't recall there being a "Start Kinto" item in the application menu in Windows, since it is intended to always auto-start itself.
Knowing IT people, it seems unlikely that they will be interested in making a specific exception to the auto-start blocking policy just for Kinto, but maybe you'll get lucky. This Python function seems to be the entirety of what the setup script does when installing Kinto in Windows: Lines 17 to 88 in 4a3bfe7
The key is probably this line in the last os.system('mklink "%userprofile%\\AppData\\Roaming\\Microsoft\\Windows\\STARTM~1\\Programs\\Startup\\kinto-start.vbs" "%userprofile%\\.kinto\\kinto-start.vbs"') |
Thank you for the detailed comment. It does appear to be that I am unable to add things to the location they need to be in to allow auto start. I can probably get this change authorized. Just needed to know what needed to be done. This issue can be closed now, as I think it is resolved. Hopefully, this will provide documentation for others who might run into the same thing. |
Describe the bug
kinto.sh does not start automatically on Windows 11
Expected behavior
I expect that kinto.sh will be started upon system startup and that it shows up in the system tray and is active.
Install Type: Bare Metal
Distro: Windows 11
DE: n/a
Branch: master, dev
Commit: git rev-parse --short HEAD
Logs and status if relevant
Don't know what to grab on Windows 11
The text was updated successfully, but these errors were encountered: