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

Conflicts with local instance. #32

Open
mzso opened this issue Sep 27, 2020 · 8 comments
Open

Conflicts with local instance. #32

mzso opened this issue Sep 27, 2020 · 8 comments

Comments

@mzso
Copy link

mzso commented Sep 27, 2020

Behaviour

Typical fail for a portable package. (but very annoying). Won't run if a local version is running.

Steps to reproduce this issue

  1. Have Locel WF running
  2. Start WF portable
  3. Portable won't run only a new window of the local instance is opened

Expected behaviour

Run WF portable completely independently from an instance that has nothing to do with it.

Actual behaviour

Stated above.

@crazy-max
Copy link
Member

Have you checked the configuration settings to handle multi instances? https://portapps.io/app/waterfox-portable/#configuration

@mzso
Copy link
Author

mzso commented Sep 27, 2020

Have you checked the configuration settings to handle multi instances? https://portapps.io/app/waterfox-portable/#configuration

It helps. but causes the usual running and non-responding message to appear if I am running the exe again. And in fact a local Waterfox version is not an instance of this portable package, so it shouldn't conflict with it at all.

@crazy-max
Copy link
Member

@mzso

It helps. but causes the usual running and non-responding message to appear if I am running the exe again. And in fact a local Waterfox version is not an instance of this portable package, so it shouldn't conflict with it at all.

Can you elaborate your use case steps by steps please? Also I need some logs and you configuration file (yaml) for each instance to be able to reproduce. Update your issue and create a proper bug report.

@mzso
Copy link
Author

mzso commented Sep 29, 2020

@mzso

It helps. but causes the usual running and non-responding message to appear if I am running the exe again. And in fact a local Waterfox version is not an instance of this portable package, so it shouldn't conflict with it at all.

Can you elaborate your use case steps by steps please? Also I need some logs and you configuration file (yaml) for each instance to be able to reproduce. Update your issue and create a proper bug report.

The local instance is just the official WF classic installed normally. So it doesn't have a yaml.
Use case would be to run the portable instance for various reasons. Checking something I browsed with that, or just running an (should be) isolated instance to test something.

@EmberHeartshine
Copy link

If you start the portable instance first, the local instance will start normally and without complaint.

This behavior is seen in almost every portable Firefox edition; the executable checks to see if another version of FF is already running and refuses to run if so. The normal (installed) version does not have this check.

@mzso
Copy link
Author

mzso commented Apr 13, 2021

@EmberHeartshine commented on 2021. ápr. 13. 13:54 CEST:

This behavior is seen in almost every portable Firefox edition; the executable checks to see if another version of FF is already running and refuses to run if so.

And it's a defect in all.

The normal (installed) version does not have this check.

It does. Only behaves differently. Opens a new window or tab. But a portable version should never check for other instances.

@EmberHeartshine
Copy link

wants a fix

provides a fix

"not good enough!"

K

@mzso
Copy link
Author

mzso commented Apr 13, 2021

@EmberHeartshine commented on 2021. ápr. 14. 01:28 CEST:

wants a fix

provides a fix

"not good enough!"

K

Who fixed the flaw? I'm not aware of a fix...
As for workarounds, I have my own if the need arises. (PS: The local instance is pretty much always running.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants