Bug 68654 - entries to "nowhere"
Summary: entries to "nowhere"
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-panel   
(Show other bugs)
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
Keywords: MoveUpstream, Triaged
Depends On:
TreeView+ depends on / blocked
Reported: 2002-07-12 03:43 UTC by Michal Jaegermann
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-13 02:35:47 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michal Jaegermann 2002-07-12 03:43:34 UTC
Description of Problem:

If I am not interested in a broken bloatware why I am pestered in
~/.xsession-errors with messages like "Unable to open desktop file
applications:///Internet/evolution.desktop for panel launcher: Error reading
file 'applications:///Internet/evolution.desktop': File not found
Unable to open desktop file applications:///Office/redhat-word-processor.desktop
for panel launcher: Error reading file
'applications:///Office/redhat-word-processor.desktop': File not found"

It seems natural that these menu entries should belong to packages which
they advertise instead to be scattered in random places.  In the worst
case a session launch code should be doing elementary checks and not to
attempt to start things which do not exist.

Comment 1 Havoc Pennington 2002-07-12 15:48:50 UTC
It is doing a check, that's why it prints a message when the check fails.
The main reason to print this is that if you're trying to customize the panel
defaults for a lot of users, and you have a typo in your launcher filename, 
it's extremely frustrating to figure out what's going wrong if there are no
error messages.

If this happens every time you log in (instead of just the first time) and there
aren't launchers on the panel in order to remove them, I buy that it's a bug,
but if it just fails to create the launchers the first time, prints an error,
and is silent thereafter, I think it's right to print these so that people
trying to configure the panel don't go nuts wondering why it isn't working.

Comment 2 Havoc Pennington 2003-01-13 02:35:47 UTC
Upstream as http://bugzilla.gnome.org/show_bug.cgi?id=103273

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