Bug 4648

Summary:	GSD fails to start beacuse .desktop file does not match moved files
Product:	Mageia	Reporter:	Juan Magallon <jamagallon>
Component:	RPM Packages	Assignee:	Olav Vitters <olav>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	Normal	CC:	jamagallon, mageia, mageia, olav
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	gnome-settings-daemon-3.3.90.1-1.mga2.src.rpm	CVE:
Status comment:

Description Juan Magallon 2012-02-23 00:14:22 CET

GDM and startx can't start because they can't connect to GSD.
GSD is not launched because binay file has moved into a
directory called /usr/lib64/gnome-settings-daemon
(which was previously just the binary).
So /etc/xdg/autostart/gnome-settings-daemon.desktop points to
a directory:

-Exec=/usr/lib64/gnome-settings-daemon
+Exec=/usr/lib64/gnome-settings-daemon/gnome-settings-daemon

Changed in my box and all is up and running again ;)

Comment 1 Juan Magallon 2012-02-23 09:13:08 CET

Well, or some 'install path' is wrong in build scripts and should
be just /usr/lib64....
That looks more feasible.

CC: (none) => jamagallon

Comment 2 Jani Välimaa 2012-02-23 16:35:27 CET

*** Bug 4659 has been marked as a duplicate of this bug. ***

CC: (none) => mageia

Comment 3 Olav Vitters 2012-02-23 17:20:31 CET

Seems like upstream bug. want to fix this properly..

CC: (none) => olav
Assignee: bugsquad => olav

Comment 4 Damien Lallement 2012-02-23 18:07:55 CET

Perhaps we can push a temporary "gnome-settings-daemon" package and fix it properly after as, for now, cauldron with GNOME is completly broken and we risk to have a lot of bug reports about this issue.
My 2 cts. :-)

Status: NEW => ASSIGNED

Comment 5 Olav Vitters 2012-02-23 20:00:01 CET

Submitted a -2 release.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Comment 6 Juan Magallon 2012-02-24 02:49:47 CET

That -2 relase looks exactly the same as before ??

Comment 7 Olav Vitters 2012-02-24 09:56:59 CET

Are you sure? For me the .services file now points to the right place?

Comment 8 Olav Vitters 2012-02-24 09:57:36 CET

Ah.. two places reference this

Status: RESOLVED => UNCONFIRMED
Resolution: FIXED => (none)
Ever confirmed: 1 => 0

Comment 9 Olav Vitters 2012-02-24 10:02:55 CET

-3 submitted

There was also an upstream patch, but that didn't work for me.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => FIXED

Comment 10 Juan Magallon 2012-02-24 10:18:11 CET

Ah, I was not aware of the .services file, I always talked about the .desktop file ;)

Comment 11 Colin Guthrie 2012-03-06 14:03:22 CET

Seems this has resurfaced in the new version (it seems the binary was moved back again to it's original location thus making the patch redundant!)

I'll remove the patch and resubmit.

CC: (none) => mageia