polkitd 124-1 failed to upgrade Failed to check if group polkitd already exists: Connection refused
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
policykit-1 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Error popped up when upgrading from Ubuntu 22 to 24. It's pretty much standard ubuntu server with little to no software on it.
Setting up polkitd (124-1) ...
Failed to check if group polkitd already exists: Connection refused
id: ‘polkitd’: no such user
chown: invalid group: ‘root:polkitd’
dpkg: error processing package polkitd (--configure):
installed polkitd package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of pkexec:
pkexec depends on polkitd (= 124-1); however:
Package polkitd is not configured yet.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: polkitd 124-1
ProcVersionSign
Uname: Linux 5.15.0-100-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckR
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Thu Mar 14 00:36:20 2024
ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2022-10-05 (525 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220421)
Python3Details: /usr/bin/
PythonDetails: /usr/bin/
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageV
dpkg 1.22.4ubuntu5
apt 2.7.12
SourcePackage: policykit-1
Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to noble on 2024-03-14 (0 days ago)
mtime.conffile.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2054716, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.