Autologin does not retain changes

[tedw]

Hello:
I would like to say thanks for TinyMe. I installed it and got it working with a minimum of effort. It does bring old equipment "back to life."
Anyway, I don't know if this is a "bug," but after installing the 2010-Acorn-RC-1b.i586 image and creating a few user accounts, I cannot get it to use the "autologin" option.
When I goto the Unity control options -> boot -> autologin, and then select "yes" for autologin, and choose a user and desktop, it appears to be fine. But, after I hit "ok" and then re-open the autologin config screen, the changes that were just made are gone, and the autologin option is again set to "no."
So, is this a "bug," or am i doing something wrong.
I have spent some time trying to find which files these config changes are stored in, but have been unsuccessful.
Any help would be great.
thanks
bye - ted

[KDulcimer]

The autologin in the Unity Control Center, I believe, does not work at all, and certainly does not work for auto logging in a with the login manager TinyMe uses.

To set autologin for TinyMe, see http://slim.berlios.de/manual.php (note: config file is stored in /etc/slim.conf for TinyMe)

[tedw]

Thanks for the lead.
yes, setting a default_user and auto_login to yes in slim.conf does the trick.
bye - ted

[frog]

Well, adjusting the slim.conf file did nothing. Here it is:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile
is automatically appended
default_path
./:/bin:/usr/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local
/sbin
default_xserver /usr/bin/X
xserver_arguments :0 -audit 0
-deferglyphs 16 -nolisten tcp vt7

# Commands for halt, login,
etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd
/sbin/shutdown -r now
console_cmd /usr/bin/xvt
suspend_cmd
/usr/sbin/suspend
hibernate_cmd
/usr/sbin/hibernate
drak3d_cmd /usr/sbin/drak3d

# 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 slim-session-start %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
no

# 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 previous,Openbox,
Openbox-KDE,Openbox-Gnome,failsafe

# 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
Log in to:

# shutdown / reboot messages
shutdown_msg
The system is shutting down...
reboot_msg The system is
restarting...

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


# 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
lake,TinyMe-The-Forest,wave

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

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

What should be changed? The referenced "Slim" web page
just confused me. Here is the computer I use (Have a dozen):

Computer:
Operating System Microsoft Windows XP Professional
OS Service Pack -
DirectX 4.08.01.0810 (DirectX 8.1)
Computer Name LT-JKAFRKXFUZIW (HOME)
User Name Administrator

Motherboard:
CPU Type Intel Pentium 4, 2666 MHz (20 x 133)
Motherboard Name Dell OptiPlex SX260
Motherboard Chipset Intel Brookdale-G i845G
System Memory 253 MB (PC2100 DDR SDRAM)
BIOS Type Phoenix (05/29/03)
Communication Port Communications Port (COM1)
Communication Port ECP Printer Port (LPT1)

Display:
Video Adapter Intel Extreme Graphics
3D Accelerator Intel Extreme Graphics

Multimedia:
Audio Adapter Intel 82801DB ICH4 - AC'97 Audio Controller [A-1]

Storage:
IDE Controller Standard Dual Channel PCI IDE Controller
Disk Drive WDC WD1600BEVE-00UYT0 (127 GB, IDE)
Optical Drive LG CD-ROM CRN-8245B (24x CD-ROM)
SMART Hard Disks Status OK

Partitions:
C: (FAT32) 3021 MB (1789 MB free)
D: (NTFS) 5012 MB (4016 MB free)
E: (NTFS) 10009 MB (7286 MB free)
F: (FAT32) 30020 MB (23941 MB free)
Total Size 46.9 GB (36.2 GB free)

Input:
Keyboard Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
Mouse PS/2 Compatible Mouse

Network:
Network Adapter Sagem XG703 USB 802.11g (10.0.0.64)

Peripherals:
USB1 Controller Intel 82801DB ICH4 - USB Controller [A-1]
USB1 Controller Intel 82801DB ICH4 - USB Controller [A-1]
USB1 Controller Intel 82801DB ICH4 - USB Controller [A-1]
USB2 Controller Intel 82801DB ICH4 - Enhanced USB2 Controller [A-1]
USB Device Sagem XG703 USB 802.11g
USB Device USB Audio Device
USB Device USB Composite Device
USB Device USB Human Interface Device
Plus 10 linux partitions: 9 OS 1 SWAP

Used Quirky on USB to edit TimyMe - Very useful tool - No permissions or
logins. Thanks in advance for your help. Frog (DOB 1930)
Just trying to avoid senility.

[KDulcimer]

The slim.conf you posted is impossible to read. Please try reposting it, this time with the whole thing in [ code ] blocks. Or you can attach it as a file.