BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

View previous topic View next topic Go down

BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by CureMyMind on Tue May 17, 2011 2:08 am

KDE Login Gui

1. To make the login gui which should be in (Dragon Icon start button) then (Settings) and then click on (System Settings). You would scroll down to where it says (Login Screen). In the Login screen gui you will look at the tabs which should be (General)(Dialog)(Background)(Theme)(Shoutdown)(Users)(Convenience). You will click on the one that says (Theme) and you should be able to see the buttons (Install new theme)(Remove Theme)(Get new theme). You will click on (Get New theme) and download the themes you want. I got a theme called Asphyxia which you can type in the search to see what im talking about. Once you have the theme that you want. Click on that theme and click Apply.

2. Now you will need to download my kdm file that you will replace in /etc/inti.d/ folder. There should already be a kdm in there but just replace it. Remember to 1st back up everything.

Download my KDM from here
mediafire.com mediafire.com/?suovw19vfbirq

This is what is in there if you just want to change the information with your text editor. I used gedit, I 1st right clicked on kdm and opened it with gedit. then typed this in.
Code:
#!/bin/sh
### BEGIN INIT INFO
# Provides:          x-display-manager kdm
# Required-Start:    $local_fs $remote_fs hal
# Required-Stop:    $local_fs $remote_fs hal
# Should-Start:      console-screen
# Should-Stop:      console-screen
# Default-Start:    2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: X display manager for KDE
# Description:      KDM manages a collection of X servers, which may be on the local host or remote machines.
### END INIT INFO
# /etc/init.d/kdm: start or stop the X display manager
# Script originally stolen from the xdm package
#
# description: K Display Manager
#
set -e

# Import the LSB init functions
. /lib/lsb/init-functions

# To start kdm even if it is not the default display manager, change
# HEED_DEFAULT_DISPLAY_MANAGER to "false."
HEED_DEFAULT_DISPLAY_MANAGER=true
DEFAULT_DISPLAY_MANAGER_FILE=/etc/X11/default-display-manager

PATH=/bin:/usr/bin:/sbin:/usr/sbin
DAEMON=/usr/bin/kdm
PIDFILE=/var/run/kdm.pid
UPGRADEFILE=/var/run/kdm.upgrade

# parameters to support kdm customization
KDMRC=/etc/kde4/kdm/kdmrc
BACKGROUNDRC=/etc/kde4/kdm/backgroundrc

#if configuration is changed by kdmtheme or other tools, don't do magick
if grep -q "Theme=@@@ToBeReplacedByDesktopBase@@@" ${KDMRC} && grep -q "Wallpaper=default_blue.jpg" ${BACKGROUNDRC}
then



KDMOVERRIDEDIR=/etc/default/kdm.d
KDMCFGDIR=/var/run/kdm
KDMCFG=$KDMCFGDIR/kdmrc
BACKGROUNDCFG=$KDMCFGDIR/backgroundrc

test -x $DAEMON || exit 0

# uncomment, if you want auto-logon to be runlevel-dependant
#test "$runlevel" || { runlevel=`runlevel`; runlevel=${runlevel#* }; }
#test "$runlevel" = 4 && ARG=-autolog || ARG=-noautolog

# uncomment, if you want tons of debug info in your syslog
#ARG="$ARG -debug 255"

# we use an alternative kdm master configuration file
ARG="$ARG -config $KDMCFG"

# we source overrides. run-parts sorts the list in a predictable order
if [ -d "$KDMOVERRIDEDIR" ]; then
    for part in $(run-parts --list "$KDMOVERRIDEDIR" 2>/dev/null || true); do
        . "$part"
    done
fi

# we generate kdm configuration files
genkdmconf --in $KDMCFGDIR 1> /dev/null

# we update kdm configuration files (only overridden values)
[ -n "$USEBACKGROUND" ] && sed -i "s|^#\?UseBackground=.*|UseBackground=$USEBACKGROUND|" $KDMCFG
[ -n "$BACKGROUNDCFG" ] && sed -i "s|^#\?BackgroundCfg=.*|BackgroundCfg=$BACKGROUNDCFG|" $KDMCFG
[ -n "$USETHEME" ] && sed -i "s|^#\?UseTheme=.*|UseTheme=$USETHEME|" $KDMCFG
[ -n "$THEME" ] && sed -i "s|^#\?Theme=.*|Theme=$THEME|" $KDMCFG
[ -n "$WALLPAPER" ] && sed -i "s|^#\?Wallpaper=.*|Wallpaper=`readlink -f $WALLPAPER`|" $BACKGROUNDCFG


fi
# autologin overrides are useful for live debian environment
if [ -n "$AUTOLOGINUSER" ]; then
   sed -i "s|^#\?AutoLoginEnable=.*|AutoLoginEnable=true|" $KDMCFG
   sed -i "s|^#\?AutoLoginUser=.*|AutoLoginUser=$AUTOLOGINUSER|" $KDMCFG
fi
[ -n "$AUTOLOGINDELAY" ] && sed -i "s|^#\?AutoLoginDelay=.*|AutoLoginDelay=$AUTOLOGINDELAY|" $KDMCFG
[ -n "$AUTOLOGINAGAIN" ] && sed -i "s|^#\?AutoLoginAgain=.*|AutoLoginAgain=$AUTOLOGINAGAIN|" $KDMCFG
[ -n "$AUTOLOGINLOCKED" ] && sed -i "s|^#\?AutoLoginLocked=.*|AutoLoginLocked=$AUTOLOGINLOCKED|" $KDMCFG

# If we upgraded the daemon, we can't use the --exec argument to
# start-stop-daemon since the inode will have changed.  The risk here is that
# in a situation where the daemon died, its pidfile was not cleaned up, and
# some other process is now running under that pid, start-stop-daemon will send
# signals to an innocent process.  However, this seems like a corner case.
# C'est la vie!
if [ -e $UPGRADEFILE ]; then
  SSD_ARGS="--pidfile $PIDFILE --startas $DAEMON"
else
  SSD_ARGS="--pidfile $PIDFILE --exec $DAEMON"
fi

stillrunning () {
  if expr "$(cat /proc/$DAEMONPID/cmdline 2> /dev/null)" : "$DAEMON" > /dev/null 2>&1; then
    true
  else
    # if the daemon does not remove its own pidfile, we will
    rm -f $PIDFILE $UPGRADEFILE
    false
  fi;
}

case "$1" in
  start)
    if [ -e $DEFAULT_DISPLAY_MANAGER_FILE ] &&
      [ "$HEED_DEFAULT_DISPLAY_MANAGER" = "true" ] &&
      [ "$(cat $DEFAULT_DISPLAY_MANAGER_FILE)" != "$DAEMON" ]; then
      echo "Not starting K Display Manager (kdm); it is not the default display manager."
    else
      echo -n "Starting K Display Manager: kdm"
      start-stop-daemon --start --quiet $SSD_ARGS -- $ARG || echo -n " already running"
      echo "."
    fi
  ;;

  restart)
    /etc/init.d/kdm stop
    if [ -f $PIDFILE ]; then
      if stillrunning; then
        exit 1
      fi
    fi
    /etc/init.d/kdm start
  ;;

  reload)
    echo -n "Reloading K Display Manager configuration..."
    if start-stop-daemon --stop --signal 1 --quiet $SSD_ARGS; then
      echo "done."
    else
      echo "kdm not running."
    fi
  ;;

  force-reload)
    /etc/init.d/kdm reload
  ;;

  stop)
    echo -n "Stopping K Display Manager: kdm"
    if [ ! -f $PIDFILE ]; then
      echo " not running ($PIDFILE not found)."
      exit 0
    else
      DAEMONPID=$(cat $PIDFILE | tr -d '[:blank:]')
      KILLCOUNT=1
      if [ ! -e $UPGRADEFILE ]; then
        if start-stop-daemon --stop --quiet $SSD_ARGS; then
          # give kdm's signal handler a second to catch its breath
          sleep 1
        else
          echo -n " not running"
        fi
      fi
      while [ $KILLCOUNT -le 5 ]; do
        if stillrunning; then
          kill $DAEMONPID
        else
          break
        fi
        sleep 1
        KILLCOUNT=$(( $KILLCOUNT + 1 ))
      done
      if stillrunning; then
        echo -n " not responding to TERM signal (pid $DAEMONPID)"
      else
        rm -f $UPGRADEFILE
      fi
    fi
    echo "."
  ;;
  status)
    status_of_proc -p "$PIDFILE" "$DAEMON" kdm && exit 0 || exit $?
  ;;

  *)
    echo "Usage: /etc/init.d/kdm {start|stop|restart|reload|force-reload|status}"
    exit 1
    ;;
esac

exit 0

If you do not change the information it will not load your login gui.

3. Now you will open up the terminator or shell what ever your using and type this command in there.
Code:
root@bt:~# update-rc.d kdm defaults

4. Reboot and see if it loaded. If it didn't then use this next command b/c it might not of gotten the execuetable in the shell script. Go in to the folder 1st then use the command. Use the command "cd /etc/inti.d" with out the quotes.
Code:
root@bt:/etc/init.d/# sudo chmod +x kdm

5. If you need to go back to CLI then look at this page.CLI or KDM Theme

Loading Boot Splash

This one is simply just go to (Dragon Icon start button) then (Settings) and then click on (System Settings). Click on (Workspace Appearance) Then On Splash Screen and then on (Get New Themes...) I used the Asphyxia one which can be found there, just type it in the search box. click on your splash screen and select apply. Your done.

Change background wallaper

Right click on any where on your desktop and in the mouse menu just select (Folder View Settings Alt+D, Alt+S) which should be at the bottom. It should open up with the wallpaper. Click on Get New Wallapapers... and I leave the rest to you.

That was a tuff one wasn't it...

If you like the asphyxia as a wallpaper you can download it from the creator here. Wallpaper

To view all this information on video Then watch here.

_______________________________________________
I don't do things because they are hard nore because they are needed. I do them simply because I can -CureMyMind

CureMyMind
Admin

Posts: 69
Join date: 2011-01-15

View user profile http://curemymind.4umer.net

Back to top Go down

Re: BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by 12600 on Tue Jul 26, 2011 10:00 pm

For some reason this didn't work on mine. Is there a typo in your file code script on the forum?

12600

Posts: 8
Join date: 2011-07-22

View user profile

Back to top Go down

Re: BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by CureMyMind on Wed Jul 27, 2011 1:54 am

12600 wrote:For some reason this didn't work on mine. Is there a typo in your file code script on the forum?

Did you edit the kdm in the /etc/init.d/? how does your's look like? I uploaded what worked for me... I'm not sure why it doesn't work for you... before you go into GUI, try this...

Code:
root@bt:~# service kdm start
In the CLI before you log into the GUI... Let me know what you get...

_______________________________________________
I don't do things because they are hard nore because they are needed. I do them simply because I can -CureMyMind

CureMyMind
Admin

Posts: 69
Join date: 2011-01-15

View user profile http://curemymind.4umer.net

Back to top Go down

Re: BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by 12600 on Fri Jul 29, 2011 4:40 am

That brought it up, so how do i get it to start kdm automatically?

Edit: Nvm, i found the problem. Even though I did do the very last command after it didn't boot it the first time round, it didn't work. So just did it again and now it works great.


Last edited by 12600 on Fri Jul 29, 2011 5:06 am; edited 1 time in total (Reason for editing : Figured it out.)

12600

Posts: 8
Join date: 2011-07-22

View user profile

Back to top Go down

Re: BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by Omyna on Wed Dec 21, 2011 11:04 pm

Hi there! Has anybody tried to do this on KDE R1? I've followed all the steps above and have had no success... When I navigate over to the folder where the original KDM file sits, it appears as if it is a shortcut to the KDM file... I'm logged in as root, so I figured that couldn't be the problem. I'm having trouble I guess actually finding the source KDM file.. I'm a noob, wet behind the ears still to BackTrack and this site. Be gentle.....! Very Happy (BackTrack 5 KDE R1 32bit)

Omyna

Posts: 2
Join date: 2011-12-21

View user profile

Back to top Go down

Re: BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by Omyna on Wed Dec 21, 2011 11:07 pm

Also, could this code be used with any login screen? or is it limited to Asphyxia only? Cheers!

Omyna

Posts: 2
Join date: 2011-12-21

View user profile

Back to top Go down

Re: BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by CureMyMind on Mon Jan 09, 2012 5:14 pm

Omyna wrote:Also, could this code be used with any login screen? or is it limited to Asphyxia only? Cheers!


The code is for all login screen's that is KDE... I havent been able to figure out GNOME.. But IDK I also haven't been playing with it.. I kind of took a long brake for xmas and new years but I should start to figute more out later...

_______________________________________________
I don't do things because they are hard nore because they are needed. I do them simply because I can -CureMyMind

CureMyMind
Admin

Posts: 69
Join date: 2011-01-15

View user profile http://curemymind.4umer.net

Back to top Go down

Re: BackTrack 5 KDE Login GUI, Boot splash, Wallpaper

Post by CureMyMind on Mon Jan 09, 2012 5:25 pm

Omyna wrote:Hi there! Has anybody tried to do this on KDE R1? I've followed all the steps above and have had no success... When I navigate over to the folder where the original KDM file sits, it appears as if it is a shortcut to the KDM file... I'm logged in as root, so I figured that couldn't be the problem. I'm having trouble I guess actually finding the source KDM file.. I'm a noob, wet behind the ears still to BackTrack and this site. Be gentle.....! Very Happy (BackTrack 5 KDE R1 32bit)

I took a long brake from xmas and new years. I have tried this in KDE R1 32bit and it works there. Did you see the youtube video at the bottom of this? You have to modify the KDM file and also open up the konsole and tell it to be a program and then tell it to execute it at boot up. The modification should be in the tutorial, look where it says how to make shell skripts executable on google it should give you the "chmod" command, or you can simply right click on the file go to its properties. There should be a box to check to make it executable. Once you made it executable, you would then have to tell it to load at boot up. The command for bootup would be that update-rc.d kdm defaults. I know there are other command for executable like the chmod 755 and the one i mention in this video. I would google "linux chmod" that way you know google is looking for the command chmod and its for linux... This is a short summery of what the tutorial should be like.. You will have to open the KDM file and or download the one i have in this video.. But you have to modify it. What exactly did you do to the KDM file?

_______________________________________________
I don't do things because they are hard nore because they are needed. I do them simply because I can -CureMyMind

CureMyMind
Admin

Posts: 69
Join date: 2011-01-15

View user profile http://curemymind.4umer.net

Back to top Go down

View previous topic View next topic Back to top


Permissions in this forum:
You cannot reply to topics in this forum