[GH-ISSUE #133] Networking broken on Tumbleweed - Login not possible #98

New issue

Closed

opened 2026-02-28 14:30:35 +03:00 by kerem · 2 comments

kerem commented

2026-02-28 14:30:35 +03:00

Owner

Originally created by @Ozymandias42 on GitHub (Aug 21, 2021).
Original GitHub issue: https://github.com/jpochyla/psst/issues/133

When compiled in and run in a 'Toolbox' Ubuntu container it works though without being able to see or connect to my audio.
(I'm using pipewire)

When compiled natively on Tumbleweed or when starting the container-compiled version natively, the connection to the pipewire socket works but the following error occurs.

[2021-08-21T12:02:22Z ERROR psst_core::connection] using AP fallback, error while resolving: AudioFetchingError(Transport(Transport { kind: Dns, message: None, url: Some(Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("apresolve.spotify.com")), port: None, path: "/", query: None, fragment: None }), source: Some(Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }), response: None }))

Originally created by @Ozymandias42 on GitHub (Aug 21, 2021). Original GitHub issue: https://github.com/jpochyla/psst/issues/133 When compiled in and run in a 'Toolbox' Ubuntu container it works though without being able to see or connect to my audio. (I'm using pipewire) When compiled natively on Tumbleweed or when starting the container-compiled version natively, the connection to the pipewire socket works but the following error occurs. `[2021-08-21T12:02:22Z ERROR psst_core::connection] using AP fallback, error while resolving: AudioFetchingError(Transport(Transport { kind: Dns, message: None, url: Some(Url { scheme: "http", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("apresolve.spotify.com")), port: None, path: "/", query: None, fragment: None }), source: Some(Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }), response: None })) `

kerem

2026-02-28 14:30:35 +03:00

closed this issue
added the
bug

wontfix

linux
labels

kerem commented

2026-02-28 14:30:36 +03:00

Author

Owner

@jpochyla commented on GitHub (Aug 23, 2021):

Marking as wonfix, as it's something I personally won't work on. PRs welcome of course.

@jpochyla commented on GitHub (Aug 23, 2021): Marking as wonfix, as it's something I personally won't work on. PRs welcome of course.

kerem commented

2026-02-28 14:30:36 +03:00

Author

Owner

@Ozymandias42 commented on GitHub (Aug 23, 2021):

Marking as wonfix, as it's something I personally won't work on. PRs welcome of course.

That's okay. I looked into it further and noticed it was a local problem after all. Unsetting HTTPS_PROXY and HTTP_PROXY alone wasn't enough like it is for most other apps. I also had to unset SOCKS_PROXY despite the variable being empty.

After that it works.
The idea to make a flatpak together with https://github.com/TheEvilSkeleton resulting in this MR https://github.com/jpochyla/psst/pull/141

Came partly from wanting to find a way around this issue. (which btw. is still present in flatpaks because those use the systems proxy settings too, ironically)

@Ozymandias42 commented on GitHub (Aug 23, 2021): > Marking as wonfix, as it's something I personally won't work on. PRs welcome of course. That's okay. I looked into it further and noticed it was a local problem after all. Unsetting HTTPS_PROXY and HTTP_PROXY alone wasn't enough like it is for most other apps. I also had to unset SOCKS_PROXY despite the variable being empty. After that it works. The idea to make a flatpak together with https://github.com/TheEvilSkeleton resulting in this MR https://github.com/jpochyla/psst/pull/141 Came partly from wanting to find a way around this issue. (which btw. is still present in flatpaks because those use the systems proxy settings too, ironically)