Skip to content
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

Cannot start Winpinator #19

Open
michalderlatka opened this issue Apr 24, 2022 · 5 comments
Open

Cannot start Winpinator #19

michalderlatka opened this issue Apr 24, 2022 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@michalderlatka
Copy link

On both W10 and W11 I'm not able to run winpinator

image

@swiszczoo
Copy link
Owner

Hi, can you check if this file exists: %APPDATA%\Winpinator\winpinator.lock? It should be created when Winpinator starts. If it doesn't exist, can you create an empty one and check if it will be removed? I have no clue what's going on but that might help to debug it. And I just want to ensure, do you have any free disk space?

@swiszczoo swiszczoo self-assigned this Apr 24, 2022
@swiszczoo swiszczoo added the bug Something isn't working label Apr 24, 2022
@michalderlatka
Copy link
Author

michalderlatka commented Apr 24, 2022

Looks like I found what might be wrong. When you close application with X button it doesn't really close. Process is still runnning, so it cannot be started once again. After killing process in task manager I'm able to start app once again.

I think it would be good to add some kind of notification (winpinator is still running) in tray. With collapsed tray you cannot see it is still running.

@ghost
Copy link

ghost commented Apr 25, 2022

Process is still running

Yes, and that should be checked by the user by disabling that utterly annoying non-feature of hiding systray icons that the system enables by default. One might be surprised by what still runs in the background without their knowledge.

That said, I believe each application should either give up this toxic practice of mapping the Close button to tray minimize, or offer the user the option to choose between minimize-to-tray and straight-up close in their Settings panel.
If the author chooses the second variant and if minimize-to-tray is enabled by default then yes, there should be a one-time notification about the state of the application (at first run, when "closed" to tray), together with a mention of the ability to change that behavior.

@swiszczoo
Copy link
Owner

Yeah, but that's not how it was supposed to work. When you started Winpinator for the second time, it successfully detected that another process is already running, so it tried to tell that older instance to restore a window by some kind of IPC (DDE, to be exact) but somehow failed. I can't think of any reason why it doesn't work on your computer. I thought that maybe the older process was running under privilleged account (by having a selected checkbox in the installer) and the new one under normal account and that broke something, but I just can't replicate it.

@michalderlatka
Copy link
Author

After few days problem suddenly disappeared. I am now able to start Winpinator for the second time and this restores older instance's window.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants