Bitmessage/PyBitmessage-2025-02-27
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 56 Actions Packages Projects Releases 5 Wiki Activity

Second bitmessage instance should pop up the window of the first one and quit, and not run in parallel #630

New Issue
Closed
opened 2014-01-25 07:16:12 +01:00 by yurivict · 4 comments
yurivict commented 2014-01-25 07:16:12 +01:00 (Migrated from github.com)
Copy Link

I launched the second copy of bitmessage from the same user on the same display, and it launched. It showed two windows and two tray icons.

This shouldn't happen. It should locate the first instance, make its window active and quit. Chrome browser, for example, does this.

The second instance also shouldn't be allowed to launch off the same database on another screen, since this doesn't make sense.

It is possible to find the window of the original instance through the window manager.

I launched the second copy of bitmessage from the same user on the same display, and it launched. It showed two windows and two tray icons. This shouldn't happen. It should locate the first instance, make its window active and quit. Chrome browser, for example, does this. The second instance also shouldn't be allowed to launch off the same database on another screen, since this doesn't make sense. It is possible to find the window of the original instance through the window manager.
PeterSurda commented 2015-10-18 12:50:30 +02:00 (Migrated from github.com)
Copy Link

This is a very valid point.

This is a very valid point.
PeterSurda commented 2015-11-14 13:26:30 +01:00 (Migrated from github.com)
Copy Link

I did a quick test on Windows. It looks like when you launch it in a different way, for example, once from the command line using python, and once from the bundled EXE, it doesn't detect the second instance correctly. Only if you run two instances from python at the same time, or run the EXE twice at the same time, will it detect the second instance correctly.

I did a quick test on Windows. It looks like when you launch it in a different way, for example, once from the command line using python, and once from the bundled EXE, it doesn't detect the second instance correctly. Only if you run two instances from python at the same time, or run the EXE twice at the same time, will it detect the second instance correctly.
thelink2012 commented 2015-11-14 19:38:29 +01:00 (Migrated from github.com)
Copy Link

Perhaps using a UUID as the basename in singleton.py of the lock file would resolve the issue instead of taking it off argv.

Perhaps using a UUID as the `basename` in `singleton.py` of the lock file would resolve the issue instead of taking it off argv.
PeterSurda commented 2015-11-14 19:41:14 +01:00 (Migrated from github.com)
Copy Link

I think that a combination of current UID and configuration path would be better, or maybe even only the configuration path.

I think that a combination of current UID and configuration path would be better, or maybe even only the configuration path.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
bug
Milestone
No items
No Milestone v0.6.0
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-27#630
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?