Lost Desktop After Updates

Anything that pertains to Entropy, Equo or Sulfur

Moderator: Moderators

Post Reply
Posts: 9051
Joined: Sat Jan 14, 2006 0:55
Location: Midwest USA

Lost Desktop After Updates

Post by wolfden » Mon Dec 14, 2009 10:03

Ok, we got a million and one threads on this. If you did the last two big updates and suddenly find yourself at desktop prompt, but can do ctrl alt f7 and can find the login screen than you need to modify a file. You will need to be root to edit this file.

at your prompt:
enter your root password when prompt


nano /etc/init.d/nfs

now u need to add a simple line

scroll down till u see mnotify=/usr/sbin/sm-notify

after that insert the line

sleep 15

so it should look something like:

Code: Select all

# Copyright 1999-2009 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/net-fs/nfs-utils/files/nfs.initd,v 1.19 2009/05/30 22:01:43 vapier Exp $


# This variable is used for controlling whether or not to run exportfs -ua;
# see stop() for more information

# The binary locations

sleep 15

depend() {
	local myneed=""
	if [ -e /etc/exports ] ; then
		if awk '!/^[[:space:]]*#/ && $2 ~ /sec=/ { exit 0 } END { exit 1 }' /etc/exports ; then
			myneed="${myneed} rpc.svcgssd"
	config /etc/exports
	need portmap rpc.statd ${myneed} ${NFS_NEEDED_SERVICES}
	use ypbind net dns rpc.rquotad rpc.idmapd rpc.svcgssd
	after quota

mkdir_nfsdirs() {
	local d
	for d in rpc_pipefs v4recovery v4root ; do
		[ ! -d "${d}" ] && mkdir -p "${d}"

waitfor_exportfs() {
	local pid=$1
	( sleep ${EXPORTFS_TIMEOUT:-30}; kill -9 $pid 2>/dev/null ) &
	wait $1

mount_nfsd() {
	if [ -e /proc/modules ] ; then
		# Make sure nfs support is loaded in the kernel #64709
		if ! grep -qs nfsd /proc/filesystems ; then
			modprobe -q nfsd
		# Restart idmapd if needed #220747
		if grep -qs nfsd /proc/modules ; then
			killall -q -HUP rpc.idmapd

	# This is the new "kernel 2.6 way" to handle the exports file
	if grep -qs nfsd /proc/filesystems ; then
		if ! grep -qs "nfsd /proc/fs/nfsd" /proc/mounts ; then
			ebegin "Mounting nfsd filesystem in /proc"
			mount -t nfsd -o nodev,noexec,nosuid nfsd /proc/fs/nfsd
			eend $?

start_it() {
	ebegin "Starting NFS $1"
	"[email protected]"
	eend $?
	ret=$((ret + $?))
start() {

	# Exportfs likes to hang if networking isn't working.
	# If that's the case, then try to kill it so the
	# bootup process can continue.
	if grep -qs '^[[:space:]]*/' /etc/exports ; then
		ebegin "Exporting NFS directories"
		${exportfs} -r &
		waitfor_exportfs $!
		eend $?

	local ret=0
	start_it mountd ${mountd} ${OPTS_RPC_MOUNTD}
	start_it daemon ${nfsd} ${OPTS_RPC_NFSD}
	[ -x "${smnotify}" ] && start_it smnotify ${smnotify} ${OPTS_SMNOTIFY}
	return ${ret}

stop() {
	local ret=0

	# Don't check NFSSERVER variable since it might have changed,
	# instead use --oknodo to smooth things over
	ebegin "Stopping NFS mountd"
	start-stop-daemon --stop --oknodo --exec ${mountd}
	eend $?
	ret=$((ret + $?))

	# nfsd sets its process name to [nfsd] so don't look for $nfsd
	ebegin "Stopping NFS daemon"
	start-stop-daemon --stop --oknodo --name nfsd --user root --signal 2
	eend $?
	ret=$((ret + $?))
	# in case things don't work out ... #228127
	rpc.nfsd 0

	# When restarting the NFS server, running "exportfs -ua" probably
	# isn't what the user wants.  Running it causes all entries listed
	# in xtab to be removed from the kernel export tables, and the
	# xtab file is cleared. This effectively shuts down all NFS
	# activity, leaving all clients holding stale NFS filehandles,
	# *even* when the NFS server has restarted.
	# That's what you would want if you were shutting down the NFS
	# server for good, or for a long period of time, but not when the
	# NFS server will be running again in short order.  In this case,
	# then "exportfs -r" will reread the xtab, and all the current
	# clients will be able to resume NFS activity, *without* needing
	# to umount/(re)mount the filesystem.
	if [ "${restarting}" = no -o "${RC_CMD}" = "restart" ] ; then
		ebegin "Unexporting NFS directories"
		# Exportfs likes to hang if networking isn't working.
		# If that's the case, then try to kill it so the
		# shutdown process can continue.
		${exportfs} -ua &
		waitfor_exportfs $!
		eend $?

	return ${ret}

reload() {
	# Exportfs likes to hang if networking isn't working.
	# If that's the case, then try to kill it so the
	# bootup process can continue.
	ebegin "Reloading /etc/exports"
	${exportfs} -r 1>&2 &
	waitfor_exportfs $!
	eend $?

restart() {
	# See long comment in stop() regarding "restarting" and exportfs -ua
than hit ctrl x and than Y when it asks.

Now when u reboot, you should be good to go.

if you can't figure out nano

Normally you should be able to start the desktop as root
/etc/init.d/xdm restart

now you should get the login box

edit the /etc/init.d/nfs file the way you prefer as root.

I seriously recommend getting yourself familiar with nano as it will save you a lot of troubles when running a bleeding edge distro.

Growing Hen
Posts: 112
Joined: Sun Nov 23, 2008 4:21

Re: Lost Desktop After Updates

Post by tonyawards » Wed Dec 16, 2009 7:01

Thank you, wolfden. I've been trying to figure that one out for a week or more. Very much obliged.
SL Version: XI+, just rollin' along / Kernel 3.8.3 | KDE 4.10.1 | HP dv6000z | AMD Turion64 MK-36 | 2GB RAM | nVidia GeForce 6150

User avatar
Sagely Hen
Posts: 1923
Joined: Fri Nov 16, 2007 1:15
Location: Ribeirão Preto City, São Paulo State, Brazil

Re: Lost Desktop After Updates

Post by albfneto » Wed Dec 16, 2009 15:56

Thanks... this solve threads of many people!
[email protected]
Favorite Distros: Sabayon, Gentoo, Mageia and OpenSUSE

Post Reply