On Sunday 07 of October 2012 16:24:23 Lisi Reisz wrote:
On 7 October 2012 12:34, Julius Schwartzenberg
julius.schwartzenberg@gmail.com wrote:
Pascal Viandier wrote:
adept_updater: symbol lookup error: adept_updater: undefined symbol: _ZN9KListView9selectAllEb
I've seen this as well. For instance on a Lucid system:
kicker: symbol lookup error: /opt/trinity/lib/libkdeinit_kicker.so: undefined symbol: _ZN9KListView9selectAllEb
It seems that 3.5.13.1 broke binary compatibility with 3.5.13 and this is causing partial upgrades to fail. This is not good :( 3.5.13.1 was supposed to stay fully binary compatible with 3.5.13 allowing packages to be mixed from both versions and upgrades to work smoothly.
In the current situation the package manager assumes that binary compatibility is there and is allowing partial upgrades to proceed. This causes many systems to break now.
I really have no clue what would be the best thing to do now, but I'm afraid 3.5.13.1 is causing havoc for lots of users right now.
I would suggest Slavek's recovery instructions are put on the website as a warning message for the main news and the 3.5.13.1 packages are removed from the 3.5.13 repository until all the upgrade problems are solved. Then people with partial upgrades hopefully will reach the warning and no other systems will break due to the 3.5.13.1 release problems.
Does this explain the problems am having with keyboards and mice? (I upgraded yesterday.)
Lisi
Since you used my PPA, problem with slow publishing official update does not affect you. Packages that are slow to publish, you have already installed a long time ago.
Slavek --