This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2035786 - gnome-tour panicks when launched in environment without graphical session
Summary: gnome-tour panicks when launched in environment without graphical session
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: gnome-tour
Version: 9.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Kalev Lember
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-27 16:25 UTC by Jiri Prajzner
Modified: 2023-09-15 17:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-15 17:02:09 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4105 0 None Migrated None 2023-09-15 17:02:03 UTC
Red Hat Issue Tracker RHELPLAN-106614 0 None None None 2021-12-27 16:32:55 UTC

Description Jiri Prajzner 2021-12-27 16:25:09 UTC 
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
Comment 1 bilelmoussaoui 2022-02-23 09:42:18 UTC 
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.
Comment 2 Tomas Popela 2022-02-23 11:19:13 UTC 
(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).
Comment 3 bilelmoussaoui 2022-02-23 11:23:33 UTC 
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
Comment 4 Tomas Popela 2022-02-23 11:32:04 UTC 
(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.
Comment 5 Jiri Prajzner 2022-02-24 10:22:58 UTC 
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
Comment 6 bilelmoussaoui 2022-02-24 10:26:57 UTC 
I will have a look at fixing the issue today
Comment 8 RHEL Program Management 2023-09-15 17:01:54 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9 RHEL Program Management 2023-09-15 17:02:09 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.