Bug 1217564

Summary: LXQt lists Yumex in Settings menu instead of System Tools
Product: [Fedora] Fedora Reporter: Raphael Groner <projects.rg>
Component: lxqt-panelAssignee: Helio Chissini de Castro <helio>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: rawhideCC: helio, projects.rg, rdieter, ti.eugene, tim.lauridsen
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1217565 (view as bug list) Environment:
Last Closed: 2015-05-07 09:49:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1217565    
Attachments:
Description Flags
desktop file without Settings in Categories none

Description Raphael Groner 2015-04-30 16:11:46 UTC
Created attachment 1020656 [details]
desktop file without Settings in Categories

Description of problem:
LXQt lists Yumex in Settings menu instead of System Tools. Other desktops do list in Administration.

Version-Release number of selected component (if applicable):
-

How reproducible:
yes

Steps to Reproduce:
1. login into LXQt session
2. open application menu
3. go to System Tools group

Actual results:
no Yumex listed inside the System Tools

Expected results:
Yumex entry inside the System Tools

Additional info:
LXQt seems to prefer Settings before System in desktop file's Categories entry

Comment 1 Raphael Groner 2015-04-30 16:12:37 UTC
Informal CC to the LXQt packages maintainer.

Comment 2 Tim Lauridsen 2015-05-06 12:53:16 UTC
this should be fixed in LXQt, cant fix it in yumex

Comment 3 Raphael Groner 2015-05-07 09:47:49 UTC
(In reply to Tim Lauridsen from comment #2)
> this should be fixed in LXQt, cant fix it in yumex

Reassigning then to LXQt. Probably a fix from upstream is required.

Comment 4 Raphael Groner 2015-05-07 09:49:45 UTC

*** This bug has been marked as a duplicate of bug 1217565 ***