How to reproduce: - Install the latest KDE 4.2.0 from kde-redhat-testing * - Install any GUI application that comes with a /usr/share/applications/*.desktop file via yum
Actual result: The application doesn't appear in the KDE menu until re-login
Expected result: The application shows up in the KDE menu rightaway (well maybe with a slight delay, but surely one shouldn't have to log out and back in).
I am 90% sure that this problem didn't exist in KDE 4.1.9? versions. Can you confirm this?
Orcan
$ rpm -qa | grep kde kdeutils-4.2.0-1.fc10.x86_64 kdelibs3-3.5.10-3.fc10.x86_64 kdemultimedia-libs-4.2.0-1.fc10.1.x86_64 licq-kde-1.3.5-4.fc10.x86_64 kdebase3-pim-ioslaves-3.5.10-4.fc10.x86_64 kdegraphics-libs-4.2.0-1.fc10.x86_64 kdepim-libs-4.2.0-2.fc10.x86_64 kdelibs-common-4.2.0-4.fc10.x86_64 kdesdk-libs-4.2.0-1.fc10.x86_64 kdegames-4.2.0-1.fc10.x86_64 kdeplasma-addons-4.2.0-1.fc10.x86_64 kde-filesystem-4-23.fc10.noarch solar-kde-theme-0.1.17-1.fc10.noarch kdebase3-3.5.10-4.fc10.x86_64 kdenetwork-libs-4.2.0-1.fc10.x86_64 kdesdk-4.2.0-1.fc10.x86_64 kdebase-runtime-libs-4.2.0-3.fc10.x86_64 kdepim-4.2.0-2.fc10.x86_64 kdebase-workspace-libs-4.2.0-2.fc10.x86_64 kdebase3-libs-3.5.10-4.fc10.x86_64 kdepimlibs-4.2.0-1.fc10.x86_64 kde-settings-kdm-4.1-5.20090126svn.fc10.noarch kdeartwork-4.2.0-1.fc10.x86_64 kde-settings-4.1-5.20090126svn.fc10.noarch kdegames-libs-4.2.0-1.fc10.x86_64 kdeaccessibility-4.2.0-1.fc10.x86_64 kdebase-runtime-4.2.0-3.fc10.x86_64 kdebase-4.2.0-2.fc10.x86_64 kde-settings-pulseaudio-4.1-5.20090126svn.fc10.noarch kdebase-workspace-4.2.0-2.fc10.x86_64 kdelibs-4.2.0-4.fc10.x86_64 kdegraphics-4.2.0-1.fc10.x86_64 kdemultimedia-4.2.0-1.fc10.1.x86_64 kde-plasma-quickaccess-0.7.1-7.fc10.x86_64 kdenetwork-4.2.0-1.fc10.x86_64 kdebase-libs-4.2.0-2.fc10.x86_64 kdesdk-utils-4.2.0-1.fc10.x86_64
Le Thursday 29 January 2009 08:18:04 Orcan Ogetbil, vous avez écrit :
fresh installed GUI application does not appear in KDE menu
does they appear if you do a kbuildsycoca4 and then look on the menu ?
It seems there is a pb here because a mandriva user reported this issue too, and we didn't had this issue before.
On Thu, Jan 29, 2009 at 2:28 AM, Nicolas Lécureuil wrote:
Le Thursday 29 January 2009 08:18:04 Orcan Ogetbil, vous avez écrit :
fresh installed GUI application does not appear in KDE menu
does they appear if you do a kbuildsycoca4 and then look on the menu ?
It seems there is a pb here because a mandriva user reported this issue too, and we didn't had this issue before.
yes, they appeared when I did a kbuildsycoca4. side-info: When I remove GUI applications via yum, their menu entries stay (until re-login or kbuildsycoca4) but their icons are gone. Only a question mark shows up.
Orcan
Orcan Ogetbil schrieb:
I am 90% sure that this problem didn't exist in KDE 4.1.9? versions. Can you confirm this?
Yes, I encounter a similiar problem with installing plasmoids. They didn't appear in the plasmoid list and I thought it might be a problem with packaging. However, if you run "kbuildsycoca4" they appear. Looks like something went broken between RC1 and final.
Florian Sievert wrote:
Orcan Ogetbil schrieb:
I am 90% sure that this problem didn't exist in KDE 4.1.9? versions. Can you confirm this?
Yes, I encounter a similiar problem with installing plasmoids. They didn't appear in the plasmoid list and I thought it might be a problem with packaging. However, if you run "kbuildsycoca4" they appear. Looks like something went broken between RC1 and final.
Boo, I think I can confirm it here too.
Any upstream pinging/bugs going on yet?
-- Rex
Hi,
Boo, I think I can confirm it here too. Any upstream pinging/bugs going on yet?
Nope. Until yesterday evening I thought I did something wrong. I just did a fast search on bko, but didn't find anything that might sounds like this problem. However, I am not even sure, how to debug this problem. Sound strange, if this would be an upstream bug... I would expect lots of noise about something like this.
Florian Sievert wrote:
Boo, I think I can confirm it here too. Any upstream pinging/bugs going on yet?
Nope. Until yesterday evening I thought I did something wrong. I just did a fast search on bko, but didn't find anything that might sounds like this problem.
Looks like the awareness of the issue has been raised, so that should no longer be a problem, but for tracking purposes, I just filed, http://bugs.kde.org/show_bug.cgi?id=182472
-- Rex
Hi Rex,
Looks like the awareness of the issue has been raised, so that should no longer be a problem, but for tracking purposes, I just filed, http://bugs.kde.org/show_bug.cgi?id=182472
Impressive how you find everything in bko. ;) However, this is a bug in the final version of kde 4.2.0? I guess that we won't wait for 4.2.1 for this kind of fix and an update will be pushed soon? This issue is pretty nast. Thanks for your good work!
Best regards, Florian
Dne Saturday 31. of January 2009 09:33:32 Florian Sievert napsal(a):
Hi Rex,
Looks like the awareness of the issue has been raised, so that should no longer be a problem, but for tracking purposes, I just filed, http://bugs.kde.org/show_bug.cgi?id=182472
Impressive how you find everything in bko. ;) However, this is a bug in the final version of kde 4.2.0? I guess that we won't wait for 4.2.1 for this kind of fix and an update will be pushed soon? This issue is pretty nast. Thanks for your good work!
Our packages (kdelibs-4.2.0) will contain a fix for this problem, no worry :)
Lukáš Tinkl wrote:
Dne Saturday 31. of January 2009 09:33:32 Florian Sievert napsal(a):
Hi Rex,
Looks like the awareness of the issue has been raised, so that should no longer be a problem, but for tracking purposes, I just filed, http://bugs.kde.org/show_bug.cgi?id=182472
Impressive how you find everything in bko. ;) However, this is a bug in the final version of kde 4.2.0? I guess that we won't wait for 4.2.1 for this kind of fix and an update will be pushed soon? This issue is pretty nast. Thanks for your good work!
Our packages (kdelibs-4.2.0) will contain a fix for this problem, no worry :)
kdelibs-4.2.0-7 has the fix.
-- Rex