Rune Player (Mac version) last.fm login failed; the same API is functional on Windows.

[Kauxan]

Describe the bug
Rune Player (Mac version) last.fm login failed; the same API is functional on Windows.

To Reproduce
Steps to reproduce the behavior:

1. Go to 'Settings'
2. Click on 'Playback'
3. Scroll down to 'Online Services - Last.fm'
4. Click on ‘Login’
5. Provide username, passwords, API Key, and API Secret
6. Click on 'Login'

Expected behavior
Login successfully

Screenshots

reqwest::Error {
    kind: Request,
    url: "https://ws.audioscrobbler.com/2.0/?format=json",
    source: hyper_util::client::legacy::Error(
        Connect,
        ConnectError(
            "dns error",
            Custom {
                kind: Uncategorized,
                error: "failed to lookup address information: nodename nor servname provided, or not known",
            },
        ),
    ),
}

Desktop (please complete the following information):

• OS: macOS 15.6.1 (24G90)

[dosubot]

Hi @Kauxan! I'm Dosu and I’m helping the rune team.

The DNS resolution error on macOS is likely due to differences in how the Rust networking stack interacts with system DNS settings compared to Windows. The Rune Player uses the reqwest library and Tokio's TcpStream for network requests, which rely on the system's DNS configuration and do not have macOS-specific logic in the codebase for handling DNS or network permissions source.

Troubleshooting steps you can try:

• Check your macOS network settings and DNS configuration (System Settings > Network > Wi-Fi > Details > DNS).
• Ensure Rune Player has network permissions (System Settings > Privacy & Security > Network).
• Try disabling any VPN, proxy, or firewall that could block DNS requests.
• Test DNS resolution for ws.audioscrobbler.com from Terminal using nslookup or dig to confirm system-level DNS works.

If the issue persists only in Rune Player, it may be related to how Rust's async networking libraries interact with macOS 15.6.1. There are no known platform-specific workarounds in the codebase, so system-level troubleshooting is the best next step.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Losses]

That's weird, is your proxy working well...? And you are using an intel mac or a arm mac?