You are not logged in.
G'day gents.
I'm having an issue with awesome not executing my custom configuration scripts.
I'm using the SLiM login manager. Here's my config file for SLiM:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# 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; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/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 ~/.xinitrc %session
login_cmd exec /bin/zsh -l ~/.xinitrc %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 some command
# 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 awesome,xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window 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 james
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password yes
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login no
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme archlinux-darch-white
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.logHere's my ~/.xinitrc file:
xscreensaver -nosplash &
xcompmgr -cf &
xrdb -merge ~/.Xresources
urxvtd &
DEFAULT_SESSION=awesome
case $1 in
awesome) exec awesome ;;
*) exec $DEFAULT_SESSION ;;
esacIt's very simple, just executes awesome after doing some configuration for basic programs.
Finally, after reading man awesome, and man awesomerc I've discovered that the configuration order for awesome is $XDG_CONFIG_HOME/awesome/rc.lua
$ echo $XDG_CONFIG_HOME
/home/james/.configMy rc.lua file is in that directory, however I am still unable to get my configuration to work. I am using the latest awesome package in the official repositories.
I've tried several different rc.lua I've found online, none of them work either, however they all pass:
awesome -kAny help would be vastly appreciated!
Last edited by DrPhiTheta (2012-10-29 00:06:18)
Offline
Maybe your config is just buggy. Take a look in the log:
http://awesome.naquadah.org/wiki/FAQ#Wh … mething.3F
Offline
Maybe your config is just buggy. Take a look in the log:
http://awesome.naquadah.org/wiki/FAQ#Wh … mething.3F
Unlikely, as I said, I've tried atleast 3 different online users' examples.
Offline
Maybe your config is just buggy. Take a look in the log:
http://awesome.naquadah.org/wiki/FAQ#Wh … mething.3F
Offline
I do not use awesome, but have you tried using Xephyr to test your config, as descibed in the wiki?
Offline
I don't see how the problem could be with my config. I've tried so many other configs and none of them worked. I'm having trouble getting awesome to see my configuration files. I have them in the proper directories, with normal permissions(644) but none of them seem to work. I've even explicitly started arch from ~/.xinitrc with the config script located in ~/.config/awesome/rc.lua, but that did not work either.
I will give it a shot, however.
Offline
Maybe the third time will be the charm...
Maybe your config is just buggy. Take a look in the log:
http://awesome.naquadah.org/wiki/FAQ#Wh … mething.3F
Offline
Fixed ![]()
I built awesome from source, copied the default rc.lua to its proper place, and am now able to configure it properly.
Thank you guys for the help, I will install zephyr, as that looks like a safe way to configure this in the future.
Offline