On Fri, 2014-10-03 at 20:34 +0200, Armin K. wrote: > > Error verifying signature: Failed > to execute gpg. > On 10/03/2014 07:46 PM, Christopher Gregory wrote: > > On Sat, October 4, 2014 6:32 am, Armin K. wrote: > >> On 10/03/2014 07:19 PM, Christopher Gregory wrote: > >> > >>> Hello, > >>> > >>> > >>> Well after re-installing all of gnome once, and testing and then > >>> re-installing up to gdm (minus rebuilding the webkits) I still have the > >>> wonderful error message of oops something went wrong and the system > >>> could not recover. > >>> > >>> Whoever put that in gnome should be horse wipped. > >>> > >>> > >>> Looking at the journal log files I find the below wonderful error: > >>> > >>> > >>> Oct 04 06:01:17 lfs systemd-timesyncd[172]: > >>> interval/delta/delay/jitter/drift 128s/+0.001s/0.191s/0.001s/+4ppm Oct 04 > >>> 06:01:15 lfs gnome-session[433]: Entering running state > >>> Oct 04 06:01:15 lfs gnome-session[433]: WARNING: Unable to find required > >>> component 'gnome-settings-daemon' Oct 04 06:01:15 lfs > >>> gnome-session[433]: gnome-session[433]: WARNING: > >>> Unable to find required component 'gnome-settings-daemon' > >>> Oct 04 06:01:15 lfs org.a11y.atspi.Registry[444]: SpiRegistry daemon is > >>> running with well-known name - org.a11y.atspi.Registry Oct 04 06:01:15 > >>> lfs org.a11y.Bus[437]: Successfully activated service > >>> 'org.a11y.atspi.Registry' > >>> Oct 04 06:01:15 lfs org.a11y.Bus[437]: Activating service > >>> name='org.a11y.atspi.Registry' > >>> > >>> Now this is just plain BS. gnome-settings-daemon is most certainly > >>> installed. I even checked all of the directories mentioned in the > >>> gnome-settings-daemon.pc file. > >>> > >>> All I get on a google search is rubbish from the distros about have you > >>> deleted it blah blah blah, which is also years old. Nothing new and > >>> or relevant. > >>> > >>> Failing a complete re-install of lfs and then blfs I am unable to solve > >>> this. > >>> > >>> I really do not fancy another week or so re-installing. > >>> > >>> > >>> I am not even sure if re-compiling gnome-session with debugging symbols > >>> would be helpful. > >>> > >>> I get the exact same error if I disable the display manager, reboot and > >>> login at console, manually startx and run gnome-session. > >>> > >>> This time it is not gdm at fault. That starts up and displays > >>> correctly. > >>> > >>> Any thoughts on this? > >>> > >>> > >>> Regards, > >>> > >>> > >>> Christopher. > >>> > >>> > >> > >> I suppose XDG_CONFIG_DIRS is set to something that doesn't include /etc. > >> That's a major issue when KDE is also installed. > >> > >> > >> -- > >> Note: My last name is not Krejzi. > > > > Hello Armin, > > > > I have just solved it. In this case it is a failure on the installers > > part of gnome-settings-daemon. > > > > It did not copy the gnome-settings-daemon.desktop into > > /usr/share/applications during install as it was meant to. > > > > I ran gnome-session --debug and it went through the process of looking for > > the components and failed. I then looked in the /usr/share/applications > > directory and found it was indeed missing. Copying it from the /data > > directory of the source code fixed it. > > > > Now to put that little gem onto the page so that it will not frustrate > > others. > > > > Regards, > > > > Christopher. > > > > The file is installed in /etc/xdg/autostart, not in > /usr/share/applications. As I said, XDG_CONFIG_DIRS does not seem to > include /etc/xdg on your system.
Hello Armin, I just looked and indeed the file is installed in /etc/xdg/autostart, so I just reverted the change I made to the page. I just added /etc/xdg XDG_CONFIG_DIRS to extrapaths.sh so that should solve other issues as well. The thing is with copying it to /usr/share/applications it did work when I re-enabled gdm and rebooted. Regards, Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
