Announcement

**sithlord48** · May 11, 2011, 08:40 PM

Re: HELP!! Did most recent upgrades (Mon May 9) to Natty and lost KDE Login

can you boot in to "recovery mode"? hold shift right after your bios screen to get to the grub2 menu and select recovery mode, if it boots up choose the root terminal option from the list and try this command

Code:

dpkg --configure -a

you may have some packages not set up fully.

**mistchild** · May 12, 2011, 01:36 PM

Re: HELP!! Did most recent upgrades (Mon May 9) to Natty and lost KDE Login

Did do recovery mode.

Did clean up repository, it also did the new pending updates.

Shut down the system (Halt)

Rebooted and came up to KDE (spinning balls are post boot it seems)

At login tried logging in and NO JOY.

Still get the "ccccccccccccc..." command not found thing at virtual terminal (Looks like during /etc/bashrc.bash.

Login into KDE -> Does not do the devices picture -> flashes a rectangle (konsole?) on left of screen with a black background (Rectangle is off while color which is why I think it is a console trying to come up) -> Bubbles -> Login box displayed.

Sigh

Still in need of HELP!!

**sithlord48** · May 12, 2011, 01:45 PM

Re: HELP!! Did most recent upgrades (Mon May 9) to Natty and lost KDE Login

maybe that file has an issue, you can compair the contents of you /etc/bash.bashrc to mine

Originally posted by /etc/bash.bashrc

# System-wide .bashrc file for interactive bash(1) shells.

# To enable the settings / commands in this file for login shells as well,
# this file has to be sourced in /etc/profile.

# If not running interactively, don't do anything
[ -z "$PS1" ] && return

# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize

# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi

# set a fancy prompt (non-color, overwrite the one in /etc/profile)
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '

# Commented out, don't overwrite xterm -T "title" -n "icontitle" by default.
# If this is an xterm set the title to user@host:dir
#case "$TERM" in
#xterm*|rxvt*)
# PROMPT_COMMAND='echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD}\007"'
# ;;
#*)
# ;;
#esac

# enable bash completion in interactive shells
#if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
# . /etc/bash_completion
#fi

# sudo hint
if [ ! -e "$HOME/.sudo_as_admin_successful" ]; then
case " $(groups) " in *\ admin\ *)
if [ -x /usr/bin/sudo ]; then
cat <<-EOF
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

EOF
fi
esac
fi

# if the command-not-found package is installed, use it
if [ -x /usr/lib/command-not-found -o -x /usr/share/command-not-found ]; then
function command_not_found_handle {
# check because c-n-f could've been removed in the meantime
if [ -x /usr/lib/command-not-found ]; then
/usr/bin/python /usr/lib/command-not-found -- $1
return $?
elif [ -x /usr/share/command-not-found ]; then
/usr/bin/python /usr/share/command-not-found -- $1
return $?
else
return 127
fi
}
fi

**mistchild** · May 12, 2011, 03:42 PM

Re: HELP!! Did most recent upgrades (Mon May 9) to Natty and lost KDE Login

The files are the same except for the trap I put in bash.bashrc.

Is there a way to clear out any saved sessions? I have no idea what file would have that information for Plasma. Given the initial Plasma message (before the first login attempt) and the flash of a possible attempt to restore a konsole terminal session, I wonder if that is kicking the bucket over?

Thanks by the way for all the help.

**The Liquidator** · May 12, 2011, 04:43 PM

Re: HELP!! Did most recent upgrades (Mon May 9) to Natty and lost KDE Login

From the recovery mode choose the terminal login option and type:

Code:

sudo startx

If you get into a kde session you will have done 2 things:

1. Committed the cardinal sin of logging in as root to kde and

2. Established that there is something wrong with your user settings, as opposed to the system itself.

If that is the case go into your user directory with dolphin and select view/show hidden files and rename the folder .kde/share/config (a .old prefix is the norm). That will establish a completely clean kde configuration which hopefully will now get you in. Once running if you wish you can copy files from the old folder to the new one, but as all this does is to reset the kde-based applications without destroying data a new start might be the best thing.

If, however, the root login doesn't get you in, then the problem is at a more fundamental level and I wouldn't know what to do either.

HTH

**mistchild** · May 12, 2011, 06:05 PM

Re: HELP!! Did most recent upgrades (Mon May 9) to Natty and lost KDE Login

Well, that did not work either (config -> config.old and reboot).

I also still get the stupid command not found.

I may just give up and reinstall natty into the /boot, /, /tmp, /usr, /opt, /var I have and leave the rest of the partitions alone until re-installed.

I pulled my current /etc and network stuff to the side as that is all I should need to rebuild. And I backed up the /home particularly

It will give me a chance to not have some of the packages I installed that I never use

**mistchild** · May 12, 2011, 08:47 PM

Re: HELP!! Did most recent upgrades (Mon May 9) to Natty and lost KDE Login

Interesting - I am trying to redefine my boot disk device (sda1 - 12 partitions).

Recording so I may later file a bug report if I get closer.

There seems to be a bug in the Live/Recovery/Install disk for natty for AMD64.

The partitioner for manual formatting keeps failing

So I went to the live disk and put in all the partitions on the disk successfully using the
kpartition tool from the applications menu (possibly miss named the partitioner here) which got the job done.

Back to the install mode. I can set 4 mount points (I have 10) and the manual mode crashes and takes me back to the desktop.

(It seems to be a python error).

More later or a bug number.

Needless to say, this is annoying.