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

KDiskMark3 second instance - D-Bus interface is already in use. #88

Closed
WojtasJD opened this issue Aug 24, 2022 · 3 comments
Closed

KDiskMark3 second instance - D-Bus interface is already in use. #88

WojtasJD opened this issue Aug 24, 2022 · 3 comments
Labels
wontfix This will not be worked on

Comments

@WojtasJD
Copy link
Contributor

  • Linux-distro (kernel version): Ubuntu 22.04 (5.15.0-25-generic) x86-64
  • Desktop Environment (KDE/GNOME etc.): GNOME 42.0 (X11)
  • Qt Version: 5.15.3
  • KDiskMark Version: 3.0.0
  • FIO Version: fio-3.28

Description:

Unable to run KDiskMark 3.0.0 multiple instances.

Steps To Reproduce:

Install KDiskMark 3.0.0, launch it and then launch another instance

Screenshot from 2022-08-24 16-47-18
.

@WojtasJD WojtasJD added bug Something isn't working unconfirmed labels Aug 24, 2022
@JonMagon
Copy link
Owner

In fact, this is expected behavior, isn't it? The helper registers the name by which it communicates with the main application. Only one connection can be established at a time. Or it might be worth limiting the number of copies of kdiskmark so that a new window cannot be created.

@WojtasJD
Copy link
Contributor Author

So this will be a limitation of the new version?
With version 2.3.0 I can have multiple instances of KDiskMark running.

@JonMagon
Copy link
Owner

Yes, this is a new technical limitation of the current implementation, related to doing all the work through the helper. This can hardly be solved.

@JonMagon JonMagon added wontfix This will not be worked on and removed bug Something isn't working unconfirmed labels Aug 25, 2022
JonMagon added a commit that referenced this issue Aug 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants