I've built a system and installed Debian 5.0.7 on it, the one thing I'd like to do is to get it to autologin at startup. I've changed my /etc/inittab and ~/.bash_profile as per the instructions in this thread:
viewtopic.php?f=16&t=29333
so that they look like this:
/etc/inittab:
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
code....
Code:
# cat /etc/init/tty.conf
# This service maintains a getty on the sepcified device.
stop on runlevel [016]
respawn
instance $TTY
exec /sbin/mingetty $TTY
exec /sbin/mingetty --autologin user tty1
when i use this conf I'm auto logged back in again , and cant't execute any command
commenting pre-last line has no effect.
How to enable autologin on desired tty for certain user?
I've been on 11.2 KDE for about a week (clean install). Previously on 11.1 Gnome. Everything's great except I can't get Autologin to work consistently. It worked perfectly in 11.1 Gnome! In 11.2 KDE sometimes it works and sometimes it doesn't. I set it up as root in both Yast and System Settings.
View 6 Replies View RelatedI use Xfce 4.I can not enable autologin.I make the necessary changes:
Yast
system
editor / etc / sysconfig /
desktop
display manager
and put my name in
DISPLAYMANAGER_AUTOLOGIN
code....
I'm running Debian + LXDE in a VirtualBox. Here are the details:
Code: Select all➜ ~ hostnamectl
Static hostname: debian64
Icon name: computer-vm
Chassis: vm
Machine ID: #############################
Boot ID: ###########################
Virtualization: kvm
Operating System: Debian GNU/Linux stretch/sid
Kernel: Linux 4.2.0-1-amd64
Architecture: x86-64
I really would like to jump into my desktop environment when I start my machine without the need to enter my user name and password. Apparently this is very easy to do. I added the following lines to my /etc/lightdm/lightdm.conf
Code: Select allpam-service=lightdm
pam-autologin-service=lightdm-autologin
autologin-user=username
autologin-user-timeout=0
session-wrapper=/etc/lightdm/Xsession
And also added my user to the autologin group
Code: Select allgroupadd -r autologin
gpasswd -a username autologin
As you can imagine, it didn't work. Otherwise I wouldn't be here... I also tried to install Slim and enable autologin adding the following line to the /etc/slim.conf
Code: Select allauto_login = yes
That didn't work either!
Am I missing anything? Enabling autologin in LXDE?
I installed a minimal Debian Squeeze with slim as login manager.
How can I automatically log in to X?
I have succesfully installed Debian with gnome-core, iceweasel and other useful packages and also followed this guide to autologin and start X. I noticed that the sudo chmod +s /sbin/halt and adding /sbin/halt
in ~/.bashrc made Debian refuse me to log out (from X) and 'log out' turns off the computer insted.Removing /sbin/halt from .bashrc turned everything to as i want it. Should I "repair" or remove something I created with chmod +s command or should I leave it as it is?
Also I would like apt-get(or aptitude) update to run after login (and before startx), so i added sudo apt-get update to .bashrc but it will prompt me with password. Is there someway I could do this without the password(s) which su/sudo needs to execute? This is not so important but it would be very nice to update the system on startup.
I have already tried editing /etc/slim.conf and making the "Automatically login..." look like this: auto_login yes default_user<username>
BUT nothing I've tried has work.
I installed JWM and Slim in Lenny Now, can't seem to get autologin working for user "guest"
Heres my slim.conf
Code:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
default_xserver /usr/X11R6/bin/X
#xserver_arguments -dpi 75
[Code]...
I'm trying to set up an autologin on an OpenSuse minimal install of 11.2. So, no Gnome or KDE, just X and TVWM. I tried setting this up in via the Display Manager setings in the SysConfig editor, but that didn't work.
View 1 Replies View RelatedSometimes(after a crash??) the GDM wan't autologin, is there a way to always autologin? The pc is running in a kiosk environment so it is really annoying that the machine are left in the login shell after a restart/boot.
View 2 Replies View RelatedI am geting a bit confused regarding the autologin of a user , and in need of help desperately. Could anybody please help me with the below queries :
How can we set autologin for any normal user in RHEL5 ? Also, How can we then logout such a user later, as we can't logout such user normally ? How to set timeout for such autologin users ?
it tried to test the autologin mechanism, now i have to decided to go back to normal
login on fc14 under gnome, but the login screen doesn't appear any longer.The autologin was activated with accounts-login and disabled by removing the twolines below
Code:
[daemon]
AutomaticLoginEnable=True
[code]....
In 9.04 this worked. Log out and in 10 seconds a default user logs in if no keys are pressed. I need this in 10.04. This is great for my Mom's PC. When one of her grandchildren visits for the weekend they can log Mom out and use their ID, bookmarks games etc. Then when they finish they logout and the PC logs Mom back in. Mom doesn't have to fish around for a password. She's 81 and I try to make things easy for her. In both 10.04 and 9.04 I have /etc/gdm/custom.conf with
Code:
AutomaticLoginEnable=true
AutomaticLogin=ridgeland
TimedLoginEnable=true
TimedLogin=ridgeland
TimedLoginDelay=10
In 9.04 log out and in 10 seconds it does an autologin. With 10.04 log out and it goes to the select a user screen and stays there. Where is the configuration file? What do I change? Disable something like SELinux?
I created a ubuntu distro that originated from ubuntu server and have an xserver installed with openbox and am having problems getting autologin working. I had slim installed and everything seemed to be working except as soon as the monitor went into sleep mode and I moved the mouse to get it back it just came up to the shell again. With that problem I decided to remove slim and go with NODM and that worked perfectly for what I wanted but I was messing around with a few other configuration stuff and when I rebooted everything was fine until after the splash when it would normally boot into X it would show the shell for a about 10 seconds before it would boot to X.
View 2 Replies View RelatedI've got a couple of nagging issues that may or may not be related to each other. First, although I have this machine set to log me on automatically (I'm the only user ever and there's no public access) it doesn't; I get the standard login welcome screen. In the system menu (from Applications) I have two login managers: "Login Screen" and "Login Screen (GDM2)". The first of these shows I'm configured for automatic login, as does the custom.conf file in /etc/gdm. However when I click its "unlock" button, it flashes orange momentarily but nothing else happens. The second manager doesn't seem to have any effect on the problem...
The other issue is that my networking fails to start during boot-up; I'm not using the network manager applet and am not starting it; instead I have the three NICs in the machine (which serves as the router and gateway for my LAN) configured in /etc/network/interfaces. Once I am logged in, I can run "sudo service networking start" from a Terminal window and everything works properly, but adding that same line to /etc/rc.local (minus the "sudo" of course) had no effect on the problem. Both issues happen only at boot time, and since this machine normally runs 24/7 except immediately after certain updates or when troubleshooting they're not show-stoppers, but I greatly prefer to have my systems working the way I've configured them rather than going off in other directions!
I saw that Evolution 3.0 was available for 11.04 so I decided to give it a shot. I installed it via ppa following these directions:
[URL]
There were a bunch of dependencies that installed and required a restart. Upon reboot, autologin doesn't work and graphically the desktop is uglier with a different theme. Unity is not working properly, the wallpaper does not exist and many, many artefacts are present.
Screenshots:
Based on my description and the posted instructions, is there a way to undo what I did short of a format and re-install?
my system has an autologin as root defined by custom.conf which is located in /etc/gdm : Code: [daemon]
TimedLoginEnable=false
AutomaticLoginEnalbe=true
TimedLogin=root
AutomaticLogin=root
TimedLoginDelay=30
And I would like to have the program "expfit_spifunc2" executed after the auto login. So, I have added "xterm_expfit.desktop" inside of /root/.config/autostart
"xterm_expfit.desktop" code:
Code: [Desktop Entry]
Encoding=UTF-8
Version=0.9.4
Type=Application
Name=xterm_expfit
code....
I usually shut down openSUSE in KDE by clicking the shutdown icon and selecting "Turn Off Computer". When I boot back into openSUSE, my session resumes automatically without it asking for my password.While I don't mind KDE resuming my session because it saves time, me not having to reenter my password is a security risk. How do I turn off the autologin?
View 4 Replies View RelatedI have a single kernel with 2 menu entries in grub like following:
Boot(gfx)
Boot(text)
First entry boot the fedora in graphical mode running the gnome.
Second entry boot the fedora in text mode.
First thing is working fine but i want to know how to do the second thing. i added 3 at the end of second entry in syslinux.cfg and after booting it dropped me at console asking for login.
So how to autologin in runlevel 3 and start autostart an application(e.g python script)?
I just finished setting up a new computer lab at my kids school, using LTSP and 22 think clients connecting to Ubuntu.Everything is going beautifully, and I'm using static IPs and autologin so that when each computer is turned on it logs itself in with no userintervention. The problem is, when users go to the top right system menu and select "Shut Down", they are brought out to the login screen for a second and then immediately logged back in automatically to the Desktop. How should I be shutting down the thin clients?he only way to do it at the moment is to have everyone hold the power button down until the CPU shuts off, but it feels sloppy and unhealthy.
View 3 Replies View RelatedWhat i'm trying to accomplish seems rather silly but is needed for my little project here.
I'm using OpenSuSE 11.2 as a media center PC and need it to login automatically(console not X). That one i accomplished without problems.
However, after login i can see all the info about the services that were started and that needs to "go away".
One could do a "clear" in the .bash_rc and or .bash_profile but it will still show the login prompt which i don't want to see either (i don't even want to see the blinking cursor as well).
Question: How do i accomplish that so that the login console shows only the "splash screen" without any output of the kernel,rc.status nor the "issue-file"... just a plain blank screen ?
Installed 10.10 Ubuntu and found the Dell D820 did not digest Gnome that easily. I tried adding Lubuntu from repos after adding PPA. Seemed unstable to use, so I followed Psychocat direction for Pure LXDE and removed Ubuntu. Now login is giving error "xsession:unable to launc "openbox-gnome" X Session --- "openbox-gnome" not found; falling back to defaultsession." Where do I correct the xsession login to allow auto login. (I know the chances for autologin, and still choose to use it)
View 7 Replies View RelatedI've run into a strange problem with GDM that I haven't managed to find a solution for yet, either by trying myself or googling, and I have run out of good ideas. I'll just infodump here about the problem and what I've tried etc;
I installed Ubuntu on a new PC a few weeks ago, setting it up with autologin for my mom and a separate user for myself, using the on/off-icon menu in the top-right corner to switch to my own user and back as needed, and logging the user out when done. This worked quite well.
However, a few days ago, this stopped working; logging out or trying to switch now leaves me with a blank black screen, without even a mouse pointer (but not off, the backlight is on).
EDIT: To clarify, this is an issue that only affects the GDM login screen, but that affects it whenever it is used, wether it is on boot (when not set to autologin), after logging out, or when trying to switch user.
At this point, I can usually use Ctrl-Alt-F1 to get a textmode login, and Ctrl-Alt-F7 to get back to the auto-logged in session (assuming I tried to switch, not logout).
I can't think of anything specific I did or installed around then that should be related in any way...
I tried disabling autologin and restarting gdm, which left me with the same black screen (which is still there after rebooting), instead of the expected login window. I managed to re-enable autologin by manually editing the /etc/gdm/custom.conf file, so that it would at least work for mom.
I've also tried to change which user is auto-logged in, thinking it might be a problem with my user account, but both users get an automatic session just fine when I restart gdm.
I thought it might be a problem with the video driver, but that's not the case - if I run zenity --info as root with DISPLAY set correctly, the dialog box appears on the screen just fine. It has no borders or titlebar (there's no windowmanager), and is apparently without keyboard focus, so since there's no visible mouse pointer I can't click the OK button... But since it appears, X is apparently up and running just fine, just has nothing to display other than a black background.
I tried purging and reinstalling gdm and gnome-session(-bin|-common), but that didn't help any.
Running ck-list-sessions after trying to switch indicates that there's a new session there, with session-type = 'LoginWindow', so it appears to think everything's fine.
Enabling debug output in the /etc/gdm/custom.conf file did get me some more debug output in the gdm logs, but it didn't really tell me anything, there weren't any obvious problems that I could see.
After some looking around, I've guessed that it's supposed to be running gdm-simple-greeter, which I assume would display a login box; trying to run it manually doesn't work though (it's missing some environment variables, and trying to add them based on the abovementioned debug output doesn't really help).
I upgraded to F13 this week. And autologin just sits with autologin present, but I have to click the autologin (rather than a user name) and then click again to actually login. That's not so "auto" anymore if I can't push the power button and come back in x minutes with everything and running.
I had this in my /etc/gdm/custom.conf
TimedLoginEnable=true
TimedLogin=marty
TimedLoginDelay=8
What changed and what do I need to do now to get autologin to get off it's ass and log me in?
i'm running fedora 10 Gnome ver 2.24.3 kernel 2.6.30.4
i tried to change my /etc/gdm/custom.conf by adding it the following lines:
[daemon]
TimedLoginEnable=true
TimedLogin=your_mike
TimedLoginDelay=0
after reloading gnome it's trying to log through "autologin" but than it give an error message "Unable to authenticate user", i tried using passwd -d on my account but still the error persisted, i saw that some users had this error after a fresh install just with logging into the machine without relation to autologin and they needed to change their password first i tried that as well.
i also tried to edit the /etc/gdm/gdm.schemas file
<schema>
<key>daemon/AutomaticLoginEnable</key>
<signature>b</signature>
<default>true</default> <schema>
<key>daemon/AutomaticLogin</key>
code....
But unfortunately the results were the same, i tried this procedure on a different Fedora 7 and on a virtual ubunto 9.4 machine and is was successful.
I'm using openSUSE 11.3 with Xfce 4.7.0 and I want to enable automatic login. What I have tried so far:
1) YaST -> User and Group Management -> Expert Options -> Login Settings. This didn't work because I have no "Login Settings" option in this menu.
2) Editing variables "DISPLAYMANAGER_AUTOLOGIN" and "DISPLAYMANAGER_PASSWORD_LESS_LOGIN" via YaST -> /etc/sysconfig Editor. This didn't work too and xdm was still asking about name and password no matter what I set here.
3) I don't know how to configure xdm, so I tried to replace xdm with gdm. Gdm worked, but application "gdmsetup" was missing from my installation (YaST simply don't offer this package) and I don't know how to set up gdm manually, so I ended without autologin again.
I've been able to kludge a kill script which finds the correct pid for the kdeserver (or gnome server) after my system comes up in run level 5 so I can drop back to run level 3 mode. Lots of experimentation showed me that using telinit 3 and telinit 5 would occasionally leave the video memory in a mess and I would have the black screen of death.
I set the security parameter setting to autologin for me since I am the only user of my machine, but I still have to kludge the default setting under sysconfig (the DEFAULT_WM) under Window Manager to pick a certain window manager, so it takes time to manually switch the desktop.
Right now I can leave the gui and drop back to cli, but painful experimenting showed me that killing the X server is a no no. Right now I kill the kde server, which sends the SIGTERM to the X windows manager, which then figures out that it has to shut down.
Questions: Is there a better way of doing this? Apparently openSUSE figures that we have multiple users logging into the gui desktop, so the gui is always kept running and a login window with the desktop manager option forces the user to login in. With autologin, this never happens, but no choice of desktop is possible on the fly.
Can some type of script be set up to painlessly enable this to happen? And what is the best way of bringing either the Gnome or KDE desktop manager down gracefully? I do get lots of error messages as the system attempts to recover and X shuts down. It appears that apparently the single user with autologin is left out in the cold.
My problem is: One of my services has failed to start. All I need is just go into interactive startup and ignore that service. The system is encrypted as LUKS. I press 'i' before and after entering the phrase (it asked me "Password for filesystem"). But interactive startup seems not working. All the services go to start without my permission. I mean there is no question such as "Start XXX [Y/N]?"
In the past I used CentOS for some months, and interactive startup (by pressing 'i' on boot time) was fine. I could allow or not what service should be started.
I have googled and found these:
[URL]
I recently installed Ubuntu 9.04 through WUBI, but when the installation finished and I went to turn the computer on to Ubuntu, I could not get graphics working. It would appear that the resolution has been set super-high somehow, because a message will pop up saying that I don't have enough video memory to run at the resolution I'm trying. I have tried xfix in recovery modeI don't know if this has anything to do with it, but I'm using a very old monitor.
View 2 Replies View Related