superuser privelege problems.
steven vollom
stevenvollom at sbcglobal.net
Sun Jun 7 17:31:52 UTC 2009
On Sunday 07 June 2009 04:30:48 pm Willy K. Hamra wrote:
> steven vollom wrote:
> > On Sunday 07 June 2009 03:39:25 pm clay weber wrote:
> >> steven vollom wrote:
> >>> I just typed in the command line, sudo apt-get install
> >>> kubuntu-restricted- extras and got a funny response. I get the
> >>> following response:
> >>>
> >>> steven at Yeshua:~$ sudo apt-get install kubuntu-restricted-extras
> >>> [sudo] password for steven:
> >>> E: Type '.debs' is not known on line 55 in source list
> >>> /etc/apt/sources.list E: The list of sources could not be read.
> >>> steven at Yeshua:~$ sudo apt-get install kubuntu-restricted-extras
> >>> E: Type '.debs' is not known on line 55 in source list
> >>> /etc/apt/sources.list E: The list of sources could not be read.
> >>> steven at Yeshua:~$
> >>>
> >>> I just made a fresh install of jaunty w/kde 4.2.2. TIA for help.
> >>>
> >>> Steven
> >>
> >> There is an error on line 55 of your /etc/apt/sources.list file.
> >> probably a typo involving the phrase '.debs'. If you can post that line,
> >> or even the whole file, we can quickly see what needs to be edited.
> >>
> >> clay
> >
> > Hi Clay,
> >
> > There are two strange things on the apt page. The folder
> > 'sources.list.d' and the 'apt.conf.d' looked strange, however are
> > probably correct. This is line 55:
> >
> > .debs for Ubuntu Hardy (8.04), Intrepid (8.10), and Jaunty (9.04) .debs
> > for Ubuntu Hardy (8.04), Intrepid (8.10), and Jaunty (9.04) .debs for
> > Ubuntu Hardy (8.04), Intrepid (8.10), and Jaunty (9.04) .debs for Ubuntu
> > Hardy (8.04), Intrepid (8.10), and Jaunty (9.04) .debs for Ubuntu Hardy
> > (8.04), Intrepid (8.10), and Jaunty (9.04) .debs for Ubuntu Hardy (8.04),
> > Intrepid (8.10), and Jaunty (9.04) .debs for Ubuntu Hardy (8.04),
> > Intrepid (8.10), and Jaunty (9.04)
> >
> > I am sure it should probably start at the very beginning of the line, not
> > one character in, and I suppose the repeating of it, over and over, is
> > the problem. What do you suppose caused that? If I am correct, do I
> > have to use a sudo command with kate to edit it? And if sudo doesn't
> > work, how do I get the permission needed to edit the line? I hope these
> > are not stupid thoughts.
> >
> > I typed into Alt+F2 and then typed sudo kate, and nothing opened up. I
> > still wonder if demons are in my machine.
> >
> > Steven
>
> first of all, what you have in sources.list is total meaningless
> gibberish. sources.list has a format of:
> deb http://blah.blah.blah blah blah
>
> as for the above, are meaningless, not sure what is intended here, or
> why did you add them, i want to see your complete sources.list.
> secondly, sources.list.d and apt.conf.d are perfectly normal to be
> there, don't edit them, don't do anything with them
> thirdly, we had a very long discussion steven about sudo and kdesudo
> only few days ago. sudo is for console application, you can't use in
> alt+f2!!! it needs a console to ask for the password. you use kdesudo.
This is the complete list:
deb cdrom:[Kubuntu 9.04 _Jaunty Jackalope_ - Release i386 (20090420.1)]/
jaunty main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty universe
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty universe
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-backports main restricted
universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-backports main
restricted universe multiverse
## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://archive.canonical.com/ubuntu jaunty partner
deb-src http://archive.canonical.com/ubuntu jaunty partner
deb http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-src http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb http://security.ubuntu.com/ubuntu jaunty-security universe
deb-src http://security.ubuntu.com/ubuntu jaunty-security universe
deb http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-src http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-proposed restricted main
multiverse universe
.debs for Ubuntu Hardy (8.04), Intrepid (8.10), and Jaunty (9.04) .debs for
Ubuntu Hardy (8.04), Intrepid (8.10), and Jaunty (9.04) .debs for Ubuntu Hardy
(8.04), Intrepid (8.10), and Jaunty (9.04) .debs for Ubuntu Hardy (8.04),
Intrepid (8.10), and Jaunty (9.04) .debs for Ubuntu Hardy (8.04), Intrepid
(8.10), and Jaunty (9.04) .debs for Ubuntu Hardy (8.04), Intrepid (8.10), and
Jaunty (9.04) .debs for Ubuntu Hardy (8.04), Intrepid (8.10), and Jaunty
(9.04)
In prior attempts to get an application installed, I tried kdesudo apt-get,
then I tried kdesudo aptitude, then I tried sudo apt-get, next I tried sudo
aptitude and the item. Nothing worked. All spoke of a problem. Because the
language after creating a workable command has been so confusing to me, I have
not tried to translate it's meaning until recently. In the last couple of
days I have been reading the product of a failed command. Sometimes it is
somewhat understandable, but mostly confusing yet. And when it says to refer
to man, I try that too, but the man pages are as confusing to me as what ends
up in the entries that follow a command. Had I just attempted to trace that
line 55 comment, I would have seen that long line of repeating information.
I did try kdesudo first. In fact every time I would normally use sudo, I tried
kdesudo. But wget and aptitude and sudo and kdesudo still get me confused. I
don't really know when sudo takes preference over kdesudo, but I have heard
enough people say to use kdesudo that I use it almost always. The one
exception is a sudo command that has always worked and been recommended
several times, I will use the sudo command because it is shorter. As far as
aptitude and apt-get or when weget or wget is used, I still don't get that
part.
There are a lot of things that are crystal to an experienced user that are
both similar and different to an inexperienced person, and when you are unclear
about the terminology most of the time, the ones that are similar get mixed
together in my mind. I wish I had one day where I worked along side an
experienced user, so that I could get an answer to a problem without the long
wait that causes me to forget of confuse things in my memory. And I never
stop working, so when I post a question I am working on totally unrelated stuff
when the answer comes. I am not trying to make excuses, just allow you to
understand what goes through my mind when I have to wait for the answer to a
question. When you have people and/or experts close by, you can get an answer
before you forget all the details that make up the question. I have never had
that, except one day when an experienced friend came over. And he sat at the
computer and input data faster than I could read it. I saw the great skill in
action, but I didn't learn anything and never had an opportunity to ask a
question, so that I could get a rapid response when everything is fresh. And
I just love you guys for taking the time to help me struggle through it.
And Willie, you guys don't always agree. Sometimes there are 3 or 4 different
opinions. How would you deal with 4 different solutions from four people you
respect. To accept one over another is indicating you think he is more
expert. When things don't work out, the one who really is the expert, can't
understand why you didn't take his advice. In fact there is lots of
conflicting input when it comes to sudo and kdesudo; sometimes a person will
enter a conversation with two people working the problem just to put his
opinion in play. And when you are confused about almost everything, it is
challenging. I wish there was a real pecking order that everyone more or less
agreed upon. That way the generals could trump the lieutenants and the
lieutenants could trump the privates, even thought the privates occasionally
will have the best solution. I am sitting here laughing about what I am
writing, because it is almost always in the mix somewhere. And it sure beats
the dickens out of not having anyone to ask the question like it used to be
for me. That is why I love you all so much. I get answers. But, I do use
kdesudo first now. Because it is for gui stuff, and everything I do with a
computer is gui. But if it doesn't work, I am inclined to at least try the
only thing that worked for me up till now, and that is sudo - and then the su
users enter once in a while. Hah Hah. Because you all know this stuff, it
doesn't even cross your minds, I bet how confusing it can be for someone who
doesn't yet have a grasp on things. No matter what, though, I will never give
up, so if you get tired of trying to soften my rock brain, I will just beat it
against the wall until I soften it up. Quiting is not in my nature.
Ongoing thanks.
Steven
More information about the kubuntu-users
mailing list