Description of problem: tour panicks when launched from cli or given a valid argument Version-Release number of selected component (if applicable): gnome-tour-40.0-4.el9.x86_64 How reproducible: always Steps to Reproduce: 1. ssh to server/workstation 2. gnome-tour --valid-argument or just plain gnome-tour 3. Actual results: thread 'main' panicked at 'Unable to start GTK3: BoolError { message: "Failed to initialize GTK", filename: "/builddir/build/BUILD/gnome-tour-40.0/vendor/gtk/src/rt.rs", function: "gtk::rt", line: 129 }', src/main.rs:22:17 stack backtrace: 0: 0x562cd5bab2d0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h7346ef35344da971 1: 0x562cd5bc612f - core::fmt::write::h4c35274e7f1f2b72 2: 0x562cd5ba9a95 - std::io::Write::write_fmt::h90963487920a69ee 3: 0x562cd5bad20b - std::panicking::default_hook::{{closure}}::hd2989a88586c636b 4: 0x562cd5baccdd - std::panicking::default_hook::hd68a69e68d565d2d 5: 0x562cd5bad82d - std::panicking::rust_panic_with_hook::h78fa23e85ebb254e 6: 0x562cd5bad3b7 - std::panicking::begin_panic_handler::{{closure}}::h71df9d9892d5bc06 7: 0x562cd5bab76c - std::sys_common::backtrace::__rust_end_short_backtrace::h79afda96df1f9629 8: 0x562cd5bad319 - rust_begin_unwind 9: 0x562cd5b05821 - core::panicking::panic_fmt::h471341e59c25a5c6 10: 0x562cd5b058b3 - core::result::unwrap_failed::h2cdc9a07e4f7629c 11: 0x562cd5b08c27 - gnome_tour::main::hee4c491af842401c 12: 0x562cd5b0a433 - std::sys_common::backtrace::__rust_begin_short_backtrace::h07411f5594d59219 13: 0x562cd5b0a449 - std::rt::lang_start::{{closure}}::h1c04e484b162a296 14: 0x562cd5badc2a - std::rt::lang_start_internal::hce057b83727e2aaa 15: 0x562cd5b08cd2 - main 16: 0x7fa766342560 - __libc_start_call_main 17: 0x7fa76634260c - __libc_start_main@@GLIBC_2.34 18: 0x562cd5b05f15 - _start 19: 0x0 - <unknown> Expected results: print out usage Additional info: gnome-tour --valid-argument works fine from within gnome-terminal
I am not really sure how you end up with this issue, but I have made a new 40.1 release with updated bindings, it should hopefully land soon.
(In reply to belmouss from comment #1) > I am not really sure how you end up with this issue, but I have made a new > 40.1 release with updated bindings, it should hopefully land soon. On thing isn't explicitly mentioned by the reporter and one have to read it between the lines: you will only be able to reproduce it when running GNOME Tour in an environment when there's no graphical session available (aka jump to tty, log in and try to run gnome-tour --help).
Thanks Tomas, although, no idea if there is anything actionable here as it is a GUI application after all and doesn't provide any CLI options that would make such issue a priority
(In reply to belmouss from comment #3) > Thanks Tomas, although, no idea if there is anything actionable here as it > is a GUI application after all and doesn't provide any CLI options that > would make such issue a priority On the other hand it should rather fail gracefully as other GUI applications.
thanks for clarifying Tomas, i overlooked the reply from Bilal. "On the other hand it should rather fail gracefully as other GUI applications." - yes, it should not panic and just fail gracefully
I will have a look at fixing the issue today