LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices



Reply
 
Search this Thread
Old 10-10-2003, 04:54 PM   #1
fundoovikas
LQ Newbie
 
Registered: Sep 2003
Distribution: Fedora Core 1
Posts: 2

Rep: Reputation: 0
Unhappy I get a graphical login screen...have to start window manager expilcitly


I am a bit of newbie. I have just installed SuSE8.1. I then started Yast Online Update. I also installed DirectFB as was specified to run mplayer if i wished to see video on console.

Then to my surprise when i rebooted the machine...the login screen was there but a bit different. I logged on and what i get is just console...which allowed me run everything. But there was no window manager.

The window manager could be run from that console....but my problem is why cant I login normally as it used to happen before.

Moreover, if I shutdown X and to a startx from console login, KDE directly starts at it earlier did.

I have following window managers installed on my system:
KDE
Gnome
Window Maker
fvwm, fvwm2
blackbox

I can run all the above managers from the console that comes up.

Following is the listing of kdmrc and Xsession(i guess these are two that are responsible for the act)

kdmrc:

[Desktop0]
BackgroundMode=Flat
BlendBalance=100
BlendMode=NoBlending
ChangeInterval=60
Color1=30,114,160
Color2=192,192,192
CurrentWallpaper=0
LastChange=0
MinOptimizationDepth=1
MultiWallpaperMode=NoMulti
Pattern=
Program=
ReverseBlending=false
UseSHM=false
Wallpaper=SuSE-kdm.jpeg
WallpaperList=
WallpaperMode=Scaled

[Shutdown]
HaltCmd=/sbin/halt
LiloCmd=/sbin/lilo
LiloMap=/boot/map
RebootCmd=/sbin/reboot
UseLilo=false

[X-*-Core]
AllowShutdown=Root
AutoReLogin=false

[X-*-Greeter]
AntiAliasing=true
DefaultUser=at
EchoMode=OneStar
FailFont=helvetica,12,-1,5,75,0,0,0,0,0
FocusPasswd=false
GUIStyle=Default
GreetFont=charter,24,-1,5,50,0,0,0,0,0
GreetString=Welcome to %s at %n
GreeterPosFixed=false
GreeterPosX=100
GreeterPosY=100
HiddenUsers=
Language=en_US
LogoArea=None
LogoPixmap=/opt/kde3/share/apps/kdm/pics/kdeflower.png
MaxShowUID=65535
MinShowUID=0
PreselectUser=None
SelectedUsers=vikas,
SessionTypes=kde,failsafe,default,
ShowUsers=Selected
SortUsers=true
StdFont=helvetica,12,-1,5,50,0,0,0,0,0

[X-:*-Core]
AllowShutdown=All
NoPassEnable=false
NoPassUsers=

[X-:0-Core]
AutoLogin1st=true
AutoLoginEnable=false
AutoLoginUser=at

Xsession:

#!/bin/sh
#
# Xsession: Setup the xsession and start the xsession
# script of the user.
#
# Copyright (c) 1998-2000 SuSE GmbH Nuernberg, Germany.
# please send bugfixes or comments to feedback@suse.de.
#
# Author: Werner Fink, <werner@suse.de>
#

#
# What we do if we are signaled or do not leave this
# script with an appropriate exec call.
#
: ${failsafe="xterm -ls -T Failsave -geometry 80x24+0+0"}
readonly failsafe
trap "exec $failsafe" EXIT SIGHUP SIGINT SIGPIPE SIGTERM SIGIO

#
# Save our arguments, maybe some of users call
# `set' in their profile files.
#
argv="$@"

#
# Handle the NoChange option of wdm
#
/sbin/pidof -s wdm > /dev/null 2>&1
if test $? -eq 0 ; then
if test -z "$argv" ; then
if test -s $HOME/.wmrc ; then
argv=$(<$HOME/.wmrc) #use wm from previous session
fi
else
echo "$argv" > $HOME/.wmrc #save wm
fi
fi

readonly argv

#
# Disable graphical login if normal login is disabled
#
login=false
while read sh ; do
if test "$sh" = "$SHELL" ; then
login=true
break
fi
done < /etc/shells

if test "$login" != "true" -o "$SHELL" = "/bin/false" ; then
trap "exec xmessage -timeout 10 -button okay:1 -center \
\"${0##*/}: Login for $USER is disabled.\"" \
EXIT SIGHUP SIGINT SIGPIPE SIGTERM SIGIO
exit 1
fi
unset sh login

#
# Some bash (1 and 2) settings to avoid trouble with
# personal profile or bashrc files and failed exec calls.
#
test -n "$BASH" && set +o posix
no_exit_on_failed_exec=1
type shopt &> /dev/null && shopt -s execfail
set +e &> /dev/null

#
# Redirect errors to the standard user log files.
#
: ${TMPDIR=/tmp}
for errfile in "$HOME/.xsession-errors" \
"$TMPDIR/xses-$USER" \
"/tmp/xses-$USER"
do
#
# Avoid bad symbolic links
#
case "$errfile" in
/tmp/*|$TMPDIR/*) rm -f $errfile ;;
esac
if (> "$errfile") 2> /dev/null ; then
chmod 0600 "$errfile"
exec > "$errfile" 2>&1
break
fi
done

#
# Danger: What will the user do with some of the used variables?
# I do not like that ... but even if we source user's files
# we want to find our files and use correct variables.
#
__HOME="$HOME" # Users HOME determined by xdm
__DISPLAY="$DISPLAY" # The DISPLAY set by xdm for this session
__XAUTHORITY="$XAUTHORITY" # Should be empty in the most cases
readonly __HOME __DISPLAY __XAUTHORITY

#
# Read the default system settings.
#
test -r /etc/profile && { . /etc/profile > /dev/null 2>&1 ; }
set +u > /dev/null 2>&1

#
# Some system defaults
#
: ${XLIBDIR=/usr/X11R6/lib/X11}
: ${OPENWINHOME=/usr/openwin}
readonly XLIBDIR

#
# the users ~/.profile
#
test -r ${HOME}/.profile && { . ${HOME}/.profile > /dev/null 2>&1 ; }
set +u > /dev/null 2>&1

#
# Restore
#
HOME="$__HOME"
DISPLAY="$__DISPLAY"
XAUTHORITY="$__XAUTHORITY"
TERM=xterm
#
export OPENWINHOME TERM DISPLAY HOME
test -z "$XAUTHORITY" && unset XAUTHORITY || export XAUTHORITY

#
# Check path (paranoid)
#
type -p xdm > /dev/null 2>&1 || PATH=$PATH:/usr/X11R6/bin

#
# Handle arguments given by xdm.
#
set -- $argv
if test $# -ge 1 ; then
case "$1" in
failsafe)
shift
exec $failsafe
;;
*)
#
# KDM may overwrites this
#
WINDOWMANAGER=$1 ; export WINDOWMANAGER
if test $# -ge 2 && test -n "$2" ; then
LANG=$2 ; export LANG
fi
shift $#
;;
esac
fi

#
# Reset default background and cursor.
#
xsetroot -def
xsetroot -cursor_name top_left_arrow

#
# Some common user and system files,
# do not use `: ${xx=yy}' here.
#
xdefaults=$HOME/.Xdefaults
xresources=$HOME/.Xresources
xmodmap=$HOME/.Xmodmap
session=$HOME/.xsession
xinitrc=$HOME/.xinitrc
openwin=$OPENWINHOME/bin/openwin
errinit=$XLIBDIR/xinit/xinitrc
errsess=$XLIBDIR/xdm/sys.xsession

#
# Handle the users Xmodmap and Xresources
#
test -r "$xmodmap" && xmodmap "$xmodmap"
if test -r "$xdefaults" ; then
xrdb -I$HOME -load -retain "$xdefaults"
test -r "$xresources" && xrdb -I$HOME -merge "$xresources"
elif test -r "$xresources" ; then
xrdb -I$HOME -load -retain "$xresources"
fi

# User session
# If the user doesn't have their own xsession, then run
# xinitrc if they exist

readonly XSESSION_IS_UP=yes
export XSESSION_IS_UP

if test -f $session ; then
test -x $session && exec $session
exec /bin/sh $session
elif test -f $xinitrc ; then
test -x $xinitrc && exec $xinitrc
exec /bin/sh $xinitrc
elif test -f $errsess; then
test -x $errsess && exec $errsess
exec /bin/sh $errsess
elif test -f $errinit ; then
test -x $errinit && exec $errinit
exec /bin/sh $errinit
elif test -f $openwin ; then
test -x $openwin && exec $openwin
exec /bin/sh $openwin
else
test -n "$WINDOWMANAGER" && exec $WINDOWMANAGER
fi

#
# Call failsafe
#
exit 1


Moreover i tried to add more options to the files to get options for other widow managers as describer in kde handbook....but of no use.

plzz help
 
Old 10-10-2003, 05:49 PM   #2
jailbait
Guru
 
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Debian Wheezy, Debian Jessie
Posts: 7,593

Rep: Reputation: 188Reputation: 188
"Following is the listing of kdmrc and Xsession(i guess these are two that are responsible for the act)"

There are two ways to do what you are trying to do. One way is working with kdmrc, .xinitrc, and Xsessions as you are doing (but don't forget xinitrc). The other way is make your changes in Control Center -> System Administration -> Login manager. At various times I have done it both ways.


" I logged on and what i get is just console...which allowed me run everything. But there was no window manager."

Your kdmrc is set up to allow you to get kde and console. The fact that you cannot get kde is probably because your .xinitrc has been changed.

Your .Xsessions has been changed significantly from mine. My .Xsessions is set up so that if .xinitrc is screwed up then you will get kde as a default. In your .Xsessions
I think that the default is to run bash if xinitrc is screwed up.

What I think that you need to do to fix your problem is to get back to the .Xsessions and .xinitrc that you had before the Yast Online Update. then if necessary make changes in Control Center -> System Administration -> Login manager.


___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites
 
Old 10-11-2003, 02:35 AM   #3
fundoovikas
LQ Newbie
 
Registered: Sep 2003
Distribution: Fedora Core 1
Posts: 2

Original Poster
Rep: Reputation: 0
I looked into .xinitrc but could not find anything that looked bad.

Moreover, i couldn't find the backup copy as well....so I guess i'm still stuck where I originally was.

can u send me a copy of ur kdmrc, .xinitrc, and Xsession....so that I can copy them onto my system after making relevant changes if any
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
startx/graphical login manager darkleaf Linux - Security 18 10-10-2004 10:11 AM
Adding Window Manager to Login Screen JSmith Linux - Newbie 1 09-28-2004 12:40 AM
What Next after LogIn (graphical screen)?? kodai Linux - Newbie 20 09-16-2004 11:50 AM
Graphical Login Screen? neocookie Linux - Software 17 06-07-2004 06:10 PM
[poll] Do you use a graphical login manager or not? sti Linux - General 15 01-31-2004 06:44 AM


All times are GMT -5. The time now is 05:31 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration