Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 575664 - Gnome Shell workspace switching behaviour changed
Summary: Gnome Shell workspace switching behaviour changed
Status: CLOSED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.14   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-08-27 07:50 EDT by Will Rogers CLA
Modified: 2021-09-10 10:52 EDT (History)
1 user (show)

See Also:

Attachments
Screencast showing workspace switch (716.44 KB, video/webm)
2021-08-27 07:50 EDT, Will Rogers CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Will Rogers CLA 2021-08-27 07:50:18 EDT 
Created attachment 287035 [details]
Screencast showing workspace switch

Example scenario using product based on Eclipse 2020-12:

* SWT shell on workspace 1. Eclipse product window on workspace 2.
* Action on shell triggers logging that opens Console view on workspace 1.
* Gnome shell switches workspaces to workspace 2.

This workspace switch did not happen in Eclipse Oxygen.

The switch is very problematic for our RCP application. It is not clear it is a bug exactly, but I am trying to find out what changed so that I can try to prevent this behaviour.

See attached screencast video.

RHEL7, Gnome Shell 3.28.3, openjdk 11.0.11.
Comment 1 Will Rogers CLA 2021-09-06 09:34:09 EDT 
I have established that this behaviour changes between SWT versions 3.112.0 and 3.113.0 (versions from Maven Central).

GTK version is 3.22.30; neither of these SWT versions uses GTK2.
Comment 2 Will Rogers CLA 2021-09-06 11:19:15 EDT 
The change was introduced in this commit: https://git.eclipse.org/c/platform/eclipse.platform.swt.git/commit/?id=bb4b85528d973e7f97e2a0b0f632b4f0f8401b9a

I don't know why.
Comment 3 Will Rogers CLA 2021-09-10 10:52:56 EDT 
After looking into this in some detail, I conclude that the offending fix in Bug 371545 is probably correct. It did change behaviour, and no-one seemed to notice.

Meanwhile I have found a satisfactory workaround in my application, so I will close this bug.