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
Starting a second instance crashes the first instance #11
Comments
|
The stack trace looks like we're trying to build the UI again, thus replacing some GObjects references, the GC collects the older (but still active) references, and we end up with a segfault. |
Confirmed: Gtk signals the running application which runs the Now, to understand how to switch to the running app... |
Found it: |
Done in c0feda7 |
Oh, |
Gtk tries to keep unique applications by default. When starting a new instance it will actually send a message to the currently running instance, and immediately exit the new instance.
This is currently not supported by the app, and is leading to a crash:
At a minimum, the app shouldn't crash. Ideally, it should be un-minimized (if needed), moved to the current screen (if possible) and put above any existing windows on that screen.
The text was updated successfully, but these errors were encountered: