Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Networking broken on Tumbleweed - Login not possible #133

Closed
Ozymandias42 opened this issue Aug 21, 2021 · 2 comments
Closed

Networking broken on Tumbleweed - Login not possible #133

Ozymandias42 opened this issue Aug 21, 2021 · 2 comments
Labels
bug Something isn't working linux Linux-specific issues wontfix This will not be worked on

Comments

@Ozymandias42
Copy link

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 }))

@jpochyla jpochyla added bug Something isn't working linux Linux-specific issues wontfix This will not be worked on labels Aug 23, 2021
@jpochyla
Copy link
Owner

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

@Ozymandias42
Copy link
Author

Ozymandias42 commented 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 #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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working linux Linux-specific issues wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants