Please confirm the following.
What version of the Modrinth App are you using?
0.15.10 and 0.15.11 (earlier versions work)
What operating systems are you seeing the problem on?
Windows
Describe the bug
Approximately a second after loading the app, the mouse stops working in various ways:
- The cursor changes to clicking mode some times, and it stays that way
- Clicking, Hovering and Scrolling give no response.
- If I click on something before it gets unresponsive, it does work for that little time frame
- The tab navigation does work
- The buttons for closing, maximizing and minimizing remain working
- The bar to move the window works normally
- Resizing works perfectly fine
- Reinstalling from scratch doesn't help
- The UI renders correctly
- The application does not crash
This occurs in versions 0.15.10 and 0.15.11, which are the latest to the moment of this writing.
The issue is not present in any previews version.
Steps to reproduce
- Open Modrinth in version 0.15.10 or 0.15.11
- Wait aproximately a second
- Try to use the mouse
Expected behavior
Any reponse
Additional context
- Windows 11 version 25H (OS Build 26200.8875)
- AMD Radeon RX 6650 XT 32.0.11029.1008
- 12th Gen Intel(R) Core(TM) i5-12400F
- WebView2 version 150.0.4078.65
I tested with three monitors:
- 3840 x 2160 to 150%
- 2560 x 1440 to 100%
- 920 x 1080 to 100%
After changing to only one monitor (the first one) to 100%, the issue persists.
session log after opening version 0.15.10:
session_20260715_234648.log
Apps with overlays my computer also has installed:
- Discord
- Steam
- AMD Adrenalin
- Logitech G Hub
- Xbox Game Bar
- PowerToys
If you guys need any more information feel free to ask :)
Please confirm the following.
What version of the Modrinth App are you using?
0.15.10 and 0.15.11 (earlier versions work)
What operating systems are you seeing the problem on?
Windows
Describe the bug
Approximately a second after loading the app, the mouse stops working in various ways:
This occurs in versions 0.15.10 and 0.15.11, which are the latest to the moment of this writing.
The issue is not present in any previews version.
Steps to reproduce
Expected behavior
Any reponse
Additional context
I tested with three monitors:
After changing to only one monitor (the first one) to 100%, the issue persists.
session log after opening version 0.15.10:
session_20260715_234648.log
Apps with overlays my computer also has installed:
If you guys need any more information feel free to ask :)