Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 198828 - FC5 version of KDE menu does not follow menu-spec
FC5 version of KDE menu does not follow menu-spec
Product: Fedora
Classification: Fedora
Component: kdebase (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2006-07-13 18:29 EDT by Waldo Bastian
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version: 3.5.5-0.1.fc5
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-11-02 08:33:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Waldo Bastian 2006-07-13 18:29:02 EDT
Description of problem:
FC5 includes a menu implementation that does not follow the freedesktop.org menu

Version-Release number of selected component (if applicable):
[bastian@localhost scripts]$ kbuildsycoca --version
Qt: 3.3.5
KDE: 3.5.3-0.2.fc5 Red Hat
KBuildSycoca: 1.1

How reproducible:

Check out the menu spec from fd.o and run the test suite with
MENUTEST="kbuildsycoca --menutest" ./menutest
Actual results:
All tests fail

Expected results:
All tests pass

Additional info:
Comment 1 Rex Dieter 2006-11-02 08:33:49 EST
I've confirmed the menu spec test suite passes with kdebase-3.5.5-0.1.fc5 (see 
also bug #178320):

OK tests:      1 2 3 4 5 6 7 8 9 a b c d e f g h i j k l m n o p q r s t v w x 
33 tests passed, 0 tests failed

>>> Running test u
>>> recursive <MergeFile>s ...
seemed to hang (I left it running for ~5 minutes before giving up)
Comment 2 Rex Dieter 2006-11-02 08:44:47 EST
FYI, test 'u' finally did pass, I just needed more patience.

OK tests:      1 2 3 4 5 6 7 8 9 a b c d e f g h i j k l m n o p q r s t u v w 
x y
34 tests passed, 0 tests failed

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