View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002572Kali LinuxGeneral Bugpublic2015-08-19 15:312015-09-15 08:14
Reportermatterpreter Assigned Torhertzog  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionnot fixable 
Product Version1.1.0 
Summary0002572: dpkg error while upgrading to 2.0
Description

Hello,

Tried upgrading a laptop yesterday from 1.1.0 to 2.0 and dpkg ran into some issues. When I rebooted, I got a kernal panic and now the root FS is corrupted.

Tried with a dry run of the dist-upgrade on another machine this morning and ran into this error:

<snip>
Conf webshells (1.1-0kali0 kali-current [all])
Conf weevely (3.2.0-0kali2 kali-current [all])
Conf whatweb (0.4.8~git20141014-1 kali-current [all])
Conf wifite (2.0.2-1kali1 kali-current [all])
Conf wkhtmltopdf (0.12.1-2 kali-current [amd64])
Conf xbrlapi (5.2~20141018-5 kali-current [amd64])
E: Conf Broken dpkg:amd64

Steps To Reproduce

cat << EOF > /etc/apt/sources.list
deb http://http.kali.org/kali sana main non-free contrib
deb http://security.kali.org/kali-security/ sana/updates main contrib non-free
EOF

apt-get update
apt-get --dry-run dist-upgrade

Additional Information

The boxes are very close to the stock config.

Activities

matterpreter

matterpreter

2015-08-27 12:05

reporter   ~0003839

Anyone had a chance to look into this more? Issue still persisting.
rhertzog

rhertzog

2015-08-31 09:50

administrator   ~0003850

I'm afraid that this report is not helpful. I tried recently a dist-upgrade from an up-to-date moto system and I had some failures with file conflicts. I fixed some of those recently and I'm in the process of fixing one more right now.

But if you bring hardware problem with filesystem corruption on top of it, it becomes untractable. The upgrade is unlikely to be responsible of the filesystem corruption, maybe it triggered an imminent hardware failure.

If you want to help us diagnose anything, you should at least provide a full log... possibly with some debugging data (see man apt.conf) like with "-o Debug::pkgProblemResolver=true".

In any case, apt-get certainly provides a solution and tries to upgrades the system. I never saw any failure in the middle of dry run...
rhertzog

rhertzog

2015-09-15 08:14

administrator   ~0004001

Can't do anything without user feedback.

Issue History

Date Modified Username Field Change
2015-08-19 15:31 matterpreter New Issue
2015-08-27 12:05 matterpreter Note Added: 0003839
2015-08-31 09:50 rhertzog Note Added: 0003850
2015-08-31 09:50 rhertzog Assigned To => rhertzog
2015-08-31 09:50 rhertzog Status new => assigned
2015-08-31 12:46 rhertzog Status assigned => feedback
2015-09-15 08:14 rhertzog Note Added: 0004001
2015-09-15 08:14 rhertzog Status feedback => closed
2015-09-15 08:14 rhertzog Resolution open => not fixable