Errors during debian upgrades are highly uncommon... Today that I upgraded my testing box, I noticed the following:
Preparing to replace openoffice.org-writer2latex 0.5.0.2-2 (using .../openoffice.org-writer2latex_0.5.0.2-4_all.deb) ... /usr/lib/openoffice/program/unopkg.bin: error while loading shared libraries: libunopkgapp.so: cannot open shared object file: No such file or directory Removing extension org.openoffice.da.writer2latex.oxt.../usr/lib/openoffice/program/unopkg.bin: error while loading shared libraries: libunopkgapp.so: cannot open shared object file: No such file or directory
done. Unpacking replacement openoffice.org-writer2latex ... and... Removing extension org.openoffice.legacy.mailmerge.py...ERROR: python-loader:<type 'exceptions.ImportError'>: No module named pythonloader, traceback follows
no traceback available unopkg failed. done. Unpacking replacement openoffice.org-emailmerge ... Should I worry? And two issues with the upgrade of the kernel (from 2.6.26-1 to 2.6.26-2):I have a Nvidia graphics adapter and after the upgrade X broke. I saw that nvidia-glx was installed along with nvidia-kernel-2.6.26-1-686. Shouldn't this be automatically updated? Anyway, I installed manually nvidia-kernel-2.6.26-2-686 and all worked again.
Second issue was with virtualbox, which also had some modules for 2.6.26-1. I installed the right ones manually and all worked again.
Giorgos
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature