Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 80583 - "copy here" and "link here" of menu entries is the same
"copy here" and "link here" of menu entries is the same
Product: Red Hat Linux
Classification: Retired
Component: kdebase (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-12-28 05:37 EST by Michael Schwendt
Modified: 2007-04-18 12:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-16 09:09:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Schwendt 2002-12-28 05:37:33 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021218

Description of problem:
Drag menu entry "Internet > Web Browser" to the desktop and choose "copy here".
A desktop entry will be created in user's $HOME/Desktop directory as a soft-link
(!) to /usr/share/applications/redhat-web.desktop. Since it is just a link and
not a copied file, the user doesn't have write permission to change the
"Properties" of that desktop entry.

Where is the difference to dragging a menu entry to the desktop and choosing
"link here"? It also creates a link to the desktop file in either
/usr/share/applications or /etc/X11/applnk. I would expect "copy here" to
actually _copy_ the *.desktop file rather than soft-linking it. Copying it would
mean the user could edit the "Properties" of his local copy. 

From a usability point of view, it doesn't look right that "copy here" also
creates only a link just like "link here" does already.

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

How reproducible:
Comment 1 Michael Schwendt 2004-02-16 09:09:33 EST
This is fixed in Fedora Core 1.90 (KDE 3.2.0).

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