KDE fails to load since updates 2010-09-15

I created a VirtualBox guest host using the 9/8/10 Maverick LiveCD. It ran well. Yesterday I received notification of updates available. Rather than run KPackageKit I opened a Konsole and used apt-get. About 274 packages were updated. I rebooted and my KDE desktop appeared and ran normally. A few minutes later KPackageKit said 254 packages were available. I let it do the updates and rebooted when it told me to. I was greeted with the login screen loop. None of the usual remedies would fix it.

So, also yesterday, 9/15/10, I downloaded the Maverick daily livecd with the intention of installing it over the existing Maverick guest OS on VirtualBox. Booting the LiveCD up within VirtualBox using the existing Maverick guest OS I was greeted with the Maverick LiveCD menu.

I selected the install option straight away. An "ubi-partmon failed with an exit code 141". A retry failed. Ignoring the failure resulted in a sterile install, with the progress bar missing, and it never progress beyond the final ad graphic. I canceled and the system proceeded to go to the LiveCD KDE desktop. While still running the LiveCD KDE desktop I installed gparted and created a bootable EXT4 partition, erasing the Maverick install that had resided there. Then I ran the install option from the desktop icon. Upon completion of the install I rebooted and was greeted again with the login screen loop. Today, 9/16/10, I booted into a console screen, thinking there would be some additional downloads which would resolve the situation. I did the apt-get update & dist-upgrade. After between 20-30 downloads installed I rebooted. The login screen loop remains. The contents of the .xsession-errors file is copied below (only because this bug system allows only on attachment per post)
***************************************************
Xsession: X session started for greygeek at Thu Sep 16 10:04:11 CDT 2010
Setting IM through im-switch for locale=en_US.
Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default.
[: 225: ==: unexpected operator
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
kbuildsycoca4 running...
QDBusObjectPath: invalid path ""
Fetched layout groups from X server: layouts: ("us") variants: ("")
Fetched layout groups from X server: layouts: ("us") variants: ("")
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QMetaObject::invokeMethod: No such method KUniqueApplication::loadCommandLineOptionsForNewInstance()

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Invalid D-BUS member name 'idle-hint' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name 'is-local' found in interface 'org.freedesktop.ConsoleKit.Session' while parsing introspection
Invalid D-BUS member name '...

My i386 test machine is fine, but my amd64 machine has this problem.

Just installed an tested today's (9/17/10) 32 bit Maverick daily LiveCD as a guest OS in my VirtualBox.
It, too, has the login screen loop, in addtion to missing a GPG key for one of the repositories, thus blocking any files it may offer.

I have even done a couple of fresh reinstalls of 10.10 Beta (64 bit) and once the updates are installed, I am immediately faced with the repeating longon screen.

I was having this same login loop problem starting on 9-15-10 in Kubuntu Maverick Beta too, but since after installing the Ubuntu daily-live cd dated 21-sep-2010 (plus the installing the kubuntu-desktop meta-package), the login loop problem appears to be fixed. I have also tested and installed the Kubuntu daily-live cd dated 22-sep-2010 and the problem appears to be fixed there too. I use 32 bit systems.

Fixed for me on amd64.

Problem is fixed.