Bruce Marshall <bmarsh at bmarsh.com>

[Macario Valle]

Or, if you do not wish to reboot, but want to fix your problem anyways
do the following:
	ps -ewf| grep adept|grep -v grep|awk '{print $2}'

This will list all process being used by adept, one per line.  Next you
want a sure way to destroy these processes:

sudo kill -9 <process>

Where <process> is each process number separated by a space.  for
example if you got two lines like these:
7513
12158

Your command will look like this:

sudo kill -9 7513 12158

Tpe your password when asked for it here.

Once that is done, just use adept as you  ussually do.

Note: if you did not get any process numbers, it might be some apt-get
process, in this case replace 'adept' in the first command for 'apt'
instead.

There is no need to be afraid of command line.  It just take a little
getting used to, and can make you feel all powerfull or utterly dumb,
when you succeed or fail.

On Mon, 2007-06-04 at 12:40 -0400, Bruce Marshall wrote:
> On Monday 04 June 2007, Robin Taylor wrote:
> > > Please help me.  When I finally figure out how to operate Kubuntu, I will
> > > repay your kindness by answering the questions of other rockheads like me
> > > and take that problem away from the forum.
> 
> Hey....  another old fart here answering your question......
> 
> The way *ubuntu is setup is to use the 'sudo' command to issue root commands.
> 
> I think if you're having this much trouble (nothing wrong with that)  that you 
> shouldn't try for an su password at all.   Try the sudo route.  It will do 
> what you want.
> 
> How-some-ever,  your problem with adept is not going to go away with an su or 
> any other password by itself.   And I will tell you from experience, that you 
> can't dig far enough to eliminate the problem with  bit twiddling.
> 
> I once posted to try:
> 
> dpkg -a --configure
> 
> but what I should have said was to use:
> 
> sudo dpkg -a --configure
> 
> Get yourself a console session and try that and post the results.
> 
> There are a few other incantations that can be tried but that's a start.
>