Bug 429428 - Task context menu has "Start new instance" for single-instance apps
Summary: Task context menu has "Start new instance" for single-instance apps
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager (show other bugs)
Version: 5.23.4
Platform: openSUSE Linux
: NOR minor
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2020-11-21 06:52 UTC by Justin Zobel
Modified: 2022-07-05 05:47 UTC (History)
5 users (show)

See Also:
Latest Commit: https://invent.kde.org/plasma/plasma-workspace/-/commit/43d50c6c4217972ce8a0d813577eac3894e4122e
Version Fixed In: 5.25
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Justin Zobel 2020-11-21 06:52:39 UTC 
SUMMARY
Cannot open a second instance of konversation

STEPS TO REPRODUCE
1. Start konversation
2. Right-click taskbar item
3. Select Start New Instance

OBSERVED RESULT
No new instance

EXPECTED RESULT
New instance

Operating System: openSUSE Tumbleweed 20201117
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.8-2-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 23.4 GiB of RAM
Graphics Processor: NV136
Comment 1 argonel 2020-11-21 07:32:45 UTC 
This is by design. Why do you want to do that?
Comment 2 Justin Zobel 2020-11-21 08:16:48 UTC 
A user could want separate instances for work and personal IRC conversations.

If this is specifically made this way then Plasma ought to know that an application prevents a new instance from being created, or konversation should at least pop up a message informing the user so there is some idea as to why the second instance didn't launch.
Comment 3 Friedrich W. H. Kossebau 2021-12-21 19:50:49 UTC 
Konversation is designed as a single instance application. Supporting multiple windows would need some big overhaul, nothing to be expected to be done from someone currently, given the maintenance state.

The expectations given by the "Start new instance" are not Konversation's fault though, that is an issue with the task manager, So closing as duplicate of the related bug (which currently is seeing work gladly :) ).

*** This bug has been marked as a duplicate of bug 447204 ***
Comment 4 Nate Graham 2021-12-24 20:59:02 UTC 
Not a duplicate since that bug report is about apps whose desktop files have NoDisplay=true in them, which I have to assume is not the case for Konversation. Making this a new master bug for the issue of Task Manager context menus showing "Start new instance" item for single-instance apps.