Bug 338682

Summary: When switching windows using task manager on panel, activity & desktop switch is done in wrong order
Product: [Plasma] kwin Reporter: Mike Krutov <nekoxmachina>
Component: activitiesAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: notuxius
Priority: NOR    
Version First Reported In: 4.11.11   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Mike Krutov 2014-08-30 16:08:32 UTC 
Scenario:
User has 2 activities,
Activity-A & Activity-B
Also, same user has 4 desktops:
Desktop[1-4].
When user is working on something on Activity-B, Desktop 1.
On Activity-A, Desktop 4, user has Skype running.
User recieves a message in skype, so highlighted button of Skype shows up in Task Manager plasmoid.
User presses this button, following happens:
1) Activity-B gets switch from Desktop-1 to Desktop-2.
2) Only after 1), Current Activity gets switched to Activity-A.
Then Notification vanishes from the panel.
This brings in following wrong behavior:
1) ActivityB has now Desktop-4 as active desktop.
2) ActivityA, on the other hand, does not get a switch to Skype desktop, and stays in previous state.
3) Notification vanishes. 

3rd point is not a problem if 1/2 are fixed.

Reproducible: Always
Comment 1 Mike Krutov 2014-08-30 16:11:22 UTC 
>1) Activity-B gets switch from Desktop-1 to Desktop-2.
Desktop-4, of course.
Comment 2 Alexander Mentyu 2018-04-04 15:32:25 UTC 
Clicking on Skype notification didn't bring Skype into front for me - but seems i can't reproduce this bug:
1. Open Skype and set it's desktop to 4 in activity A.
2. Switch to activity B -> desktop 1.
3. Right click on Skype tray icon and chose 'Open Skype'

Actual results:
Activity is switching to A and current desktop is switching to 4.

skypeforlinux-stable-bin 8.15.0.4-1.3
Plasma: 5.12
Apps: 17.12.3
Frameworks: 5.44.0
Qt: 5.10.1
Kernel: 4.14.27-1-MANJARO
OS: Netrunner Rolling
Comment 3 Alexander Mentyu 2018-04-05 15:54:41 UTC 

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