View Issue Details

IDProjectCategoryView StatusLast Update
0004286Kali LinuxGeneral Bugpublic2017-10-03 15:33
Reporterpavan Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version2017.2 
Summary0004286: Unable to Locate package
Description

After Upgrading my Current Version to 2017.2 .unable to install any software with
sudo apt-get install<package name>

what i a have done

i used the

sudo apt-get update
sudo apt-get dist-upgrade
reboot

and after Upgrading

i am getting error as

E:Unable to Locate package

tried to upgrade again but it is doing the same

i changed the repo details also doing the same
but it is continuing the same thing

Steps To Reproduce

just upgrade your distribution with dist-upgrade and then you will be into problem of unable to locate package

Additional Information

My System Conf

Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 55
Model name: Intel(R) Pentium(R) CPU N3510 @ 1.99GHz
Stepping: 3
CPU MHz: 1598.359
CPU max MHz: 1999.2000
CPU min MHz: 499.8000
BogoMIPS: 3998.40
Virtualization: VT-x
L1d cache: 24K
L1i cache: 32K
L2 cache: 1024K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm arat

Attached Files

Activities

pavan

pavan

2017-10-03 14:20

reporter   ~0007456

After Upgrading to 2017.2 the Applications icon are changed to system default icons Screen shot attached

crash

crash

2017-10-03 14:35

reporter   ~0007457

So, first of all:
1 - If you put external repo in sources.list I suggest you to make a fresh install. Please refer to Kali Repo documentation in case you have any doubt about that.

2 - run this command to update your Kali properly:
apt update ; apt full-upgrade -y ; apt autoremove -y

3- You can check id you kali is ok running this script: https://github.com/crashbrz/kalihealthcheck/

If there is something wrong, the script will show you. Fix it and run the command in #2 again.

Again, if you put any external repo, the best solution is to make a fresh install.

Ps: I think you attached a wrong screenshot.

crash

crash

2017-10-03 14:37

reporter   ~0007458

Another point, for this kind of problem you should use http://forums.kali.org (:

pavan

pavan

2017-10-03 14:54

reporter   ~0007459

if i do these below things

apt update ; apt full-upgrade -y ; apt autoremove -y

it is telling me to fix broken
by apt --fix-broken install

i tried to fix in two ways by using packager and by updating in terminal

crash

crash

2017-10-03 15:10

reporter   ~0007460

So, I'm not sure if you fixed it or not. If not I need more details. Post all information in pastebin please.

pavan

pavan

2017-10-03 15:25

reporter   ~0007461

@crash issue not resolved ..please specify wat u need

crash

crash

2017-10-03 15:31

reporter   ~0007462

So now seems you have a basic problem with packets.
Do the process again and put all the output in pastebin.

Also, you can remove the broken packets using dpkg. Check the dpkg documentation.

So, check it and as I told you, move this topic to https://forums.kali.org if you want because its not a kali issue.

I'm in kali irc channel you can call there. I will ask to close this post.

rhertzog

rhertzog

2017-10-03 15:33

administrator   ~0007463

Please have this conversation somewhere else. This is a bug tracker, not a support forum. Thank you.

Paste standard response:

Thank you for your interest in Kali but this bug report is not actionable. Please read https://kali.training/chapter-6/filing-a-good-bug-report/ first. We are a small team and we expect you to provide a much more detailed bug report.

Once you have done the necessary research (possibly with the help of the community on http://forums.kali.org or on IRC #kali-linux on irc.freenode.net), feel free to re-open this bug with more information or to open a new report.

Issue History

Date Modified Username Field Change
2017-10-03 14:11 pavan New Issue
2017-10-03 14:18 pavan File Added: Screenshot from 2017-10-03 19-47-17.png
2017-10-03 14:20 pavan Note Added: 0007456
2017-10-03 14:35 crash Note Added: 0007457
2017-10-03 14:37 crash Note Added: 0007458
2017-10-03 14:54 pavan Note Added: 0007459
2017-10-03 15:10 crash Note Added: 0007460
2017-10-03 15:25 pavan Note Added: 0007461
2017-10-03 15:31 crash Note Added: 0007462
2017-10-03 15:33 rhertzog Assigned To => rhertzog
2017-10-03 15:33 rhertzog Status new => closed
2017-10-03 15:33 rhertzog Resolution open => no change required
2017-10-03 15:33 rhertzog Note Added: 0007463