Thanks to everyone who is contributing to this active thread, but please remember:
(1) UNINSTALL TrueSuite before upgrading to Mavericks, cutting corners can result in ugly surprises
(2) DON'T assume that because some TrueSuite functions work under OS X 10.9 that they are working correctly.
Using TrueSuite as-is under Mavericks could result in nasty surprises. As much as we all love the functionality and convenience, we are best holding back in hopes that Apple can deliver Mavericks-compliant solutions.
TrueSuite is NOT a simple program: it spawns an SQL database, and other two-factor hooks deep into the OS and Eikon hardware.
Patience is hard to muster -- but please feedback to Apple and lets stay in touch. It's gratifying to see how many people rely on Authentec solutions, and see Apple Communities in action...
Actually, the only component that is not compatible is the login, all other work perfectly fine.
Disabling the login will keep the upgrade process running smoothly. The login is the only component in the application that could create an issue in which you couldn't log in to your Mac. Aside from that component it is just another application that may have issues with th upgrade.
Thanks so much for this thread - it has been a life saver.
Installed Mavericks without thinking there would be a conflict so severe as to stop me being able to log in at all, yet here I am. I had previously disabled the Guest account as well - so I was effectively completely locked out.
In the end (prior to finding this thread) I had tried to reinstall Mavericks via the Recovery menu, and forced Mavericks to think that I was installing it for the first time by deleting /var/db/.AppleSetupDone - which re-enabled the Guest account.
By logging in as Guest and disabling the "Fingerprint Log On" setting in TrueSuite I was then able to log in as normal.
There must be quite a few AppleCare phone calls going on about this issue as it is hardly intuitive that the OS update would result in this behaviour, and even unplugging the fingerprint reader doesn't fix the problem.
I'm also a victim of the login boot issue... and this thread saves much hours of troubles. Thanks so much.
@wfauma: you wrote the steps how to solve it, but please explain step 3:
Where can I find the auth.db file? Since I'm not so familiar with Unix commands, can you please list all commands to fulfill step 3?
Many thanks in advance, Paddy.
I was referring to a previous post by RGab. So step 3 is:
3a) Mount he harddrive: type "/sbin/mount -uw /"
3b) Remove the file: type "rm /var/db/auth.db"
3c) Reboot: type "reboot"
I modified RGab's instructions in step 3b by typing "mv /var/db/auth.db /var/db/auth.db.old" instead, i.e. I saved the file for possible later use.
only because it was several time asked, what this auth.db thing is all about. The former /etc/authorization (xml file) in Mountain Lion is now transferred into a sqlite3 DB in /var/db/auth.db. The truesuite has added several items to the /etc/authorization which was then still alive in /var/db/auth.db and incorporated the truesuite software into several parts of the OS (set it into action).
So the "trick" of removing this file works, because this file is rebuilt if missing from /System/Library/Security/authorization.plist where the TrueSuite settings are not part of the file.
Thank you everyone for your help on this problem! Unfortunately I had not seen this until it was too late. It has been stated before, but for the sake of others, DO NOT run the uninstall AFTER Mavericks is installed. I ended up getting the Apple white screen of death. Thankfully I was able to do a full recovery from Timecapsule.
The nicest feature I liked of Truesuite was the login feature. Does anyone know of software that is Mavericks compatible or is it over for using the fingerprint scanner if updating to Mavericks? Of the two, I will keep the fingerprint scanner and avoid updating as long as possible.
Thanks again to all of you, even though I got out of the mess in a different method tha posted, it pointed me in the right direction!
I upgraded to Mavericks today, without even thinking (as others of you have said) that there would be a problem with Truesuite. However, if I'm reading correctly, many or most of you are not able to log in. I don't have that problem, but I no longer have the fingerprint scan security. The Truesuite software just says that it can't find my scanner.
So I guess, if I'm undertanding, I should just unplug my scanner and not worry about it until Apple solves this? As long as I'm able to boot up and log in, there's no need to uninstall Truesuite, right?
Thank you for everyone's afford. Finally I know how to fix the login loop problem.
After I disabled the "Fingerprint Log On" option, I can login successfully now.
Do I just leave the Truesuite there?
As I found that some people trying to uninstall it under 10.9 will cause another grey screen loop while booting.
PROPS TO YREISER
Big thanks! That worked. When I first created the "new acct" at the end, for some reason my amchine shut down. I rebooted and then was asked to create a new acct again, did that, and got on. I threw the switches OFF on everything in the options and rebooted and now all users show up--including the two new users I just created.
Log on proceeded normally and now I am tweaking and loading up Mavericks for the first time.
Many thanks again
It was like the old MS DOS days (sort of)
Wait a minute:
1-Apple bought the company- assuming the responsibility for customer support and quickly demoted it to self service.
2-Apple had better than a year to either update the driver to gain interoperability with Mavericks or mod Mavericks to keep the 10.8x driver working.
3-Lacking the intent to fix the problem, Apple's installer should have recognized the problem in bug reports and disabled the software.
4-Apple is a large company built upon a reputation rapidly being sullied by stuff like this. They have the resources to fix this any time they wish without a great deal of effort.
5-As Apple owns the IP for both the OS and the driver for the Eikon scanners, only Apple can fix this problem.
6-This appears another example of Apple ignoring OS X to serve the interests of iOS.
7-This is a really glaring example of bad customer service.