package libfreerdp-server2-2:amd64 2.6.1+dfsg1-3ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Bug #2000670 reported by Jack Richey
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
freerdp2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Description: Ubuntu 22.04.1 LTS
Release: 22.04

libfreerdp2-2:
  Installed: 2.6.1+dfsg1-3ubuntu2.3
  Candidate: 2.6.1+dfsg1-3ubuntu2.3
  Version table:
 *** 2.6.1+dfsg1-3ubuntu2.3 500
        500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2.6.1+dfsg1-3ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

ran dpkg --configure -a manually
ran apt-get upgrade
ran apt --fix-broken install

threw a bug error report

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libfreerdp-server2-2:amd64 2.6.1+dfsg1-3ubuntu2.3
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
AptOrdering:
 libfreerdp2-2:amd64: Install
 libwinpr2-2:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Dec 28 22:00:24 2022
ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
InstallationDate: Installed on 2022-12-29 (0 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt 2.4.8
SourcePackage: freerdp2
Title: package libfreerdp-server2-2:amd64 2.6.1+dfsg1-3ubuntu2.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jack Richey (pinwiz1978) wrote :
information type: Private Security → Public
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.