I killed kpackage :(

[sue]

When I try to get it going I receive the following error:

"No package cache is available.
The package list needs to be rebuilt.
This should have been done by the backend automatically."

How do I fix this?

[dibl]

Re: I killed kpackage

Try, in a Konsole window,

sudo dpkg --configure -a

sudo apt-get autoclean

post any errors if they are shown.

[sue]

Re: I killed kpackage

With sudo included, I was unable to type my password, without sudo I was able to input password when it was requested, but................
Command not found?

[dibl]

Re: I killed kpackage

I was unable to type my password

You mean you typed it, but you didn't see anything on the screen? That is normal -- Linux does not show any feedback when a password is entered, for security. Enter the command as I wrote it, then when the password prompt comes up, enter your password exactly as you did during installation, and then press "Enter". Post back with the results.

[sue]

Re: I killed kpackage

nope, in konsole I could not type at all after using the sudo. When I tried without I could type it, and see it.
Solved that problem by triggering a prompt for password elsewhere, then doing it.
Result:
E: Type 'http://packages.debian.org/sid/text/...t/fbreaderdeb' is not known on line 39 in source list /etc/apt/sources.list
E: The list of sources could not be read.
kola@Ks:~$

[dibl]

Re: I killed kpackage

Aha -- someone's been playing with Automatix, or otherwise twiddling her source repositories!

Until you build a modicum of proficiency with your Linux system, it is very advisable to steer clear of attempts to install software packages that are not available in the default Kubuntu repositories. Among other risks, you can mess up your source list, like this.

So, without knowing what else is amiss, you need to open your source list file for editing, in Super User mode, and delete that particular line. To open it directly from your user session, press Alt-F2 and enter the following in the launcher window:

kdesudo kate /etc/apt/sources.list

and give it your password.

Now cursor down to the offending line that is shown in your error output, and carefully delete it, making sure not to disturb the lines above or below it. If it is the last line in the file, make sure there is a hard return after the new last line (i.e. make sure the cursor can go down to the next blank line). Then click "File > Save" to save the edited file, and then "File > Close" and "File > Exit". When you have exited kate, you can try again with the

sudo dpkg --configure -a

command and the other one, and see if it will process without error.

For future reference, note that you could have simply entered

kdesudo kate

in the launcher, and then browsed with kate to the system file that you need to edit.

[sue]

Re: I killed kpackage

That is very odd, I have not messed with any source repos and I have no idea what Automatix is. (Hhmm, suspicious glare at the cat....)

Anyways, tried that, got this: (Dunno what Wesnoth has to do with it, that was installed quite a bit before this started up)

Reading package lists... Done
Building dependency tree
Reading state information... Done
Del wesnoth-nr 1:1.6a-3ubuntu1 [3212kB]
Del wesnoth-did 1:1.6a-3ubuntu1 [2985kB]
Del wesnoth-aoi 1:1.6a-3ubuntu1 [2232kB]
Del wesnoth-thot 1:1.6a-3ubuntu1 [2876kB]
Del wesnoth-low 1:1.6a-3ubuntu1 [7699kB]
Del libboost-regex1.37.0 1.37.0-3ubuntu3 [441kB]
Del wesnoth-data 1:1.6a-3ubuntu1 [55.0MB]
Del wesnoth-ttb 1:1.6a-3ubuntu1 [2203kB]
Del wesnoth-music 1:1.6a-3ubuntu1 [107MB]
Del libsdl-net1.2 1.2.7-2 [11.5kB]
Del wesnoth-httt 1:1.6a-3ubuntu1 [6573kB]
Del wesnoth 1:1.6a-3ubuntu1 [1472B]
Del wesnoth-trow 1:1.6a-3ubuntu1 [5746kB]
Del wesnoth-l 1:1.6a-3ubuntu1 [3658kB]
Del wesnoth-ei 1:1.6a-3ubuntu1 [3364kB]
Del wesnoth-core 1:1.6a-3ubuntu1 [2825kB]
Del wesnoth-sotbe 1:1.6a-3ubuntu1 [4133kB]
Del wesnoth-sof 1:1.6a-3ubuntu1 [1356kB]
Del wesnoth-tsg 1:1.6a-3ubuntu1 [1925kB]
Del wesnoth-utbs 1:1.6a-3ubuntu1 [6956kB]
Del libboost-iostreams1.37.0 1.37.0-3ubuntu3 [136kB]
kola@Ks:~$

Fingers crossed, starting kpackage.......................................... ...working

Thank you so much for your help!

[dibl]

Re: I killed kpackage

Hhmm, suspicious glare at the cat....

Yes, you have successfully fixed the famous "feline sources.list infection" problem!



Good -- the wesnoth bits were residual in the apt cache and were deleted by the autoclean command. You're good to go.