package gnome-shell-common 3.30.2-0ubuntu1.18.10.1 failed to install/upgrade: installed gnome-shell-common package post-installation script subprocess returned error exit status 2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-shell (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When trying to update , reinstall , purge or whatever command it does this :
E: gnome-shell-common: installed gnome-shell-common package post-installation script subprocess returned error exit status 2
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: gnome-shell-common 3.30.2-
ProcVersionSign
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
AptOrdering:
gnome-shell:amd64: Install
ubuntu-
gdm3:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Sun Apr 14 23:07:24 2019
DisplayManager: gdm3
DuplicateSignature:
package:
Setting up gnome-shell-common (3.30.2-
update-
dpkg: error processing package gnome-shell-common (--configure):
installed gnome-shell-common package post-installation script subprocess returned error exit status 2
ErrorMessage: installed gnome-shell-common package post-installation script subprocess returned error exit status 2
GsettingsChanges:
InstallationDate: Installed on 2019-04-13 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitec
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageV
dpkg 1.19.0.5ubuntu5
apt 1.7.4
SourcePackage: gnome-shell
Title: package gnome-shell-common 3.30.2-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1804742, so it 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. Feel free to continue to report any other bugs you may find.