Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
I use the procedure explained in the first post, but every time that I ssh to my computer, it autologins and tries to startx, but X is already running, so it gives an error. When I am back to my computer, I have to restart X every time that I have connected to it via ssh.
I use the procedure explained in the first post, but every time that I ssh to my computer, it autologins and tries to startx, but X is already running, so it gives an error. When I am back to my computer, I have to restart X every time that I have connected to it via ssh.
Does anybody know how to solve it?
I add the following code in ~/.bashrc, so X starts only for tty1
display manager = the login window??
I can't get this working. first I tried MeanDean's method. what do you mean with
"comment out "? I added the two lines at the bottom of the file (there were other lines
including "getty" at the bottom) then I edited the .bashrc as you wrote.
I still get the login window when I boot though.
so I decided to try out acemi's method. this did not work either. any ideas? (dont know how to program in python, so perhaps I did something wrong?)
#NOTE! this is not my first message. I have ~200 posts, but decided to change user name. my old one is called HenrikVSE
contredire wrote:display manager = the login window??
I can't get this working. first I tried MeanDean's method. what do you mean with
"comment out "? I added the two lines at the bottom of the file (there were other lines
including "getty" at the bottom) then I edited the .bashrc as you wrote.
I still get the login window when I boot though.
so I decided to try out acemi's method. this did not work either. any ideas? (dont know how to program in python, so perhaps I did something wrong?)
#NOTE! this is not my first message. I have ~200 posts, but decided to change user name. my old one is called HenrikVSE
Aye, the x display manager is the login screen. To "comment out " something means to add a "#" or "!" in front of what is not to be read by bash, Just to be sure, if you can not get it to work, post both your /etc/inittab & ~/.bash_profile
Cheers
ps - are still other ways to accomplish what you want, but let's try & sort out Dean's way.
Henke:~# more /etc/inittab
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
# The default runlevel.
id:2:initdefault:
# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS
# What to do in single-user mode.
~~:S:wait:/sbin/sulogin
# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."
# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
###
#1:2345:respawn:/sbin/getty -n -l /usr/local/sbin/autologin 38400 tty1
#1:2345:respawn:/sbin/getty 38400 tty1
1:2345:respawn:/bin/login -f henke tty1 </dev/tty1 >/dev/tty1 2>&1
###
# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3
Henke:~# more /home/henke/.bash_profile
# ~/.bash_profile: executed by bash(1) for login shells.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
# the default umask is set in /etc/login.defs
#umask 022
# include .bashrc if it exists
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# set PATH so it includes user's private bin if it exists
if [ -d ~/bin ] ; then
PATH=~/bin:"${PATH}"
fi
startx
For the sake of making the file more readable you could try moving this last line so that it is in the same group as the other ttyx entries.
I've tried this on at least three computers running Lenny and it works fine.
contredire wrote:what is the x window manager? not the same thing as the X windows system/Xserver/X???
My bad, I ment to type "You may have to remove your x display manager (not sure since I never install one)'. Your x display manager is what you login via, for example, GDM, KDM, XDM and such.
I made a backup of my files, so now I dare starting to fix the problem.
First I tried
sudo aptitude purge gnome-desktop-environment
now, I get to the gnome desktop after boot instead of the log in windows, but the design is rather changed but my settings are still there.. and when entering a ctrl-alt-F1 prompt, the X server is terminated, and started again when I log in on the ctrl-alt-F1-prompt
what about that? how to get rid of all gnome, KDE and fluxbox files, configs etc?
contredire wrote:I made a backup of my files, so now I dare starting to fix the problem.
First I tried
sudo aptitude purge gnome-desktop-environment
now, I get to the gnome desktop after boot instead of the log in windows, but the design is rather changed but my settings are still there.. and when entering a ctrl-alt-F1 prompt, the X server is terminated, and started again when I log in on the ctrl-alt-F1-prompt
what about that? how to get rid of all gnome, KDE and fluxbox files, configs etc?
You should have only removed GDM, gnome desktop manager not the whole gnome desktop.