This happens on all my new 10.1 installations.. I get this in the mail every morning... When running either "yast2 online_update" or "rug up" from console, the updates are downloaded and installed perfectly fine. What's up with the auto-update function? Resolving Dependencies... The following packages will be installed: freetype2 2.1.10-18.3 (http://ftp.gwdg.de/pub/suse/update/10.1) freetype2-2.1.10-18.3.x86_64[20060625-165018] needed by atom:freetype2-2.1.10-18.3.x86_64[20060625-165018] freetype2 1608-0 (http://ftp.gwdg.de/pub/suse/update/10.1) freetype2-32bit 2.1.10-18.3 (http://ftp.gwdg.de/pub/suse/update/10.1) freetype2-32bit-2.1.10-18.3.x86_64[20060625-165018] needed by atom:freetype2-32bit-2.1.10-18.3.x86_64[20060625-165018] freetype2-devel 2.1.10-18.3 (http://ftp.gwdg.de/pub/suse/update/10.1) freetype2-devel-2.1.10-18.3.x86_64[20060625-165018] needed by atom:freetype2-devel-2.1.10-18.3.x86_64[20060625-165018] gpg 1664-0 (http://ftp.gwdg.de/pub/suse/update/10.1) gpg 1.4.2-23.4 (http://ftp.gwdg.de/pub/suse/update/10.1) gpg-1.4.2-23.4.x86_64[20060625-165018] needed by atom:gpg-1.4.2-23.4.x86_64[20060625-165018] Proceed with transaction? (y/N) ERROR: Object reference not set to an instance of an object -- Anders Norrbring Norrbring Consulting -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com