ipfs/ipfs-desktop

Scaling issues

Open

#3,006 opened on Oct 12, 2025

View on GitHub
 (8 comments) (0 reactions) (0 assignees)JavaScript (912 forks)batch import
P2effort/hoursexp/intermediatehelp wantedkind/bug

Repository metrics

Stars
 (5,632 stars)
PR merge metrics
 (Avg merge 8d 12h) (6 merged PRs in 30d)

Description

  • OS: ArchLinux / KDE
  • Version of IPFS Desktop 0.46.0

Describe the bug I'm using KDE 6.4.5 (Framework versions 6.18.0 and 6.19.0; QT-Version 6.9.2 and 6.10.0) and with a scaling factor of 70%.

Version 0.45.0 of the IPFS Desktop works normally, but IPFS Desktop 0.46.0 has heavy scaling issuing:

  • The "full screen" is not full screen but only a section of the screen in the left upper corner.
  • The Mouse is offset, so clicking on elements only work if the mouse is not over the element, but below on the right of them (scaling is basicly applied but not properly translated to the application).
  • The Logo screen in the beginning is weirdly cutoff.

To Reproduce Steps to reproduce the behavior:

  1. Open app
  2. See error

Expected behavior Same scaling behavior as on 0.45.0

Screenshots Here's an example of a "full screen" of IPFS Desktop 0.46.0:

Contributor guide

Research direction
Investigate changes in the window setup between v0.45.0 and v0.46.0, particularly window options like 'useContentSize' or 'scaleFactor' settings. Test on a Linux/KDE environment with custom scaling factor.
Tech stack
javascript
Domain
desktop
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70