Bug 14322

Summary:	xmtr does not run with default arguments
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Rémi Verschelde <rverschelde>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	jani.valimaa, mageia, rverschelde
Version:	Cauldron	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mtr-0.85-4.mga5.src.rpm	CVE:
Status comment:

Description Bit Twister 2014-10-18 11:44:48 CEST

Description of problem:
xmtr does not run from desktop or terminal.

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. xmtr
or
2. kioclient exec /usr/share/applications/mageia-mtr.desktop



Reproducible: 

Steps to Reproduce:

Manuel Hiebel 2014-10-20 20:14:54 CEST

Keywords: (none) => Triaged
CC: (none) => jani.valimaa, mageia

Comment 1 Samuel Verschelde 2015-05-19 21:21:30 CEST

CCing Akien in case he wants to investigate.

CC: (none) => rverschelde
Summary: 5a2: xmtr does not run => xmtr does not run

Samuel Verschelde 2015-05-19 21:21:38 CEST

Whiteboard: (none) => MGA5TOO

Comment 2 Rémi Verschelde 2015-05-19 21:46:55 CEST

Indeed, it looks like mtr 0.85 does not work out of the box, it expects a mandatory HOSTNAME argument, but does not give any output when you omit it. If you start "mtr localhost" or "xmtr localhost", it works fine.

Looking at the upstream NEWS [1], it looks like it's indeed a bug that was fixed in 0.86 ("Fixed default hostname logic.").

I've tested it locally and indeed, now "mtr" or "xmtr" without argument work fine. I'll ask for a freeze push.

[1] https://github.com/traviscross/mtr/blob/master/NEWS

Rémi Verschelde 2015-05-19 22:14:43 CEST

Summary: xmtr does not run => xmtr does not run with default arguments

Comment 3 Rémi Verschelde 2015-05-19 23:27:02 CEST

Should be fixed with mtr-0.86-1.mga5.

Assignee: bugsquad => rverschelde
Whiteboard: MGA5TOO => (none)

Comment 4 Rémi Verschelde 2015-05-19 23:27:12 CEST

Resolved even :)

Status: NEW => RESOLVED
Resolution: (none) => FIXED