package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Matthias]

There seem to be fairly similar bugs already reported, but in my case, I was upgrading from 18.04 to 18.10 and it seems that my version is just slightly newer. Assuming it's related to the other similar bugs, then this is still an issue.

$ lsb_release -rd
Description: Ubuntu 18.10
Release: 18.10

apt-cache policy gconf2 130 ↵
gconf2:
  Installed: 3.2.6-4.1ubuntu2
  Candidate: 3.2.6-4.1ubuntu2
  Version table:
 *** 3.2.6-4.1ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
        100 /var/lib/dpkg/status

Now that's it's up everything seems to be fine, but I had to hit "close" on the error dialog many many times.

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: gconf2 3.2.6-4.1ubuntu2
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
Date: Sun Nov 25 13:31:28 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-10-02 (1149 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
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
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt 1.7.0
SourcePackage: gconf
Title: package gconf2 3.2.6-4.1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to cosmic on 2018-11-25 (0 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.