`exo-open --launch` fails to pass parameters

Bug #1480768 reported by Shahar Or
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Exo
Fix Released
Medium
exo (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

See attached screen shot

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: exo-utils 0.10.6-1
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic x86_64
ApportVersion: 2.18-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Aug 3 08:31:21 2015
InstallationDate: Installed on 2010-10-12 (1755 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: exo
UpgradeStatus: Upgraded to wily on 2014-11-11 (264 days ago)

Revision history for this message
In , nirik (kevin-scrye) wrote :

Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=870621

"Description of problem:
Specifiing command (in terminal launcher):
 "exo-open --launch TerminalEmulator --tab --tab --tab"

result in error:

exo-helper: Unknown option --tab --tab --tab.
Type 'exo-helper --help' for usage.

although right action should be start preferred terminal app with "--tab --tab --tab" as its parameters."

Revision history for this message
In , Bluesabre-1 (bluesabre-1) wrote :

*** Bug 9315 has been marked as a duplicate of this bug. ***

Revision history for this message
Shahar Or (mightyiam) wrote :
Revision history for this message
In , Skunnyk-q (skunnyk-q) wrote :

*** Bug 13453 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Gitbot (gitbot) wrote :

Sean Davis referenced this bugreport in commit 21be6acf87c8575fdbe44dd0399583c115368c5c

exo-launch: pass flags to preferred application (Bug 9427), Add exo_str_is_flag to public API

https://git.xfce.org/xfce/exo/commit?id=21be6acf87c8575fdbe44dd0399583c115368c5c

Revision history for this message
In , Bluesabre-1 (bluesabre-1) wrote :

This should now be resolved in the above commit.

Revision history for this message
Theo Linkspfeifer (lastonestanding) wrote :

This bug was fixed upstream in version 0.11.5, and therefore does not affect Ubuntu 18.04 (0.12.0).

Changed in exo (Ubuntu):
status: New → Fix Released
Changed in exo:
importance: Unknown → Medium
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.