Christopher Gregory wrote:
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.
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.
I get the exact same error if I disable the display manager, reboot and login at console, manually startx and run gnome-session.
I don't know much about Gnome, but I'd say one of thwo things could cause the problem:
1. A run time library or executable is not available where the app is looking.
2. There needs to be some service running via dbus that is not available. That could possibly indicate some kind of race condition.
I'll download the source for gnome-session and gnome-settings-daemon and see if I can see anything. In the meantime, check ldd for both to see if they find all their dependent libraries.
-- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
