Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When using HiDPI, in Ghidra, some window content is not scaled up but some are #4242

Open
pellaeon opened this issue May 30, 2024 · 4 comments
Labels
bug Something isn't working client geometry

Comments

@pellaeon
Copy link

Describe the bug

  1. I have 2 screens, one is scaled at 150%, the other at 100%
  2. When running Ghidra from xpra, and placing all windows on the 150% screen, one window of Ghidra has the correct frame size, but the content was small (seems to be 1/2 size). One other window has both correct window frame size and content size.

To Reproduce
Steps to reproduce the behavior:

  1. xpra start ssh://...
  2. Download and unpack Ghidra, I tested 11.0.3 and 10.2.2.
  3. Run Ghidra by running ./ghidraRun in the unpacked directory.
  4. See the screenshot:
    Screenshot_20240530_154410

System Information (please complete the following information):

  • Server OS: Ubuntu 22.04.4 LTS
  • Client OS: Ubuntu 24.04 LTS
  • Xpra Server Version: 6.1-r35816-1
  • Xpra Client Version: Xpra GTK3 Wayland client version 6.1-r35816 (gefa5e2cf65) beta
  • KDE Plasma version: 5.27.11
  • Display server: Wayland

Additional context

  • If I move the windows to the 100% screen, everything becomes normal again.
  • I tested konsole running on the xpra server, with its window on the 150% screen, it is displayed as expected. (It's blurry but expected.)
  • Regardless of the setting of KDE's Xwayland Client Scale , the behavior of this bug is the same.
@pellaeon pellaeon added the bug Something isn't working label May 30, 2024
@totaam
Copy link
Collaborator

totaam commented May 31, 2024

Sounds quite similar to #4167 for macos.
I believe that MS Windows also has the same problem, see also #3943 which may help there.

@totaam
Copy link
Collaborator

totaam commented May 31, 2024

Could be related to #3994

@pellaeon
Copy link
Author

pellaeon commented Jun 1, 2024

I can confirm that adding --opengl=force:native solves the problem. Performance-wise I don't feel any difference but the applications that I use generally don't need a high frame rate.

Thank you for your prompt response, I'm happy to help debug this further.

@totaam
Copy link
Collaborator

totaam commented Jun 17, 2024

This commit fixes things for v6.1 when running Wayland clients: 641847c
Wayland clients and MacOS / Windows use the --opengl=gtk backend - I will need to test some more before backporting this to older branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working client geometry
Projects
None yet
Development

No branches or pull requests

2 participants