package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm3 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Error during installation of python3 idle in ubuntu 18.04 LTS
Errors were encountered while processing: gdm3
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.2-0ubuntu1.2
ProcVersionSign
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Wed Sep 26 07:56:39 2018
DpkgHistoryLog:
Start-Date: 2018-09-26 07:56:34
Commandline: apt-get install idle-python3.6
Requested-By: nikhil (1000)
Install: libtcl8.6:amd64 (8.6.8+dfsg-3, automatic), blt:amd64 (2.5.3+dfsg-4, automatic), idle-python3.
DuplicateSignature:
package:
Setting up gdm3 (3.28.2-0ubuntu1.2) ...
dpkg: error processing package gdm3 (--configure):
installed gdm3 package post-installation script subprocess returned error exit status 10
ErrorMessage: installed gdm3 package post-installation script subprocess returned error exit status 10
InstallationDate: Installed on 2018-05-27 (121 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.1
SourcePackage: gdm3
Title: package gdm3 3.28.2-0ubuntu1.2 failed to install/upgrade: installed gdm3 package post-installation script subprocess returned error exit status 10
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 1774039, 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.