Linux Client not letting me log in

Is there something wrong with the Linux client right now? I just tried to log in and its telling me to check my password..yet its right.. as made obvious by the fact that I could log into the forum.
Anyone know what might be up?

2006-05-23T02:29:21Z INFO:   SkinDir:
2006-05-23T02:29:21Z INFO: LLControlGroup::loadFromFile unable to open.
2006-05-23T02:29:21Z INFO: Resolving Agni userserver domain name userserver.agni.lindenlab.com
2006-05-23T02:29:21Z INFO: ...Userserver resolved to 66.150.244.151:12036
2006-05-23T02:29:21Z INFO: LLCircuit::addCircuitData for 66.150.244.151:12036
2006-05-23T02:29:21Z INFO: Verifying message template...
2006-05-23T02:29:21Z INFO: Message template is current!
2006-05-23T02:29:21Z INFO: LLMessageSystem::disableCircuit for 66.150.244.151:12036
2006-05-23T02:29:21Z INFO: LLCircuit::removeCircuitData for 66.150.244.151:12036
2006-05-23T02:29:21Z WARNING: Packet  from invalid circuit 66.150.244.151:12036
2006-05-23T02:29:21Z INFO: Authenticating: Jinsar Eponym,
2006-05-23T02:29:21Z INFO: Options: inventory-root, inventory-skeleton, inventory-lib-root, inventory-lib-owner, inventory-skel-lib, gestures, event_categories, event_notifications, classified_categories, buddy-list, ui-config, login-flags, global-textures, END
2006-05-23T02:29:21Z INFO: LLUserAuth::authenticate: uri=https://login.agni.lindenlab.com/cgi-bin/login.cgi
2006-05-23T02:29:24Z INFO: Buffer size:   442 B
2006-05-23T02:29:24Z INFO: Transfer size: 229 B
2006-05-23T02:29:24Z INFO: Transfer time: 3.15207 s
2006-05-23T02:29:24Z INFO: Transfer rate: 0.576 Kb/s
2006-05-23T02:29:24Z INFO: Processed response: 0

Do you type your password by hand every time you log in or do you have it stored by the client? If you type by hand, make double sure you don't have CAPS-LOCK switched on, or NUM-LOCK off if you're using digits on the number pad. To verify, you can type the password into a blank text editor (while nobody is looking). If you still experience the same problem, you might want to contact Linden support and see, if there's anything wrong with your account.

Yes I double checked the numlock and caps lock. And there is nothing wrong with my account I can log in under windows no problem.

Try typing the password into your username field just to be sure, the keyboard mapping *inside* of the SL client works correctly. Otherwise, I'm out of ideas for now, sorry. Maybe support can have a look at it?

updatE: problem is the number pad. The linux client does not seem to read properly from it, even though other programs do. This was solved by using the regular numbers for the number part of my password.

Ah! Great news! I hope we will have a stable Linux client again, soon, so that your investigation was not in vain

hopefully someone iwll pick that up and fix it. Does anyone else notice that group names appear twice above people's head?

Yes.

This bug is one of the most irritating ones, since it requires about 10 seconds to fix it. The Linux Client has issues with line breaks. The line buffer does not get cleared on line breaks, so it always adds the contents of the previous line to the next and so on...

Yes, just spotted that this morning.

Even funnier - if you go into "edit appearance" you get the whole lot twice: so it says:

tag tag name
tag tag name (Editing Appearance)

Bug in the client, been that way for quite a while. Dunno if or when they plan on fixing it, though it is only cosmetic.

The tags can be annoying at times, but really I'd prefer if they put tier effort into makeing it stable.
THEN we can moan and bitch about the cosmetics.

Oh granted.

But these things should be mentioned as bugs, otherwise we're not doing our duty as alpha testers properly

Absolutely, however there is a need to see what bugs have a higher priority.
And at the moment, it is definatly the crashing.
Things like the linebreak bug are easy to fix, however it helps us nothing if the client remains unstable.
And reading the forum, I seem to be missing a sence of priority on some people.
I'm sure LL is doing what they can, and I hope we will get some awnsers next meeting.

I agree this is not a serious crash-related bug, yet it's very annoying (especially when you're in a mall and the vendors have heavyweight floating texts over them), and the fix should be as simple as:

-> bubbleText="";

in the text concatenation loop So a one minute fix that could simply be slipped in with a stability patch.