Updates give errs re 'gtype' & 'assert-multi-arch'

[lewyssmith]

After a huge update (1350 files) messed my favourite LMDE/LXDE installation, I re-installed it and am trying the 1000+ updates via Update Manager in small bites. But every one terminates "Update not complete" with the following example errors, of which:

Code: Select all

Trying to register gtype '...Flags' as enum when in fact it is of type 'GFlags'

&

Code: Select all

W: Waited for dpkg --assert-multi-arch but it wasn't there - dpkgGo (10: No child processes)
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:


are universal.

Code: Select all

** (process:2125): WARNING **: [b]Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'[/b]

** (process:2125): WARNING **: [b]Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'[/b]

** (process:2125): WARNING **: [b]Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'[/b]
(Reading database ... 150466 files and directories currently installed.)
Preparing to replace libcairo2 1.10.2-2ubuntu2 (using .../libcairo2_1.12.2-2_i386.deb) ...
Unpacking replacement libcairo2 ...
Selecting previously unselected package libmono-system-runtime-serialization4.0-cil.
Unpacking libmono-system-runtime-serialization4.0-cil (from .../libmono-system-runtime-serialization4.0-cil_2.10.8.1-4_all.deb) ...
Selecting previously unselected package libmono-system-xml-linq4.0-cil.
Unpacking libmono-system-xml-linq4.0-cil (from .../libmono-system-xml-linq4.0-cil_2.10.8.1-4_all.deb) ...
Selecting previously unselected package libnewtonsoft-json4.5-cil.
Unpacking libnewtonsoft-json4.5-cil (from .../libnewtonsoft-json4.5-cil_4.5r6-1_all.deb) ...
Selecting previously unselected package libgdata2.1-cil.
Unpacking libgdata2.1-cil (from .../libgdata2.1-cil_2.1.0.0-1_all.deb) ...
Preparing to replace banshee 2.2.0-2linuxmint1 (using .../banshee_2.4.1-3+1linuxmint1_i386.deb) ...
Unpacking replacement banshee ...
Processing triggers for man-db ...
Processing triggers for menu ...
Processing triggers for shared-mime-info ...
Processing triggers for desktop-file-utils ...
Processing triggers for gnome-menus ...
Processing triggers for hicolor-icon-theme ...
dpkg: error processing libcairo2:i386 (--configure):
 no package named `libcairo2:i386' is installed, cannot configure
dpkg: error processing libmono-system-runtime-serialization4.0-cil:all (--configure):
 no package named `libmono-system-runtime-serialization4.0-cil:all' is installed, cannot configure
dpkg: error processing libmono-system-xml-linq4.0-cil:all (--configure):
 no package named `libmono-system-xml-linq4.0-cil:all' is installed, cannot configure
dpkg: error processing libnewtonsoft-json4.5-cil:all (--configure):
 no package named `libnewtonsoft-json4.5-cil:all' is installed, cannot configure
dpkg: error processing libgdata2.1-cil:all (--configure):
 no package named `libgdata2.1-cil:all' is installed, cannot configure
dpkg: error processing banshee:i386 (--configure):
 no package named `banshee:i386' is installed, cannot configure
Errors were encountered while processing:
 libcairo2:i386
 libmono-system-runtime-serialization4.0-cil:all
 libmono-system-xml-linq4.0-cil:all
 libnewtonsoft-json4.5-cil:all
 libgdata2.1-cil:all
 banshee:i386
[b]W: Waited for dpkg --assert-multi-arch but it wasn't there - dpkgGo (10: No child processes)
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:[/b]
Setting up libcairo2 (1.12.2-2) ...
Setting up libmono-system-xml-linq4.0-cil (2.10.8.1-4) ...
Setting up libmono-system-runtime-serialization4.0-cil (2.10.8.1-4) ...
Setting up libnewtonsoft-json4.5-cil (4.5r6-1) ...
* Installing 1 assembly from libnewtonsoft-json4.5-cil into Mono
Setting up libgdata2.1-cil (2.1.0.0-1) ...
* Installing 11 assemblies from libgdata2.1-cil into Mono
Setting up banshee (2.4.1-3+1linuxmint1) ...
Processing triggers for menu ...

I can find nothing in the forum about this. Please advise what I might do.

AND... I have seen & read about in the forum UP5 etc, but no idea as to how to determine the UPn level of one's installation, nor a routine lead to their description (which I *did* find in an obscure thread).

TIA Lewis Smith

[TomRoche]

[I have] no idea as to how to determine the UPn level of one's installation

Hopefully this will help. (In separate thread to avoid thread pollution.)

[TomRoche]

After a huge update (1350 files) messed my favourite LMDE/LXDE installation, I re-installed it and am trying the 1000+ updates via Update Manager in small bites.

Yep, UP5 was waaay too big. Fortunately the Head Mintsters seem to have learned from this, and UP6 appears to be coming soon.

Unfortunately I don't know enough to solve your problem directly, but perhaps can provide some pointers (since no one else is):

Code: Select all

Trying to register gtype '...Flags' as enum when in fact it is of type 'GFlags'

GFlags, and pretty much G-anything in this context, is GNOME/GTK. So that particular problem may be best dealt with by consulting with GNOME folks (since, IIUC, they now support/maintain GTK). But ...

Given the many dpkg-related errors you cite, I suspect something is very wrong with your APT configuration. Consider consulting with APT experts at, e.g., debian-user or one of the debian forums.

[zerozero]

hi,

Code: Select all

Trying to register gtype '...Flags' as enum when in fact it is of type 'GFlags'

i don't remember seeing this but these bug reports https://bugs.archlinux.org/task/30809 https://bugs.launchpad.net/ubuntu/+sour ... bug/918607 look similar

as for the other issue: the second failed update, i'm not really surprised tbh

I re-installed it and am trying the 1000+ updates via Update Manager in small bites.

this is a recipe for disaster as you can see in the output you show us: some packages fail to install (or fail to configure) because some depends are not there (as in you did not select them to install)

i understand that a heavily tweaked system (with lots of removals and additions) might have at some point some kind of OOPS!! in a dist-upgrade (even more more when you add to that proprietary drivers & alien packages) but it's odd that this would happen in a vanilla system (even in a huge update from UP4>UP5)