This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes
Bug 80695 - Cannot modify command for Launcher on Desktop
Cannot modify command for Launcher on Desktop
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: nautilus (Show other bugs)
8.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Jay Turner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-29 20:40 EST by jw1233219
Modified: 2015-01-07 19:02 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-16 06:11:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description jw1233219 2002-12-29 20:40:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98; hahaha-fooled you!
This is really Mozilla/5.0 on Linux i686 rv:1.0.1 Gecko/2002103)

Description of problem:
After creating a New Launcher on desktop there is no way to modify  the command
associated with it.


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


How reproducible:
Always

Steps to Reproduce:
1. Right-click on desktop and select "New Launcher"
2. Fill in the dialog and click OK
3. Select the icon on desktop and right-click
4. Select Properties

    

Actual Results:  No ability to edit the command attached to Launcher


Expected Results:  Ability to edit command associated with a Launcher on desktop


Additional info:

MS is safe for the moment, I think
Comment 1 Alexander Larsson 2003-01-16 06:11:00 EST
This is basically a dup of
http://bugzilla.gnome.org/show_bug.cgi?id=83964
in the gnome bugzilla. I'm marking it WONTFIX here, as I prefer to use the
upstream bug tracker for "enhancement" bugs. That means more people see it an it
has a larger chance of getting fixed.


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