No need to reformat or start again. But there is a lesson in this. Stick to the
repositories unless you know what you are doing.

Open a terminal and type:
sudo aptitude purge package_name.

Well, that didn't work to well!
I got the messages
1. Wasn't able to locate file Thimght mean you need to manually fix
this package
2. Couldn't lock list directory. are you root

As for repostiories, can't do that in this case as this is a new cam
program that I am trying to learn how to use in linux. This really
is my test bed for learning "how to"

You might want to read up a bit on de-installing programs from the commandline.
When issuing a command that requires root privileges (and installing or
deinstalling does) you need to use sudo in Ubuntu. If the command prompt is $
then use sudo first in Ubuntu.

Here is a deb guide:
www.debian.org/.../ch-dpkg.html
or
linuxhelp.blogspot.com/.../...-primer-for-new.html
More detailed dpkg explanation: http://linuxreviews.org/man/dpkg/

You can use sudo before the command or you can temporarily change to root with
sudo -i. You will see the prompt change from $ to # as you go from user to root
level.

If you are asking yourself why you are using the commandline, this is punishment
inflicted on unwary users who get into problems by wandering off the beaten path
by downloading bad deb files and installing them instead of sticking with those
in the repositories. Not really. :) It is a powerful tool where you can use
switches and wildcards that aren't available from the GUI. Sometimes apt or dpkg
will break if you install outside of the repositories and in those cases you
need a powerful tool to get out of it. I have done this many times, so take
heart. It can happen to anyone. You can protect yourself in the future by
sticking with known entities. Sorry for needling you about this. However, once
you are able to fix problems then you can allow yourself more freedom to get
into them in the future.

Thanks so much for the links, that is exactly what I have been
looking for, but either have used either the wrong search words or
missed them with all the hits!

As for the command line, that I don't mind. Years ago, my company
decided to go with windows 3.1 and later 95 and I was fighting it all
the way. I like and still use the command line and have a machine
that is pure dos for my cnc machine.

Again, thank you for the links and this will give me material to mull over.