Bug 505569 - xfrun4 does not accept command line arguments anymore
xfrun4 does not accept command line arguments anymore
Product: Fedora
Classification: Fedora
Component: xfce-utils (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Kevin Fenzi
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-06-12 09:40 EDT by Josh Cogliati
Modified: 2010-06-28 08:55 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 08:55:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Xfce 5478 None None None Never

  None (edit)
Description Josh Cogliati 2009-06-12 09:40:17 EDT
Description of problem:
In xfce 4.4 xfrun4 and the launcher accepted command line arguments for commands run in the terminal.  Now, in 4.6 when they are added the terminal comes up, but it does not ever get to running the command, instead there is a blank terminal window.

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

How reproducible:
Every time 

Steps to Reproduce:
Method 1:
1. run xfrun4.
2. select run in terminal
3. type in the command 'python -i'
Method 2:
1. Add a new launcher
2. select run in terminal
3. type in the command 'python -i'
Method 3:
1. run "terminal -x 'python -i'"
Method 4 (which works as expected)
1. run "terminal -e 'python -i'"

Actual results:
Methods 1-3 result in a terminal with no text.

Expected results:
Method 4 gives the expected result, which is a terminal with the results of python -i.

Any program with arguments causes this, such as 'sftp server'
Comment 1 Kevin Fenzi 2009-06-17 23:28:51 EDT
Yep I see this here as well. ;( 

I have filed an upstream bug on this. 

I can try and dig into the code and see if I can see where it's happening as well. 

Thanks for the report!
Comment 2 Christoph Wickert 2009-09-09 17:53:55 EDT
Behavior has changed with Terminal 0.4.0: 1, 2 and 4 work, 3 gives a blank terminal.
Comment 3 Bug Zapper 2010-04-27 10:49:31 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 WONTFIX if it remains open with a Fedora 
'version' of '11'.

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 prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
Comment 4 Bug Zapper 2010-06-28 08:55:48 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.