Bug 219366

Summary: (gnome-panel) Copies broken relative symlinks to desktop
Product: Red Hat Enterprise Linux 5 Reporter: Warren Togami <wtogami>
Component: gnome-panelAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.0CC: wtogami
Target Milestone: ---Flags: pm-rhel: needinfo? (wtogami)
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-02 13:17:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Warren Togami 2006-12-12 19:56:20 UTC
If you copy a .desktop launcher to the desktop that is a relative symlink, it
places a broken relative symlink on the desktop.

RHEL5 evolution-2.8.0-25.el5 is an example that helps us demonstrate this
problem.  This is not actually an evolution bug.

Example Procedure:
1) Applications
2) Internet
3) Right-click "Email"
4) "Add this launcher to desktop"

Broken relative symlink is placed on your desktop.

Proposed Fix:
Why not have gnome-panel instead COPY the target .desktop file.  Then the user
is empowered to modify or rename it if they wish.  Problem averted.

Placing an absolute symlink that you cannot modify or rename on the desktop is
another case that this proposed fix would improve.

Comment 1 RHEL Product and Program Management 2014-03-07 13:42:36 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 2 RHEL Product and Program Management 2014-06-02 13:17:12 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).