Bug 1138440

*** Bug 1138438 has been marked as a duplicate of this bug. ***

$ grep ^Categ /usr/share/applications/kde4/kdf.desktop
Categories=Qt;KDE;System;

$ grep ^Categ /usr/share/applications/kde4/kwikdisk.desktop 
Categories=Qt;KDE;System;


$ kbuildsycoca4 --menutest | grep kdf
System/ kde4-kdf.desktop        /usr/share/applications/kde4/kdf.desktop

Applications with Category "System" show up in a System/ menu on kde.

Not sure how xfce maps that Category in its application menus, but if it is not shown anywhere, then that is likely a xfce bug (reassigning).

How can I help on this?

I was able to reproduce the problem logging into an xfce session, then installing kdf.  It did not appear on the menus.

logout/login, and it was now present in System/

I suspect xfce either doesn't support watching for newly-installed programs (ie, those installed after session start), or if it does, that feature may be buggy.

No.  This package is one of the very few that have that problem.  I have installed many from the repos without a problem at all.

Are you saying your experience is different than mine, that even after restarting your session (ie, logout/login), KDiskFree is not present in System/ menu ?

(In reply to Rex Dieter from comment #4)

<snip>

> 
> I suspect xfce either doesn't support watching for newly-installed programs
> (ie, those installed after session start), or if it does, that feature may
> be buggy.

Well, as I understand it, xfce does list applications installed session has started. I will try to take a look.

Ok. Here is the issue.

Xfce menu seems to  ignores the subdirectories in /usr/share/applications.

kdf puts the .desktop file under /usr/share/applications/kde4 which seems to be the cause of the problem. 

Can we add a symlink to /usr/share/applications from .../kde4?

I suppose other applications will also likely face this problem?

Created attachment 934658 [details]
kdf shown in xfce menu

The menu spec allows for subdirectories.  Symlink hacks are not a viable option.

That said, the app displays fine under some circumstances as experienced by both me (after session restart, see comment #4 and the screenshot in comment #9 )

I have referenced this bug at the Xfce forum at http://forum.xfce.org/viewtopic.php?pid=34207#p34207.

Perhaps this will help you as they have run across something similar last year.

Thanks.

Can you please verify and answer my query in comment #6 ?

Sorry, I'm an idiot.  It actually did show up on new system start up.  Sorry about that.

Now has correct name as well.

Still wrong icon, but probably not in package.  Correct one is shown under About.

Thanks.

(In reply to Rex Dieter from comment #10)
> The menu spec allows for subdirectories.  Symlink hacks are not a viable
> option.
> 
> That said, the app displays fine under some circumstances as experienced by
> both me (after session restart, see comment #4 and the screenshot in comment
> #9 )

Symlink was needed in my case probably because I did not restart the system but wanted it updated on the "fly".


(In reply to KitchM from comment #13)
> Sorry, I'm an idiot.  It actually did show up on new system start up.  Sorry
> about that.
> 
> Now has correct name as well.
> 
> Still wrong icon, but probably not in package.  Correct one is shown under
> About.
> 
> Thanks.

So this is not a bug then?

(In reply to Rex Dieter from comment #10)
> The menu spec allows for subdirectories.  Symlink hacks are not a viable
> option.
> 
> That said, the app displays fine under some circumstances as experienced by
> both me (after session restart, see comment #4 and the screenshot in comment
> #9 )

What I meant to say was - I added symlink just to check. Since menu spec allows subdirs, my point is moot. :)

Sorry, Mukundan, but it is a bug.  It should install with all the proper settings and parts already in place for three reasons:
1. The user should not have to restart.
2. The parts should all be there,
3. And the installation should work the same as it does for other programs.

Thanks.

I will try and take a look this weekend.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.