Bug 17238 - Gnome Shell misses .desktop file
Summary: Gnome Shell misses .desktop file
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Olav Vitters
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-27 08:59 CET by Juan Magallon
Modified: 2015-12-15 18:08 CET (History)
1 user (show)

See Also:
Source RPM: gnome-shell-3.19.2-2.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Juan Magallon 2015-11-27 08:59:50 CET 
After latest gnome-shell update, login in gnome filed because of:

Nov 27 08:45:38 werewolf.home gnome-session[2663]: gnome-session-binary[2663]: WARNING: Unable to find required component 'gnome-shell'
Nov 27 08:45:38 werewolf.home gnome-session-binary[2663]: WARNING: Unable to find required component 'gnome-shell'

I checked that gnome-shell does not provide any gnome-shell.desktop file:

werewolf:~# rpm -ql gnome-shell | grep desktop
/usr/share/applications/evolution-calendar.desktop
/usr/share/applications/gnome-shell-extension-prefs.desktop
/usr/share/applications/org.gnome.Shell.PortalHelper.desktop
/usr/share/applications/org.gnome.Shell.desktop
/usr/share/gnome-shell/xdg-override/autostart/org.gnome.Shell.desktop

Copying org.gnome.Shell.desktop to gnome-shell.desktop and adding
a 'gnome-shell' to X-GNOME-Provides fixed the issue.

Or the requirements in RequiredComponents for sessions in
/usr/share/gnome-session/sessions should be changed, or the name of the
desktop file is wrong.
Or I missunderstand everything ;).


Reproducible: 

Steps to Reproduce:
Thierry Vignaud 2015-11-30 13:09:04 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => olav

Comment 1 Olav Vitters 2015-12-15 18:08:38 CET 
Urgh, missed this bug. Someone fixed it for me and uploaded a new version. Forgot which it was, IIRC gnome-session needed to be updated.

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.