Bug 1037568 - No filemanager in menu
Summary: No filemanager in menu
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: razorqt
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Eugene A. Pivnev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-03 11:45 UTC by Rolle
Modified: 2016-01-07 10:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-07 10:27:44 UTC
Type: Bug


Attachments (Terms of Use)

Description Rolle 2013-12-03 11:45:00 UTC
Description of problem:
In RazorQT I couldn't find a filemanager, even the nautilus and nemo filemanagers are installed.
Then I install afterwards pcmanfm, this filemanager has an entry in the menu. If I uninstall nemo and then install nemo again, no menu entry for nemo is created.

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

How reproducible:
always

Steps to Reproduce:
1. Install Fedora with the default desktop (Gnome). I don't know if this first Gnome-Desktop-installation is relevant. So nautilus must be present.
2. if you wish install nemo filemanager.
3. install razorqt
4. logout from gnome and login in razorqt

Actual results:
I didn't find a filemanager in the menu (no nautilus nor nemo, which are already installed, and I can start the filemanager from console)

Expected results:
The filemanager nautilus and nemo must be present in the menu.

Additional info:

Comment 1 Jaroslav Reznik 2015-03-03 15:17:58 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Eugene A. Pivnev 2016-01-07 10:27:44 UTC
The problem is in /usr/shares/applications/*.desktop:

OnlyShowIn=GNOME


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