8372977: unnecessary gthread-2.0 loading

[azvegint]

Actual usage of the gthread-2.0 was removed with GTK2 support in JDK-8329471.
But there are some leftovers, we are still loading it with GTK3, even though it was never used when it was added in JDK-8164321.

It wasn't an issue before, but some modern systems (e.g. openSUSE 16) don't provide the library.
Because of this, we are unable to load GTK, which leads to Robot functionality requiring the Screencast or Remote Desktop API on Wayland not working.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Warning

 ⚠️ Found leading lowercase letter in issue title for 8372977: unnecessary gthread-2.0 loading

Issue

• JDK-8372977: unnecessary gthread-2.0 loading (Bug - P3)

Reviewers

• Phil Race (@prrace - Reviewer)
• Alexander Zuev (@azuev-java - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28625/head:pull/28625
$ git checkout pull/28625

Update a local copy of the PR:
$ git checkout pull/28625
$ git pull https://git.openjdk.org/jdk.git pull/28625/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28625

View PR using the GUI difftool:
$ git pr show -t 28625

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28625.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back azvegint! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@azvegint This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8372977: unnecessary gthread-2.0 loading

Reviewed-by: prr, kizune

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 36 new commits pushed to the master branch:

• aff25f1: 4690476: NegativeArraySizeException from AffineTransformOp with shear
• e93b10d: 8365400: Enhance JFR to emit file and module metadata for class loading
• 8d80778: 8373023: [REDO] Remove the default value of InitialRAMPercentage
• ... and 33 more: https://git.openjdk.org/jdk/compare/b0a758f2180a8305c05e9640192818bbb31d7922...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@azvegint The following label will be automatically applied to this pull request:

• client

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (5af0f23b)

[prrace]

I see that testing looks good.

[azuev-java]

Looks good.

[azvegint]

/integrate

[openjdk]

Going to push as commit 5ea2b64.
Since your change was applied there have been 39 commits pushed to the master branch:

• e534ee9: 8364343: Virtual Thread transition management needs to be independent of JVM TI
• ba777f6: 8372851: Modify java/io/File/GetXSpace.java to print path on failure of native call
• 8a5db91: 8171432: (fs) WindowsWatchService.Poller::run does not call ReadDirectoryChangesW after a ERROR_NOTIFY_ENUM_DIR
• ... and 36 more: https://git.openjdk.org/jdk/compare/b0a758f2180a8305c05e9640192818bbb31d7922...master

Your commit was automatically rebased without conflicts.

[openjdk]

@azvegint Pushed as commit 5ea2b64.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.