Server Bugs

Both group chat and IM failing to initiate. I mostly experience it in Firestorm Social Island (simhost-0be97bd680c67540a.agni), as do the rest of the team. Starting an IM with someone else will work most of the time and every once in a while end up with a popup stating "Unable to start a new chat session with Username. The session initialization is timed out". Group chats will either fail silently or give the following message inline: "Second Life: You are the only participant in this IM session. Your message is not being broadcast at this ti2me." Tested on Second Life Release 26.1.1.23806384790, Alchemy Beta 7.1.9.2516 and Firestorm 7.2.3.80036.

When an avatar has to be moved to a hub because they cannot be in the region they are otherwise meant to be in (for example, because it is offline when they are trying to log in), they should only be moved to a hub that matches the content rating of the original region. For example, if they are trying to log into an A-rated region and can’t go there, they should not be dumped into a G-rated hub. The reason for this is because when you move someone to a different content rating without warning them, you can’t expect them to be dressed appropriately for the new rating. I saw a rather sizable crowd of people at a landing point of a hub during the weekly rolling restarts. They were a mix of naked, bruised, bloody adult avis covered in BDSM gear and child avatars who had been dumped in from somewhere else. Many of them were AFK because they had pressed the log-in button and left to go do something else while they waited to rez in. I have since learned that this is a routine problem that hubs have to deal with. It is not a mess that can be cleaned up instantly and there is no reason why it has to be happening in the first place.

On any sim now starting on 5-15-2026 I have voice, I can use voice and microphone, but within 30 seconds it greys out my microphone. I can still hear people. Restarting voice sometimes turns it back on but usually does not and even when turned on it will grey out within 30 seconds again This happens on Firestorm, Alchemy, and the flatpak version of Firestorm on both Arch based and Debian based distributions (IE Ubuntu)

I first became aware of this when I noticed my aircraft weren't going into "taxi" mode on landing. It was hard to chase down the origin of this behavior, but I eventually discovered that a script containing collision_start()/land_collision_start() event handlers was being TURNED OFF on region crossing... but only on rare occasions. I might cross 20 borders without this happening, or even 50 or more. It seems like it's more likely to happen in certain areas, such as the stretch of sims starting just south of Santa Catalina and continuing east across the Blake Sea to that giant four-sim airport in the Norwegian area. I suppose if they're homestead sims, that could explain why that particular area seems more susceptible to it. That has been by far the most reliable place for reproducing this bug. I grepped all of the scripts in the whole object for llSetScriptState() calls. There are none. (No reason there would be in the first place.) I found that removing an llSleep() call just after a collision_start() event caused the rate of the script halting to be greatly reduced. I theorize that the chain of events is something like this: Vehicle crosses sim border. Occasionally, this causes a spurious collision_start() or land_collision_start() event. (This happens well up in the air, obviously, so it isn't a "real" collision. Probably a race condition between the vehicle and avatar entering the sim in some stochastic order.) Something about the invocation of llSleep() when the vehicle is still actively being handed off fritzes something in the simulator; and it responds by halting the script, OR by failing to return control after llSleep()'s time has elapsed. Whatever the cause, the script's "Running" checkbox is disabled, and it is quite inert.

I've just noticed during today's Tuesday grid roll, at least for LearningCenterDT, that while the restart timer is active, new user accounts are still being dropped in. I recommend that for the duration of the roll, any welcome-type region on the channel being rolled should not be accepting any new or very young accounts. As a new user, it would be highly discouraging as your first experience of the platform, to get a big scary screen shake, a loud alarm sound, an unremovable timer, and getting booted out when it reaches zero, without even knowing the slightest thing about what is going on. If a new or very young user decides to teleport manually into a welcome area region that is still to be restarted, a scripted message could be sent in friendly language that notifies the user of what might happen if they hang around for too long.

Current state of voice is a dumpster fire. Dropped calls, failed calls, sudden local voice failure. The webRTC roll out is a disaster

We did 11 races in January with all together 96 racers and have about 7-12 racers per race. A race takes normally max 40min. But there was not a single race in January all sailors finished without disconnects or thrown off the sail boat on crossing sim boarders The region "Depace" is the worst sim in the last weeks. We crash there most of the times either on the crossing into Depace or out of Depace. It happens as well when someone sails alone there. There is not much underwater stuff that needs to be rezzed long. So there is no actual reason for these crashes there. Check the sim Depace first and seriously and don't just look at some general parameters or values. Do a serious check including server address changes and all those things. The other sims start getting the same issues more and more. So the whole area is worth to be seriously checked. and i talk about all these sims: Stodierski, Mautte, Paltiete, Mon Bayete, Degrand, Sarante, Petaccio, Rexach, Betacourt, Feraco, Repaci, Castrum, Palmerston, Rafeiraga, Valdivian, Couse, Gerache, Collhaytah, Port Pawtee, Maris, Conwy, Port Gonnornertnert, Quimadra, Depace, Lavaca, Val Encia, Benach, Coull, Oprince, Getachew, Wyrldmaker, Corpening, Geffers, Costagliola, Cottier

Users who enter the Patatina region are experiencing persistent communication delivery issues affecting private messages, teleport offers, object delivery, and online/offline presence status. This has been ongoing for more than a month and appears to affect a large percentage of users who visit the region The issue continues after users leave Patatina and is usually only resolved after relogging. Weekly scheduled Linden Lab restarts have not resolved the problem, and the behavior has been observed on both third-party viewers and the official Second Life viewer. It is a very high-traffic region (Support ticket #2506835, "After investigation, it appears as though this issue may be a bug or error which would be best handled through our bug report system using Second Life's new feedback portal")

When engaged in a two-person call, (if you can even start the call, most times the mike button and or the phone button in the im window are greyed out, requires multiple refreshes to make it work) once you have gotten the call to work, after 5 to 10 minutes the call drops, and you receive the multiple . [2026/05/11 17:29:09] Tee Quandry (Tee Cramer): call again had to refresh voice [2026/05/11 17:29:15] Second Life: You started a voice call [2026/05/11 17:29:30] Second Life: You started a voice call [2026/05/11 17:30:05] Karas Quandry: go bvack to discord [2026/05/12 14:38:28] Second Life: You started a voice call [2026/05/12 14:39:18] Second Life: You started a voice call [2026/05/12 14:39:44] Second Life: You started a voice call [2026/05/12 14:50:21] Karas Quandry: Marius is on changed his name [2026/05/12 15:10:03] Second Life: You started a voice call [2026/05/12 15:10:08] Second Life: Your call has been answered [2026/05/12 15:12:53] Second Life: You started a voice call [2026/05/12 15:12:53] Second Life: Tee Cramer started a voice call [2026/05/12 15:12:53] Second Life: Tee Cramer started a voice call [2026/05/12 15:12:54] Second Life: Tee Cramer started a voice call [2026/05/12 15:12:54] Second Life: Tee Cramer started a voice call [2026/05/12 15:12:54] Second Life: Tee Cramer started a voice call [2026/05/12 15:12:55] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:02] Second Life: You started a voice call [2026/05/12 15:13:03] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:03] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:03] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:04] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:04] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:04] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:04] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:05] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:05] Second Life: Tee Cramer started a voice call [2026/05/12 15:13:05] Second Life: Tee Cramer started a voice call This occurs no matter what region you are in. Further, when you have more than two people in a call, at least one is kicked from the call and is unable to get voice to work. this is in calls of 3 or more. This is becoming very frustrating. Also, when teleporting in call of two or more, the call is dropped for all parties. and you get the repeated message as above. Can we go back to the old voice system? it was cranky but it worked better than this new one. This involves both Linden viewer and Firestorm viewers.

After spending a certain amount of time in a region, the player enters a state where they can continue to remain in the region, interact with things in the region, and chat in local or IM indefinitely, but when they try to teleport out, cross a border, or certain other actions, it will fail and they will be logged out. This is a relatively old issue, and having spoken with Monty Linden about it, it appears (at least as I understood it) that the player becomes soft-disconnected from the grid, without disconnecting from the region they're in. What's different now (within the last month or two) is that the amount of time needed to be spent in the region to trigger this has vastly shrunk, from several hours, to as little as 5-10 minutes. As a result, more and more people are experiencing teleport and crossing failures and random logouts recently. Edit: This state can usually be identified early by alt-camming on something far away. While the surrounding regions already loaded will remain loaded, all regions beyond them will never load, even when alt-camming on something that puts them well within the view range.