[linux/wayland] Map renders extremely blurry #10203

New issue

Open

opened 2025-02-04 00:23:20 +00:00 by WhyNotHugo · 0 comments

WhyNotHugo commented

2025-02-04 00:23:20 +00:00

(Migrated from github.com)

Have you searched for similar, already existing issues?

Yes

Describe the issue

The maps itself renders extremely blurry.

Steps to reproduce

Open Organic Maps. Download any country map, and zoom in.

Expected behaviour

Map should render properly

Screenshots

System information:

Operating system and its version: Alpine Linux, edge
Organic Maps version: [you can find it by tapping the button with the green Organic Maps logo] There is not green logo. Are these instructions outdated? I installed via Flatpak, which reports this as 2025.01.26-9.
Device Model: Lenovo t14s

Additional context

I'm using fractional scaling of 1.5. Checking the debug logs, I see that organic maps explicitly bind to wp_fractional_scale_manager_v1 global and requests the scale factor for a few surfaces, so the client is requesting the current scale factor and the compositor is properly informing it.

I'm not sure what other information would be useful here, but I am willing to debug this further.

**Have you searched for similar, already existing issues?** Yes **Describe the issue** The maps itself renders extremely blurry. **Steps to reproduce** Open Organic Maps. Download any country map, and zoom in. **Expected behaviour** Map should render properly **Screenshots** ![Image](https://github.com/user-attachments/assets/6ae229e5-bc43-4d75-858f-1015329b4c6f) **System information:** - Operating system and its version: Alpine Linux, edge - Organic Maps version: [you can find it by tapping the button with the green Organic Maps logo] There is not green logo. Are these instructions outdated? I installed via Flatpak, which reports this as 2025.01.26-9. - Device Model: Lenovo t14s **Additional context** I'm using fractional scaling of 1.5. Checking the debug logs, I see that organic maps explicitly bind to `wp_fractional_scale_manager_v1` global and requests the scale factor for a few surfaces, so the client is requesting the current scale factor and the compositor is properly informing it. I'm not sure what other information would be useful here, but I am willing to debug this further.

This repo is archived. You cannot comment on issues.