Bug 450310 - Okular should adhere to Plasma activities
Summary: Okular should adhere to Plasma activities
Status: RESOLVED DUPLICATE of bug 442891
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 21.12.2
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-15 15:12 UTC by Gaël de Chalendar (aka Kleag)
Modified: 2024-06-05 19:07 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gaël de Chalendar (aka Kleag) 2022-02-15 15:12:16 UTC
SUMMARY
***
Okular does not know Plasma activities.
***

STEPS TO REPRODUCE
1. Open okular on a Plasma activity with one or more files in tabs
2. Move to another activity
3. Open okular in any way (Alt-F2 + okular, click on a file, open a file from konsole)

OBSERVED RESULT
We are moved to the first activity and the okular window on this activity is activated (with the new file in a tab).

EXPECTED RESULT
A new okular Window in the current activity should be opened (except if the previous one is already set to be visible on this activity too).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  KDE neon 5.24
(available in About System)
KDE Plasma Version: 5.24.0
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
This is closely related to #442891 but maybe more general
Comment 1 TraceyC 2024-06-05 19:04:50 UTC
I am able to confirm this behavior, with an additional detail.
If I open Okular by opening a PDF from Dolphin on the second Activity, I can reproduce the bug.
If I open Okular from the KRunner menu, it opens a new window on the current Activity as expected

Operating System: Solus 4.5
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.8.11-292.current (64-bit)
Graphics Platform: X11
Comment 2 TraceyC 2024-06-05 19:07:49 UTC
Closing this in favor of the older bug describing the same behavior

*** This bug has been marked as a duplicate of bug 442891 ***