Bug 596440 - desktop file lacks a TryExec line
Summary: desktop file lacks a TryExec line
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: thunderbird
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jan Horak
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-26 18:35 UTC by Ray Strode [halfline]
Modified: 2010-11-10 21:46 UTC (History)
3 users (show)

Fixed In Version: thunderbird-3.0.5-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 21:46:46 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ray Strode [halfline] 2010-05-26 18:35:22 UTC
The desktop file for thunderbird lacks a tryexec line.  This means if the desktop file is copied to a system that lacks thunderbird installed (say in the users ~/.local or ~/.gnome2/panel.d) you'll get a broken icon instead of a nice, dynamically hidden icon.

Comment 2 RHEL Program Management 2010-05-26 21:26:16 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 3 Christopher Aillon 2010-05-26 22:59:41 UTC
Should it replace the Exec line or should it be additional?

Comment 4 Jan Horak 2010-06-01 11:33:38 UTC
Additional. It's going to be included in 3.0.5 security update.

Comment 5 Vladimir Benes 2010-06-30 15:54:17 UTC
TryExec is present
-> VERIFIED

Comment 6 releng-rhel@redhat.com 2010-11-10 21:46:46 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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