Bug 145204 - after recent update GIMP is listed twice in KDE menu
Summary: after recent update GIMP is listed twice in KDE menu
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 3
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-15 09:49 UTC by Paul Osmialowski
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-01-25 12:22:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul Osmialowski 2005-01-15 09:49:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
after recent update GIMP is listed twice in KDE graphics applications
menu. As I've checked, one entry has all fields empty in its
properties (so nothing is started when its clicked). Also I've logged
into my friends account who is using GNOME on the same host and there
was only one GIMP entry (the right one) in his GNOME menu.


Version-Release number of selected component (if applicable):
gimp-2.2.2-0.fc3.2 gimp-2.2.2-0.fc3.2

How reproducible:
Didn't try

Steps to Reproduce:
1. Upgrade gimp to 2.2.2-0.fc3.2 version
2.
3.
    

Actual Results:  GIMP is listed twice in KDE graphics applications
menu, one of the two entries has empty fields (nothing is started when
its clicked)

Expected Results:  only one GIMP icon should be in KDE applications menu

Additional info:

Comment 1 Nils Philippsen 2005-01-15 10:26:33 UTC
This is very likely a bug in the KDE panel (or whatever code creates that menu).
Maybe it copies some info about the application entries over into the user's
configuration (just a guess).

Reassigning to kdebase.

Comment 2 Than Ngo 2005-01-25 12:22:02 UTC
it looks like you have old broken ginmp desktop files in your
$HOME/.kde/share/applnk or /usr/share/applnk. Please remove the old broken one.

I works fine for me.



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