Bug 23985 - No LXDE menu entry for Openbox Configuration Manager, which is present & works from command line.
Summary: No LXDE menu entry for Openbox Configuration Manager, which is present & wor...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Nicolas Salguero
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-10 20:28 CET by Lewis Smith
Modified: 2018-12-12 17:59 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Lewis Smith 2018-12-10 20:28:30 CET
Description of problem:
LXDE desktop (1 of 5). No menu entry (say Tools or ../System tools) for the Openbox Config Manager. However, this *is* present on the system
 obconf-2.0.4-8.mga7
and works from command line (but you have to know): $ obconf
Just a missing menu entry. Present in all other desktops.

Version-Release number of selected component (if applicable):
M7beta1 4 Jan 2018, Classic ISO.

Steps to Reproduce:
1. Search all menus in vain.
Comment 1 Marja Van Waes 2018-12-11 20:06:18 CET
(In reply to Lewis Smith from comment #0)

> Just a missing menu entry. Present in all other desktops.

That's odd, I'm trying to understand why it's only missing in LXDE

Is it also missing for a new user you add?

Assignee: bugsquad => nicolas.salguero
CC: (none) => marja11

Comment 2 Nicolas Salguero 2018-12-12 15:13:19 CET
Hi,

In my tests under a fully updated x86_64 Cauldron VM, with only LXDE, I see the menu entry for obconf under "Tools" section, either with an old user or with a new one.

Can another desktop have an impact over /etc/xdg/menus/applications.menu, for example?

Best regards,

Nico.
Comment 3 Lewis Smith 2018-12-12 17:59:00 CET
(In reply to Nicolas Salguero from comment #2)
> In my tests under a fully updated x86_64 Cauldron VM, with only LXDE, I see
> the menu entry for obconf under "Tools" section
Now, so do I! It was disguised by a translation... And it works. Sorry to you & Marja for the unnecessary noise; doing too much. Closing as Invalid.

Resolution: (none) => INVALID
Status: NEW => RESOLVED


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