SEARCH

Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 2013-02-18 04:04:12

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

[Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

I apologize in advance if this has been covered.  If it has, please just post a link to the proper thread.

Anyway, I've narrowed my problem down.  When I shutdown or reboot, rather than shutting down, I get dropped into the a tty screen.  The tty screen is frozen, so I can't type anything.  The actual shutdown text is on tty7.

However, if I manually unmount a network drive before shutting down/rebooting, it works fine.  I tried the directions on post 15 here:  http://crunchbang.org/forums/viewtopic.php?id=16517, but it didn't work for me.

So, I guess I could use advice either on how to shutdown when a network drive is attached, or a different way to actually unmount a network drive while shutting down.

By the way, other than this problem, Crunchbang works just great on my really old eeepc.  I love it so far.  I love the clean interface, the quick boot up time, the access to Debian libraries.

ETA: This was solved using the link provided in post 18.

Last edited by RitterSport (2013-02-23 21:48:20)

Offline

Help fund CrunchBang, donate to the project!

#2 2013-02-18 14:48:58

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

Hi again.  Sorry for the double post.

Looking at the advice in that other thread, I wonder if the problem is that it's unmounting my network drive asynchronously.  That is, it spawns a new process to run the umount command, but before anything happens, the computer tries to reboot/shutdown.  My python is not what it could be -- is there a simple command to force the script to pause for a half second or something?

Offline

#3 2013-02-18 15:57:55

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

Apologies again, for the triple post.  I'm trying all kinds of things to solve this and I've come up with more possibilities.

I tried running the commands from that other thread directly in python.  The reboot command works as expected (that is, it reboots properly if the network drive has already been unmounted, otherwise it drops me into the TTL screen).

The umount command, however, wants escalated privileges.  Is it possible that it fails in the reboot sequence because it doesn't have escalated privileges?

Anyway, I've really run out ideas now, so I hope someone here can help me out.  I'm happy to embed my password in the python script (I know that's really not recommended) if that will help me escalate the privileges for the umount command.  I can't figure out how to do that, though.

Offline

#4 2013-02-18 16:59:07

xaos52
The Good Doctor
From: Planet of the @s
Registered: 2011-06-24
Posts: 4,602

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

this should work.

Offline

#5 2013-02-18 17:25:47

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

xaos52 wrote:

this should work.

Assuming you mean adding a menu option to execute "sudo shutdown -r now", that won't work.  If I type that from a terminal window, it shuts down to the TTY screen if there's a network drive mounted.  If the network drive is not mounted, then it reboots/shuts down properly (the same as the standard way of shutting down).

Maybe you mean removing the password request from the umount command?  I can give that a try, I guess.

Offline

#6 2013-02-18 18:41:46

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

No luck.   That is, I wasn't able to have umount stop asking for a password.  I've never used visudo, so it's very possible I did something wrong.

Offline

#7 2013-02-18 20:03:26

fatmac
#! Die Hard
Registered: 2012-11-14
Posts: 1,948

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

It used to be that you were expected to disconnect from the network before you logged out, so why not just unmount the network drive before logging out?


Linux since 1999
Currently:  AntiX, & Crunchbang.
A good general beginners book for Linux :- http://rute.2038bug.com/index.html.gz
A good Debian read :- http://debian-handbook.info/get/now/

Offline

#8 2013-02-18 20:28:27

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

Sure, that's a workaround.  Is there any way to have it automatically disconnect that drive, though?  Opening up a terminal window and typing sudo umount with the drive location, then entering the password, is a bit of a pain.  I'd rather just hold down the power button, really.

So far, other than this, Crunchbang has been great on my really old eeePC -- all the drivers work, networking, etc., all works great.  I'd love to get this working more smoothly as well.

Offline

#9 2013-02-18 20:39:10

dura
Bloated Gimp
From: interzone
Registered: 2012-09-15
Posts: 2,107

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

For my own reference, this isn't a Crunchbang problem, nor is fatmac's suggestion a workaround. It is use that is creating the problem.

What does:

terminator -x umount -a && sudo halt

do when added through obmenu?

Offline

#10 2013-02-18 23:00:24

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

I tried changing cb-exit so that choosing Reboot calls os.system with that command, no luck.  Then, I ran it from a terminal window and got this:

** (terminator:2374): WARNING **: Binding '<Shift><Control>a' failed!
Unable to bind hide_window key, another instance/window has it.

Then it asked for my password.  Entering the password will allow it to logout, and it hangs up at the TTY window (unless the network drive is disconnected, then it reboots).

Is there another way I should try it?

Offline

#11 2013-02-20 00:49:49

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

A friend suggested that the problem may be that the network drive was considered in use since I had mounted it to my home directory, rather than the mnt directory.  So, I changed the mounting point, but it still hangs up on reboot/shutdown if it's mounted (also, I created a link to the network mount in my home directory -- he assured me that should be ok).  No luck there.

Then, he mentioned maybe doing something in rc.local, to disconnect the drive as part of the kill processes.  He's a Red Hat guy, not a Debian guy, so he wasn't sure exactly what to do in Debian land.  Any suggestions?  Any other ideas?

If I have to, I'm OK with embedding my password in a python script or something in order to raise the privileges and do the umount.  I know that's a bad idea, but this computer never leaves my house and I don't keep anything important on it.

Offline

#12 2013-02-20 11:43:30

xaos52
The Good Doctor
From: Planet of the @s
Registered: 2011-06-24
Posts: 4,602

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

No need to bury your password in the python script.

Just edit /etc/pam.d/common-session:

# here are the per-package modules (the "Primary" block)
session	[default=1]			pam_permit.so
# here's the fallback if no module succeeds
session	requisite			pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
session	required			pam_permit.so
# Allow a normal user to shutdown te system                    <---
session required                        pam_loginuid.so        <---
# and here are more per-package modules (the "Additional" block)
session	required	pam_unix.so 
session	optional			pam_ck_connector.so nox11
# end of pam-auth-update config

Add the two lines marked with the arrows.

Your friend is right about the use of rc.local.
However, it is set up for starting local services only, not for stopping them.
It is easy to add though:

Edit /etc/init.d/rc.local like this:

#! /bin/sh
### BEGIN INIT INFO
# Provides:          rc.local
# Required-Start:    $all
# Required-Stop:
# Default-Start:     2 3 4 5
# Default-Stop:
# Short-Description: Run /etc/rc.local if it exist
### END INIT INFO


PATH=/sbin:/usr/sbin:/bin:/usr/bin

. /lib/init/vars.sh
. /lib/lsb/init-functions

do_start() {
	if [ -x /etc/rc.local ]; then
	        [ "$VERBOSE" != no ] && log_begin_msg "Running local boot scripts (/etc/rc.local)"
		/etc/rc.local
		ES=$?
		[ "$VERBOSE" != no ] && log_end_msg $ES
		return $ES
	fi
}

do_stop() {
       # Add the command to umount your network share after  this line
}

case "$1" in
    start)
	do_start
        ;;
    restart|reload|force-reload)
        echo "Error: argument '$1' not supported" >&2
        exit 3
        ;;
    stop)
        do_stop
        ;;
    *)
        echo "Usage: $0 start|stop" >&2
        exit 3
        ;;
esac

Just add the command to umount your network drive after the comment line.
This will run as root, so no sudo needed.


WARNING: Make a note of these modifications. New versions of pam and rc.local will overwrite your changes. You will have to re-apply them.

I have not tested the umount. The shutdown solution works for me both in Debian sid and wheezy.

Let us know how it goes for  you.

PS: Out of curiosity: are you using 'startx' or the default login manager (slim) or perhaps even another login manager?

Last edited by xaos52 (2013-02-20 14:08:41)

Offline

#13 2013-02-20 23:49:20

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

No luck.  Any other ideas?

Regarding the login manager, I'm not sure -- whatever installed with Crunchbang.  I'd say SLiM, since when I go to user login settings, SLiM Config shows up.

Offline

#14 2013-02-21 08:50:43

xaos52
The Good Doctor
From: Planet of the @s
Registered: 2011-06-24
Posts: 4,602

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

In a terminal window, run and post output of:

ck-list-sessions
ps -eF
(ps -eF | grep slim) && cat /etc/slim.conf
if [ -e $HOME/.xinitrc ]; then cat $HOME/.xinitrc; fi

Last edited by xaos52 (2013-02-21 08:54:30)

Offline

#15 2013-02-21 23:04:12

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

Here you go.  It's a bit long.

paul@eeepc:~$ ck-list-sessions
Session1:
	unix-user = '1000'
	realname = 'paul'
	seat = 'Seat1'
	session-type = 'x11'
	active = TRUE
	x11-display = ':0.0'
	x11-display-device = '/dev/tty7'
	display-device = ''
	remote-host-name = ''
	is-local = TRUE
	on-since = '2013-02-21T00:05:15.868749Z'
	login-session-id = '1'
paul@eeepc:~$ ps-eF
bash: ps-eF: command not found
paul@eeepc:~$ ps -eF
UID        PID  PPID  C    SZ   RSS PSR STIME TTY          TIME CMD
root         1     0  0   570   740   0 Feb20 ?        00:00:01 init [2]  
root         2     0  0     0     0   0 Feb20 ?        00:00:00 [kthreadd]
root         3     2  0     0     0   0 Feb20 ?        00:00:00 [ksoftirqd/0]
root         6     2  0     0     0   0 Feb20 ?        00:00:00 [watchdog/0]
root         7     2  0     0     0   0 Feb20 ?        00:00:00 [cpuset]
root         8     2  0     0     0   0 Feb20 ?        00:00:00 [khelper]
root         9     2  0     0     0   0 Feb20 ?        00:00:00 [kdevtmpfs]
root        10     2  0     0     0   0 Feb20 ?        00:00:00 [netns]
root        11     2  0     0     0   0 Feb20 ?        00:00:00 [sync_supers]
root        12     2  0     0     0   0 Feb20 ?        00:00:00 [bdi-default]
root        13     2  0     0     0   0 Feb20 ?        00:00:00 [kintegrityd]
root        14     2  0     0     0   0 Feb20 ?        00:00:00 [kblockd]
root        16     2  0     0     0   0 Feb20 ?        00:00:00 [khungtaskd]
root        17     2  0     0     0   0 Feb20 ?        00:00:00 [kswapd0]
root        18     2  0     0     0   0 Feb20 ?        00:00:00 [ksmd]
root        19     2  0     0     0   0 Feb20 ?        00:00:00 [fsnotify_mark]
root        20     2  0     0     0   0 Feb20 ?        00:00:00 [crypto]
root        23     2  0     0     0   0 Feb20 ?        00:00:03 [kworker/0:2]
root        96     2  0     0     0   0 Feb20 ?        00:00:00 [khubd]
root       119     2  0     0     0   0 Feb20 ?        00:00:00 [ata_sff]
root       120     2  0     0     0   0 Feb20 ?        00:00:00 [scsi_eh_0]
root       121     2  0     0     0   0 Feb20 ?        00:00:00 [scsi_eh_1]
root       139     2  0     0     0   0 Feb20 ?        00:00:00 [scsi_eh_2]
root       140     2  0     0     0   0 Feb20 ?        00:00:00 [usb-storage]
root       166     2  0     0     0   0 Feb20 ?        00:00:00 [jbd2/sda1-8]
root       167     2  0     0     0   0 Feb20 ?        00:00:00 [ext4-dio-unwrit
root       295     1  0   735  1488   0 Feb20 ?        00:00:00 udevd --daemon
root       380   295  0   734  1212   0 Feb20 ?        00:00:00 udevd --daemon
root       381   295  0   734  1200   0 Feb20 ?        00:00:00 udevd --daemon
root       407     2  0     0     0   0 Feb20 ?        00:00:00 [cfg80211]
root       441     2  0     0     0   0 Feb20 ?        00:00:00 [kpsmoused]
root       487     2  0     0     0   0 Feb20 ?        00:00:00 [hd-audio0]
root      1560     1  0  7018  1796   0 Feb20 ?        00:00:00 /usr/sbin/rsyslo
root      1589     1  0  2461  4324   0 Feb20 ?        00:00:00 /usr/bin/slim -d
root      1598  1589  0  5464 11088   0 Feb20 tty7     00:04:11 /usr/bin/X11/X -
root      1624     1  0   959   960   0 Feb20 ?        00:00:00 /usr/sbin/cron
101       1640     1  0   852  1516   0 Feb20 ?        00:00:02 /usr/bin/dbus-da
avahi     1653     1  0   816  1640   0 Feb20 ?        00:00:00 avahi-daemon: ru
avahi     1654  1653  0   789   532   0 Feb20 ?        00:00:00 avahi-daemon: ch
root      1665     1  0  1121  1608   0 Feb20 ?        00:00:00 /usr/sbin/blueto
root      1677     2  0     0     0   0 Feb20 ?        00:00:00 [krfcommd]
root      1751     1  0  6632  5156   0 Feb20 ?        00:00:04 /usr/sbin/Networ
root      1761     1  0  6020  3776   0 Feb20 ?        00:00:00 /usr/lib/policyk
ntp       1771     1  0  1345  2072   0 Feb20 ?        00:00:00 /usr/sbin/ntpd -
root      1779     1  0  1722  2712   0 Feb20 ?        00:00:00 /usr/sbin/modem-
root      1796     1  0  1455  2696   0 Feb20 ?        00:00:01 /sbin/wpa_suppli
root      1821     1  0   462   308   0 Feb20 ?        00:00:00 /usr/sbin/miniss
root      1829     1  0   945   852   0 Feb20 tty1     00:00:00 /sbin/getty 3840
root      1830     1  0   945   852   0 Feb20 tty2     00:00:00 /sbin/getty 3840
root      1831     1  0   945   840   0 Feb20 tty3     00:00:00 /sbin/getty 3840
root      1832     1  0   945   844   0 Feb20 tty4     00:00:00 /sbin/getty 3840
root      1833     1  0   945   844   0 Feb20 tty5     00:00:00 /sbin/getty 3840
root      1834     1  0   945   844   0 Feb20 tty6     00:00:00 /sbin/getty 3840
paul      1837     1  0 14789  3516   0 Feb20 ?        00:00:00 /usr/bin/gnome-k
root      1840     1  0  6746  3816   0 Feb20 ?        00:00:00 /usr/sbin/consol
paul      1913  1589  0  3429  6664   0 Feb20 ?        00:00:03 /usr/bin/openbox
paul      1957  1913  0   967   356   0 Feb20 ?        00:00:00 /usr/bin/ssh-age
paul      1960     1  0   879   736   0 Feb20 ?        00:00:00 /usr/bin/dbus-la
paul      1961     1  0   891  1324   0 Feb20 ?        00:00:00 /usr/bin/dbus-da
paul      1971     1  0  3490  5716   0 Feb20 ?        00:00:01 tint2
paul      1972     1  0 24662  9180   0 Feb20 ?        00:00:00 pnmixer
paul      1975     1  0  5171  5516   0 Feb20 ?        00:00:00 thunar --daemon
paul      1982     1  0  1659  2360   0 Feb20 ?        00:00:00 xscreensaver -no
paul      1983     1  0  6784  8700   0 Feb20 ?        00:00:52 clipit
paul      2000     1  0 64453  8656   0 Feb20 ?        00:00:00 xfce4-volumed
paul      2006     1  0 12792  3516   0 Feb20 ?        00:00:56 conky -q
paul      2016     1  0  9192 11108   0 Feb20 ?        00:00:03 xfce4-power-mana
paul      2020     1  0  2147  2292   0 Feb20 ?        00:00:00 /usr/lib/gvfs/gv
paul      2029     1  0 13649 14868   0 Feb20 ?        00:00:03 nm-applet
paul      2032     1  0  7931  2752   0 Feb20 ?        00:00:00 /usr/lib/gvfs//g
paul      2047     1  0  1545  2252   0 Feb20 ?        00:00:00 /usr/lib/xfce4/x
paul      2051     1  0 24354  5436   0 Feb20 ?        00:00:01 /usr/bin/pulseau
rtkit     2053     1  0  4745  1208   0 Feb20 ?        00:00:00 /usr/lib/rtkit/r
root      2079     1  0  6590  3904   0 Feb20 ?        00:00:20 /usr/lib/upower/
paul      2091     1  0  6396  6676   0 Feb20 ?        00:00:12 compton --vsync 
root      2149     2  0     0     0   0 Feb20 ?        00:00:00 [cifsd]
paul      2175     1  0  1992  2248   0 Feb20 ?        00:00:00 /usr/lib/i386-li
root      3088     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/0:0]
root      3112     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/u:0]
root      3113     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/u:1]
root      3114     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/u:2]
root      3115     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/0:1]
root      3376     2  0     0     0   0 Feb20 ?        00:00:00 [flush-8:0]
root      3377     2  0     0     0   0 Feb20 ?        00:00:00 [flush-0:19]
root      3378     2  0     0     0   0 Feb20 ?        00:00:00 [flush-cifs-1]
root      3379     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/u:3]
root      3380     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/u:4]
root      3381     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/u:5]
root      3382     2  0     0     0   0 Feb20 ?        00:00:00 [kworker/u:6]
root      3383     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:7]
root      3384     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:8]
root      3385     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:9]
root      3386     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:10]
root      3387     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:11]
root      3388     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:12]
root      3389     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:13]
root      3390     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:14]
root      3391     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:15]
root      3392     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:16]
root      3393     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:17]
root      3394     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:18]
root      3395     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:19]
root      3396     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:20]
root      3397     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:21]
root      3398     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:22]
root      3399     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:23]
root      3400     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:24]
root      3401     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:25]
root      3402     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:26]
root      3403     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:27]
root      3404     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:28]
root      3405     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:29]
root      3406     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:30]
root      3407     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:31]
root      3408     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:32]
root      3409     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:33]
root      3410     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:34]
root      3411     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:35]
root      3412     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:36]
root      3413     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:37]
root      3414     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:38]
root      3415     2  0     0     0   0 17:56 ?        00:00:00 [kworker/u:39]
root      3416     2  0     0     0   0 17:56 ?        00:00:00 [kworker/0:3]
root      3492     1  0   465   588   0 17:56 ?        00:00:00 /usr/sbin/anacro
paul      3644     1  0  7086 10604   0 17:56 ?        00:00:00 /usr/lib/xfce4/n
root      3647  1751  0  1295  3044   0 17:56 ?        00:00:00 /sbin/dhclient -
paul      3726  1913 11 89427 61088   0 17:57 ?        00:00:15 /opt/google/chro
paul      3731  3726  0 24772  4992   0 17:57 ?        00:00:00 /opt/google/chro
paul      3732  3726  0   487   524   0 17:57 ?        00:00:00 /opt/google/chro
paul      3733  3732  0 32593 13280   0 17:57 ?        00:00:00 /opt/google/chro
paul      3736  3733  0 267855 3396   0 17:57 ?        00:00:00 /opt/google/chro
paul      3737  3733  0 34642  5092   0 17:57 ?        00:00:00 /opt/google/chro
paul      3760  3737 13 56244 66484   0 17:57 ?        00:00:17 /opt/google/chro
paul      3774  3726  0 33908 14420   0 17:57 ?        00:00:00 /opt/google/chro
paul      3779  3737  7 54746 81056   0 17:57 ?        00:00:10 /opt/google/chro
paul      3821  1913  4 16771 26516   0 17:58 ?        00:00:02 /usr/bin/python 
paul      3824  3821  0   520   696   0 17:58 ?        00:00:00 gnome-pty-helper
paul      3825  3821  0  1323  2480   0 17:58 pts/0    00:00:00 /bin/bash
paul      3869  3825  0  1084  1116   0 17:59 pts/0    00:00:00 ps -eF
paul@eeepc:~$ (ps -eF | grep slim) && cat /etc/slim.conf
root      1589     1  0  2461  4324   0 Feb20 ?        00:00:00 /usr/bin/slim -d
root      1598  1589  0  5464 11088   0 Feb20 tty7     00:04:14 /usr/bin/X11/X -nolisten tcp -auth /var/run/slim.auth vt07
paul      3872  3870  0   888   816   0 18:00 pts/0    00:00:00 grep slim
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
#
default_path        /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
default_xserver     /usr/bin/X11/X
xserver_arguments   -nolisten tcp

# Commands for halt, login, etc.
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue.net; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend

# Full path to the xauth binary
xauth_path         /usr/bin/X11/xauth

# Xauth file for server
authfile           /var/run/slim.auth


# Activate numlock when slim starts. Valid values: on|off
# numlock             on

# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor          false

# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
#
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd           exec /bin/sh - ~/.xinitrc %session
login_cmd           exec /bin/bash -login /etc/X11/Xsession %session

# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
#
sessionstart_cmd	/usr/share/crunchbang/cb-user-setup %user
# sessionstop_cmd	some command

# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon	yes

# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
#sessions            default,startxfce4,openbox,ion3,icewm,wmaker,blackbox,awesome
sessions            openbox-session

# Executed when pressing F11 (requires imagemagick)
screenshot_cmd      scrot /root/slim.png

# welcome message. Available variables: %host, %domain
welcome_msg         Welcome to %host

# Session message. Prepended to the session name when pressing F1
# session_msg         Session: 

# shutdown / reboot messages
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...

# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user        paul

# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password      no

# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
auto_login          yes


# current theme, use comma separated list to specify a set to 
# randomly choose from
#current_theme       debian-spacefun
current_theme       waldorf

# Lock file
lockfile            /var/run/slim.lock

# Log file
logfile             /var/log/slim.log

paul@eeepc:~$ if [ -e $HOME/.xinitrc ]; then cat $HOME/.xinitrc; fi

Offline

#16 2013-02-22 14:40:47

xaos52
The Good Doctor
From: Planet of the @s
Registered: 2011-06-24
Posts: 4,602

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

Hmm... Can not see anything wrong in what you posted.

You are running Waldorf, are you not? (because it is posted in the stable thread, but mentions Waldorf in the title)

Which version of Waldorf? The version from 20130119 or  the previous one?
Did you do a clean install or did you install over an already existing distro?
Did you run the cb-welcome script? All sections of it?

I did a clean install of the latest Waldorf, and the shutdown works OOTB.

Can you try this in a terminal window:

/usr/bin/cb-exit

It should display the well known menu. Click on 'Shutdown'.
Any error messages(s) in the terminal window?
Does it shut down your system or not?
If it does not, break by entering Ctrl+C
Post the result.

Last edited by xaos52 (2013-02-22 14:46:03)

Offline

#17 2013-02-22 15:31:19

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

I'm running Waldorf (I thought that was the stable version -- sorry if I posted in the wrong forum).  I can check the version when I get home, but it's whatever was available about a week ago, when I first started posting.  It was a clean install.  I went through the initial set-up, which I assume is the cb-welcome.  I skipped over some irrelevant parts (I can't remember, maybe downloading libre office?  Some database stuff?).

Remember, shutdown works fine when I don't have a network drive mounted.  I've run cb-exit from a terminal window (in order to try some of the earlier ideas) -- the system doesn't shut down if there's a network drive mounted, but it will drop me into a tty page.  I'll try again tonight.

Thanks for your continued effort and patience, by the way!

Offline

#18 2013-02-22 16:54:02

xaos52
The Good Doctor
From: Planet of the @s
Registered: 2011-06-24
Posts: 4,602

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

There were 2 distinct problems to start with:

(1) being able to shutdown your system as a normal user - using cb-exit - without having to authenticate.
I gather this one is solved.

(2) The shutdown itself hangs when a network drive is mounted. This happens later in the shutdown process than (1).
Have you tried the rc.local proposed solution from post # 12? Remember you have to enter the umount command for the network drive in that script.
This should umount the network drive, so that it does not hang later on in the shutdown sequence when the network is brought down.

Or use the autofs solution offered here

Let us know what works for you.

No problem. I like solving riddles.  smile

Last edited by xaos52 (2013-02-22 16:56:38)

Offline

#19 2013-02-22 18:02:37

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

I'm sorry if I didn't explain this properly to begin with.  There is really only one problem -- if I shut down when there's a network drive mounted, it drops me into a tty screen and hangs.  The point about being a normal user was that if I modified cb-exit to unmount the drive during the shutdown, the unmounting failed because the process running cb-exit didn't have elevated privileges. 

That autofs solution looks like it may be exactly what I'm looking for.  What is autofs?  How does it relate to fstab?

Offline

#20 2013-02-23 12:53:36

RitterSport
#! Member
Registered: 2013-02-18
Posts: 58

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

The autofs solution you pointed to worked! All is well in crunchbang land for me.  Do I label the thread as solved, or does a mod do that?  Also, should I request to have this moved to the unstable forum?

Thanks again for all your help.

Offline

#21 2013-02-23 15:19:24

xaos52
The Good Doctor
From: Planet of the @s
Registered: 2011-06-24
Posts: 4,602

Re: [Solved] Eeepc 701, Crunchbang Waldorf, Unable to shutdown/reboot

You should mark it solved yourself.
Edit your first post in this thread and add [SOLVED] to the title.

Glad it works for you and thanks for posting your solution.

Offline

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.

Debian Logo