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

Crash when clicking on a web URL #373

Open
FeignMan opened this issue Nov 14, 2024 · 4 comments
Open

Crash when clicking on a web URL #373

FeignMan opened this issue Nov 14, 2024 · 4 comments
Labels
C-crash-report Category: bugs submitted from inlyne's crash reporting P-WSL Platform: windows subsystem linux

Comments

@FeignMan
Copy link

While viewing a markdown file, clicking on a web URL caused the application to crash.
Crash reports are attached.

crash_reports.zip

Note: The reports mention the host OS as Ubuntu 22.4.0, but it might be worth mentioning that it was in WSL2 on a Windows 10 machine.

@CosmicHorrorDev CosmicHorrorDev added C-crash-report Category: bugs submitted from inlyne's crash reporting P-windows Platform: windows P-WSL Platform: windows subsystem linux and removed P-windows Platform: windows labels Nov 15, 2024
@CosmicHorrorDev
Copy link
Collaborator

Fortunately it looks like that error was already relaxed from crashing to logging a message on the main branch

inlyne/src/main.rs

Lines 505 to 507 in 6f9ac5e

} else if let Err(e) = open::that(link) {
tracing::error!("Could not open link: {e} from {:?}", std::env::current_dir())
}

but that doesn't resolve it failing to begin with of course. It looks like it's getting a 512 exit status from trying to run

$ gio open "https://gitlab-ncsa.ubisoft.org/motherbrain/client/neo-client-sdk/"

Running that locally works for me (as does opening links through inlyne, but apparently it's failing for you

@CosmicHorrorDev
Copy link
Collaborator

This looks relevant although our version of open should already include that PR

@FeignMan
Copy link
Author

@CosmicHorrorDev "Running that locally works for me (as does opening links through inlyne, but apparently it's failing for you" - 512 is a DNS issue, and that makes total sense because I'm trying to reach a website hosted inside the company network. The DNS resolution needs to go through my VPN connection.

  1. You may try reproducing this issue by purposely using a URL which would cause a DNS error. DNS error or not, the application should never crash.
  2. My VPN was connected when I got this issue - does Inlyne not respect proxy environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, etc)? That might be an additional issue here.

@CosmicHorrorDev
Copy link
Collaborator

1) is already resolved. For 2) I won't have spare time to dig into things anytime soon, but this is enough to reproduce the behavior you're seeing with inlyne

[package]
name = "repro"
version = "0.1.0"
edition = "2021"

[dependencies]
open = "=5.0.0"
fn main() {
    open::that("https://example.com").unwrap();
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-crash-report Category: bugs submitted from inlyne's crash reporting P-WSL Platform: windows subsystem linux
Projects
None yet
Development

No branches or pull requests

2 participants