package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet

[Sebastian Kraus]

error occured during regular "do-release-upgrade". System remains in unstable condition. dpkg --configure -a / apt-get -f install continues the process (still running).

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Fri Apr 22 17:05:44 2016
DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
InstallationDate: Installed on 2016-03-17 (35 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt 1.2.10ubuntu1
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

[Sebastian Kraus (ticktoo)]

system upgrade finished after several iterations of apt-get dist-upgrade && apt-get autoremove. System is now booting and in proper condition.

[Launchpad Janitor (janitor)]

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

[Kenneth Bingham (qrkourier)]

After using the GUI to initiate dist-upgrade from 15.10 to 16.04 and encountering the error described above related to the gconf2 package the automatic reboot resulted in an undefined state that resembled a reboot loop. I eventually tired of waiting, switched to TTY1 and pressed ctrl-alt-delete. This seems to have succeeded switching to runlevel 6 and it became clear the machine had not yet completely shutdown following the upgrade. The reboot succeeded but the window manager failed to run. I switched to a TTY with a login prompt and was dropped into a shell. I ran the command prescribed by Sebastian and was prompted to instead run dpkg to complete a package operation that had been interrupted. I did so and was prompted several times to accept the maintainer's version of files that had changed on my computer and did so without exception. After dpkg completed successfully I again ran apt-get dist-upgrade and autoremove successfully and rebooted. This time the window manager presented normally and everything seems fine so far.