reopening the lid generates a RT ucode error -110 and then doesnt open

Bug #2022894 reported by Kshitij Sharma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Whenever i close and reopen my laptop lid it generates error RT ucode -110 and does not open. So I have to run powercfg /h off then chkdsk /f c: in my windows cmd after which it works fine but this error is a bit frustrating as i loses my work everytime.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libapparmor1:amd64 2.13.3-7ubuntu5.2
ProcVersionSignature: Ubuntu 5.15.0-73.80~20.04.1-generic 5.15.98
Uname: Linux 5.15.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.27
AptdaemonVersion: 1.1.1+bzr982-0ubuntu32.3
Architecture: amd64
CasperMD5CheckResult: skip
CrashReports:
 644:0:125:0:2023-06-05 12:40:07.170189085 +0530:2023-06-05 12:40:07.170189085 +0530:/var/crash/libip4tc2:amd64.0.upload
 600:0:125:356700:2023-06-04 01:13:29.523865222 +0530:2023-06-04 01:13:30.523865222 +0530:/var/crash/systemd-timesyncd.0.crash
 640:0:125:2692000:2023-06-05 12:40:01.823155879 +0530:2023-06-05 12:40:07.170189085 +0530:/var/crash/libip4tc2:amd64.0.crash
 600:0:125:356703:2023-06-04 01:13:29.511861085 +0530:2023-06-04 01:13:30.511861085 +0530:/var/crash/libapparmor1:amd64.0.crash
Date: Sun Jun 4 01:13:30 2023
ErrorMessage: package libapparmor1:amd64 is already installed and configured
InstallationDate: Installed on 2023-06-03 (1 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-5.15.0-73-generic root=UUID=df298721-3ee4-432f-a43c-a8ec91b2489f ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt 2.0.9
SourcePackage: dpkg
Title: package libapparmor1:amd64 2.13.3-7ubuntu5.2 failed to install/upgrade: package libapparmor1:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kshitij Sharma (horizon1202) wrote :
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.