Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1488417

Summary: xmtr doesn't actually work
Product: [Fedora] Fedora Reporter: Brian J. Murrell <brian>
Component: mtrAssignee: Michal Sekletar <msekleta>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: msekleta, redhat-bugzilla
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: mtr-0.94-1.fc33 mtr-0.94-1.fc32 mtr-0.94-3.fc33 mtr-0.94-3.fc32 mtr-0.94-3.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-19 17:43:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Brian J. Murrell 2017-09-05 11:05:16 UTC
Description of problem:
When I run "xmtr" (and authenticate with policykit) and then put www.redhat.com into the Hostname box, nothing is reported.

Version-Release number of selected component (if applicable):
mtr-gtk-0.87-4.fc26.x86_64

How reproducible:
100%

Steps to Reproduce:
1. run xmtr
2. authenticate to policykit
3. enter "www.redhat.com" into the Hostname: box

Actual results:
No hops are reported

Expected results:
Should see hops just like "mtr www.redhat.com" produces

Additional info:
Not using Wayland.

Comment 1 Fedora End Of Life 2018-05-03 09:02:17 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Ben Cotton 2018-11-27 15:53:16 UTC
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora  'version' of '27'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Brian J. Murrell 2018-11-27 16:27:02 UTC
Why has this ticket been EOL warned twice and not even triaged?  Is xmtr supported in Fedora or not?  If not, it should be removed.

Comment 4 Ben Cotton 2019-10-31 20:27:19 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2020-11-03 16:46:23 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Brian J. Murrell 2020-11-09 14:52:59 UTC
And so we continue to do the dance of pushing this ticket forward Version: after Version: as it doesn't actually get fixed.  Or removed from the distro.

Can we please put an end to this one way or the other?

Comment 7 Fedora Update System 2021-01-24 20:48:56 UTC
FEDORA-2021-1045cf08ac has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-1045cf08ac

Comment 8 Fedora Update System 2021-01-24 20:48:57 UTC
FEDORA-2021-8e18d291cb has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8e18d291cb

Comment 9 Robert Scheck 2021-01-24 20:53:58 UTC
The update isn't likely perfect, but at least "xmtr fedoraproject.org" works again. See also the upstream bug report at https://github.com/traviscross/mtr/issues/378 for this.

Comment 10 Fedora Update System 2021-01-25 02:08:09 UTC
FEDORA-2021-8e18d291cb has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8e18d291cb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8e18d291cb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2021-01-25 02:19:06 UTC
FEDORA-2021-1045cf08ac has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-1045cf08ac`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-1045cf08ac

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 12 Fedora Update System 2021-01-27 01:18:21 UTC
FEDORA-2021-1045cf08ac has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2021-02-02 02:22:32 UTC
FEDORA-2021-8e18d291cb has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Robert Scheck 2021-04-10 01:07:53 UTC
Brian, thank you very much for your report. Note, I am not the regular mtr package maintainer, however I am a passionated mtr user for nearly two decades. Together with other mtr contributors and the mtr upstream, we've now travelled across the following issues and pull requests:

 - https://github.com/traviscross/mtr/issues/378
 - https://github.com/traviscross/mtr/pull/393
 - https://github.com/traviscross/mtr/pull/394
 - https://github.com/traviscross/mtr/pull/395
 - https://github.com/traviscross/mtr/issues/396
 - https://github.com/traviscross/mtr/pull/397

As of writing, I believe that your reported issue should be fully resolved with the next mtr package update.

Comment 15 Fedora Update System 2021-04-10 01:15:48 UTC
FEDORA-2021-12126ead65 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-12126ead65

Comment 16 Fedora Update System 2021-04-10 01:15:49 UTC
FEDORA-2021-b4e751a26f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-b4e751a26f

Comment 17 Fedora Update System 2021-04-10 01:15:50 UTC
FEDORA-2021-d288193f1d has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d288193f1d

Comment 18 Fedora Update System 2021-04-10 21:37:13 UTC
FEDORA-2021-12126ead65 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-12126ead65`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-12126ead65

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 19 Fedora Update System 2021-04-10 23:12:08 UTC
FEDORA-2021-b4e751a26f has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-b4e751a26f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-b4e751a26f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 20 Fedora Update System 2021-04-10 23:52:58 UTC
FEDORA-2021-d288193f1d has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d288193f1d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d288193f1d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 21 Fedora Update System 2021-04-19 17:43:49 UTC
FEDORA-2021-b4e751a26f has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 22 Fedora Update System 2021-04-19 17:50:45 UTC
FEDORA-2021-d288193f1d has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 23 Fedora Update System 2021-04-24 20:08:49 UTC
FEDORA-2021-12126ead65 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.