package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured

Bug #1703260 reported by Muhammad Nauman
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I am just getting this error again and again

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjson-c2:i386 0.11-4ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Sat Jul 8 17:22:43 2017
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 multiarch-support 2.23-0ubuntu9
DuplicateSignature:
 package:libjson-c2:i386:0.11-4ubuntu2
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package libsystemd0:i386 (--configure):
  package libsystemd0:i386 is already installed and configured
ErrorMessage: package libjson-c2:i386 is already installed and configured
InstallationDate: Installed on 2017-07-03 (6 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.20
SourcePackage: dpkg
Title: package libjson-c2:i386 0.11-4ubuntu2 failed to install/upgrade: package libjson-c2:i386 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Muhammad Nauman (nauman786) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote : Bug is not a security issue

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

information type: Private Security → Public
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Incidentally you may also have hardware errors:

Jul 10 01:55:04 hostname kernel: ata1: SError: { UnrecovData Handshk }
Jul 10 01:55:04 hostname kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jul 10 01:55:04 hostname kernel: ata1.00: cmd 61/08:c0:00:a8:99/00:00:10:00:00/40 tag 24 ncq dma 4096 out
                                             res 40/00:d0:00:a9:19/00:00:15:00:00/40 Emask 0x10 (ATA bus error)
Jul 10 01:55:04 hostname kernel: ata1.00: status: { DRDY }
Jul 10 01:55:04 hostname kernel: ata1.00: failed command: READ FPDMA QUEUED
Jul 10 01:55:04 hostname kernel: ata1.00: cmd 60/00:c8:d0:cf:9e/01:00:16:00:00/40 tag 25 ncq dma 131072 in
                                             res 40/00:d0:00:a9:19/00:00:15:00:00/40 Emask 0x10 (ATA bus error)
Jul 10 01:55:04 hostname kernel: ata1.00: status: { DRDY }
Jul 10 01:55:04 hostname kernel: ata1.00: failed command: READ FPDMA QUEUED
Jul 10 01:55:04 hostname kernel: ata1.00: cmd 60/40:d0:00:a9:19/00:00:15:00:00/40 tag 26 ncq dma 32768 in
                                             res 40/00:d0:00:a9:19/00:00:15:00:00/40 Emask 0x10 (ATA bus error)
Jul 10 01:55:04 hostname kernel: ata1.00: status: { DRDY }
Jul 10 01:55:05 hostname kernel: ata1.00: exception Emask 0x10 SAct 0x40000003 SErr 0x400100 action 0x6 frozen
Jul 10 01:55:05 hostname kernel: ata1.00: irq_stat 0x08000000, interface fatal error
Jul 10 01:55:05 hostname kernel: ata1: SError: { UnrecovData Handshk }
Jul 10 01:55:05 hostname kernel: ata1.00: failed command: READ FPDMA QUEUED
Jul 10 01:55:05 hostname kernel: ata1.00: cmd 60/00:00:d0:cf:9e/01:00:16:00:00/40 tag 0 ncq dma 131072 in
                                             res 40/00:08:00:a8:99/00:00:10:00:00/40 Emask 0x10 (ATA bus error)
Jul 10 01:55:05 hostname kernel: ata1.00: status: { DRDY }
Jul 10 01:55:05 hostname kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Jul 10 01:55:05 hostname kernel: ata1.00: cmd 61/08:08:00:a8:99/00:00:10:00:00/40 tag 1 ncq dma 4096 out
                                             res 40/00:08:00:a8:99/00:00:10:00:00/40 Emask 0x10 (ATA bus error)
Jul 10 01:55:05 hostname kernel: ata1.00: status: { DRDY }
Jul 10 01:55:05 hostname kernel: ata1.00: failed command: READ FPDMA QUEUED
Jul 10 01:55:05 hostname kernel: ata1.00: cmd 60/40:f0:00:a9:19/00:00:15:00:00/40 tag 30 ncq dma 32768 in
                                             res 40/00:08:00:a8:99/00:00:10:00:00/40 Emask 0x10 (ATA bus error)
Jul 10 01:55:05 hostname kernel: ata1.00: status: { DRDY }
Jul 10 01:55:05 hostname kernel: ata1: limiting SATA link speed to 3.0 Gbps
Jul 10 01:55:05 hostname kernel: ata1.00: exception Emask 0x10 SAct 0x70 SErr 0x400100 action 0x6 frozen
Jul 10 01:55:05 hostname kernel: ata1.00: irq_stat 0x08000000, interface fatal error

Good luck

tags: removed: need-duplicate-check
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dpkg (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.