I have exactly the same behaviour as coffeemonk, and as superlinkx says, it was triggered by an update today. I dug a little further through the conflicts and it seems to be related to a problem with libsoup2.4-1:i386 - see the message below:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
libsoup2.4-1 : Breaks: libsoup2.4-1:i386 (!= 2.38.0-1) but 2.38.0-0ubuntu1 is to be installed
libsoup2.4-1:i386 : Breaks: libsoup2.4-1 (!= 2.38.0-0ubuntu1) but 2.38.0-1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
I have exactly the same behaviour as coffeemonk, and as superlinkx says, it was triggered by an update today. I dug a little further through the conflicts and it seems to be related to a problem with libsoup2.4-1:i386 - see the message below:
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies. ver::Resolve generated breaks, this may be caused by held packages.
libsoup2.4-1 : Breaks: libsoup2.4-1:i386 (!= 2.38.0-1) but 2.38.0-0ubuntu1 is to be installed
libsoup2.4-1:i386 : Breaks: libsoup2.4-1 (!= 2.38.0-0ubuntu1) but 2.38.0-1 is to be installed
E: Error, pkgProblemResol