package memtest86+ 5.01-3.1ubuntu2.1 failed to install/upgrade: installed memtest86+ package post-installation script subprocess returned error exit status 1

Bug #1897425 reported by Pratik jaiswal
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
memtest86+ (Ubuntu)
Invalid
Low
Unassigned

Bug Description

i am not able to connect headphones

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: memtest86+ 5.01-3.1ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
Uname: Linux 4.4.0-135-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_4_4_0_135_161_generic_61
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Sep 26 19:32:48 2020
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: installed memtest86+ package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2017-01-14 (1351 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.2ubuntu0.1
SourcePackage: memtest86+
Title: package memtest86+ 5.01-3.1ubuntu2.1 failed to install/upgrade: installed memtest86+ package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-09-26 (0 days ago)

Revision history for this message
Pratik jaiswal (pr-n-lk) wrote :
Revision history for this message
Seth Arnold (seth-arnold) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment to this bug report it seems that there may be a problem with your hardware. I'd recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck!

information type: Private Security → Public
Changed in memtest86+ (Ubuntu):
status: New → Invalid
importance: Undecided → Low
tags: added: hardware-error
Revision history for this message
Seth Arnold (seth-arnold) wrote :

In addition to the dmesg entries that look like hardware errors, it appears this machine's kernel is over two years old -- is that intentional?

Thanks

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.