Why no Linux beta clients these days?

Tofu (or any other Linden who might read this), why aren't we Linux users getting beta releases these days? From 16.0.0.1 through 16.0.0.3 we were shut out from the test grid. We apparently got a brief time with 16.0.0.4 -- I missed it, naturally -- but then 16.0.0.104 was posted for Windows and Mac almost immediately and we were locked out again.

I presume there's a reason for it -- it might be a little easier to bear if we just knew why.

Thanks,
Johanna

It's because we don't whine enough. We should start using the Random Linden Lab Flame Generator by Ordinal Malaprop and flood the Lindens.

http://ordinalmalaprop.com/tools/dear-ll.html

EDIT: JUST USE --aditi

I was ready to do some beta testing today because of the maintenance update and I found this, i personally refuse to open the Windows version to beta test it, I want my Linux beta ,

The last round of betas didn't have a Linux version because (perhaps ill-advisedly) they were rolled into the Voice branch which doesn't have Linux support.
The Linux 1.16.0.5 client is up here:
http://secondlife.com/community/linux-alpha.php
... and does connect to the test grid while the main grid is down, if you pass the --aditi argument.

Awesome, thank you so much! (for both the explanation and the link!)

Yow... Vivox not having a Linux version of their code is turning out to be quite a pain.

Aren't we (and LL) kind of at the mercy of any source of proprietary code, or rather, libraries used by the client (or the server, if that's going to be made open)? Is there any move to get rid of such dependencies in SL?

Hmm, 1.16.0.5 isn't letting me in. It waits a while (I presume due to high concurrency), and then dies after spitting the following out to the console:

2007-05-23T18:40:02Z INFO: LLHTTPRegistrar::buildAllServices adding node for path /trusted-message/<message-name>
2007-05-23T18:40:02Z WARNING: LLMessageSystem::callHandler: unknown message ChatterBoxSessionAgentListUpdates
2007-05-23T18:40:02Z WARNING: LLMessageSystem::callHandler: unknown message ChatterBoxSessionAgentListUpdates
2007-05-23T18:40:02Z WARNING: signal_handlers: *** Caught signal 11

This appears to be reproducible; it's happened three times in a row.

I notice the references to ChatterBox -- is the grid expecting voice capabilities which aren't present in 1.16.0.5?

2007-05-23T18:56:27Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.15.196:12035
2007-05-23T18:56:42Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.15.196:12035
2007-05-23T18:56:57Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.15.196:12035
2007-05-23T18:57:13Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.15.196:12035
2007-05-23T18:57:28Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.15.196:12035
2007-05-23T18:57:43Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.15.196:12035
2007-05-23T18:57:58Z WARNING: sendMessage - Trying to send RequestImage on unknown circuit 72.5.15.196:12035
2007-05-23T18:58:00Z INFO: result: LLEventPoll::Impl::completed <5> 1events (id <llsd><integer>-1645111</integer></llsd>
)
2007-05-23T18:58:00Z WARNING: LLMessageSystem::callHandler: unknown message ChatterBoxSessionAgentListUpdates


or as well an strace...

18813 write(44, "SendPacket failures: "..., 4 = 48
18813 write(44, "Dropped packets: "..., 4 = 48
18813 write(44, "Resent packets: "..., 4 = 48
18813 write(44, "Failed reliable resends: "..., 4 = 48
18813 write(44, "Off-circuit rejected packets: "..., 4 = 48
18813 write(44, "On-circuit invalid packets: "..., 4 = 48
18813 write(44, "\n", 1) = 1
18813 write(44, "Decoding: \n", 11) = 11
18813 write(44, " Mess"..., 76) = 76
18813 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
18824 <... poll resumed> [{fd=21, events=POLLIN}], 1, -1) = -1 EINTR (Interrupted system call)


i hope it will work on main grid....

tx Oh

This was a weird one! Even after completely deleting both the directory containing the executable and my ~/.secondlife directory and reinstalling from scratch, I continued to get this crash when trying to log into the beta grid using both 1.16.0.5 and 1.16.0.6.

Eventually I hit upon the idea of specifying a new location with -url, and that managed to get me in without crashing. When I restored my original ~/.secondlife directory, I could still get in, so it looks like something in the sim I had previously been in (sim13.aditi.lindenlab.com) was actually causing my crashes.

How can I find out what the inworld name is for sim13 (72.5.15.206), so I can go back there and see if I crash again?

Similar behaviour here. I log in Aditi with ./secondlife --aditi (thanks tofu), but I had to change my start location. I can login in Lusk and teleport to Sandbox Extension Island but I always crash when I enter Sandbox Island.