Summary: | Task context menu has "Start new instance" for single-instance apps | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Justin Zobel <justin.zobel> |
Component: | Task Manager and Icons-Only Task Manager | Assignee: | Eike Hein <hein> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | argonel, kossebau, nate, plasma-bugs, qydwhotmail |
Priority: | NOR | Keywords: | usability |
Version: | 5.23.4 | ||
Target Milestone: | 1.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=447204 | ||
Latest Commit: | https://invent.kde.org/plasma/plasma-workspace/-/commit/43d50c6c4217972ce8a0d813577eac3894e4122e | Version Fixed In: | 5.25 |
Sentry Crash Report: |
Description
Justin Zobel
2020-11-21 06:52:39 UTC
This is by design. Why do you want to do that? 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. 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 *** 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. |