|
|
|
Confirmed that i also have this issue with group IM
In addition Group management and usage seems to have issues also Inability to send notices or proposals inability to change charter display of group members as "no text" incorrect last login dates corrupted dates in notices sent other 1.15 issues more as i find em Yes franko, I have noticed the "other 1.15 issues" that you have in your previous post. The only reason why I haven't mentioned it is I just figured it may have something to do with the fact that the grid only came back 9 hours ago. hehe.
Yes yes. This is a very serious threat to groups, introduced during the 1.15.02 upgrade. Worringly, I don't see it mention on the SL blog as something to be resolved soon.
The fact that error popups are appearing, sometime erroneously, and IMs are arriving unpredictably and out of sync is bad enough - the suddenly increased rush of messages about people leaving the session is driving people mad. I predict a mass of people leaving groups if this isn't address ASAP. The lack of group member names on big groups (I'm seeing 1 on 10 on my 900 person group) is a REAL problem too - I have no way suddenly of changing roles, something I need to do multiple times a day. If I can't see this logged elsewhere, I'll log it asap. Look at this quick, soon, now please! Thanks OK, I've created
Due to the numerous people in a agreement with this problem, I have raised the priority to Blocker. This is a problem that MUST be fixed. It is interfering with the lives of every resident in an actively running group.
Priority lowered to "Critical". Please see: https://jira.secondlife.com/browse/SVC-137#action_12711
 Linked to internal SL-41354 - "Group chat IM reopens and error is received when attempting to send a message after user has closed group chat session".
[12:21] Monk Zymurgy: arrgh..what is with all thes left this session IMs..is this a bug in the new client?
[12:21] WarKirby Magojiro: Are group Ims fixed yet? [12:22] Constantine Amat: think so [12:22] Second Life: Frosty Fox has left this session. [12:22] Second Life: Nicky Masukami has left this session. [12:22] WarKirby Magojiro: finally [12:22] WarKirby Magojiro: Arg [12:22] Chrome Heron: nope [12:22] Second Life: Chrome Heron has left this session. [12:22] Second Life: Michael Sullivan has left this session. [12:22] Second Life: Ey Ren has left this session. [12:22] Mykael Goodman: Nope. Still broken. [12:23] Saskia McLaglen: still buggered [12:23] Chrome Heron: looks like [12:23] Saskia McLaglen: guess they still ahve not fixed it :/ [12:23] Second Life: Sauron Dryke has left this session. [12:23] Second Life: Arnout Sequent has left this session. [12:23] Saskia McLaglen: that was going on since wednesday, yes _ [12:23] Second Life: Scarabeus Kurka has left this session. [12:23] Second Life: Piero Padar has left this session. [12:23] Second Life: Constantine Amat has left this session. [12:23] Ashira Legien: No .. the blog says they may be delayed after a tp [12:23] Nardok Corrimal: yeah [12:23] Saskia McLaglen: nope [12:23] Second Life: vaguegirl Petty has left this session. [12:23] Second Life: Mykael Goodman has left this session. [12:23] WarKirby Magojiro: 30 seconds fgor that to appear [12:23] Second Life: Andronicus McMillan has left this session. [12:23] Second Life: Michael Sullivan has left this session. [12:24] Second Life: Mykael Goodman has left this session. [12:24] Second Life: Innes McLeod has left this session. [12:24] Second Life: YourA Misfit has left this session. [12:24] Second Life: Andronicus McMillan has left this session. [12:24] Second Life: Mykael Goodman has left this session. [12:24] WarKirby Magojiro: I'm going to take a wild guess and say not fixed, then [12:24] Second Life: Constantine Amat has left this session. [12:24] Second Life: Bibi Book has left this session. [12:24] Second Life: Kianeira MacDiarmid has left this session. [12:24] Second Life: Fellon Celt has left this session. [12:24] Second Life: Constantine Amat has left this session. [12:24] Second Life: Reginald Lineker has left this session. [12:24] WarKirby Magojiro: Fucking error messages [12:24] Second Life: Chrome Heron has left this session. [12:24] Second Life: Sauron Dryke has left this session. [12:24] Second Life: Secondblood Priestly has left this session. [12:24] Second Life: Innes McLeod has left this session. [12:24] Second Life: Secondblood Priestly has left this session. [12:24] BrunoOlsen Oh: no [12:24] Second Life: Morpheus Madurta has left this session. [12:24] Second Life: Elfeux Yeuxdoux has left this session. [12:24] Second Life: Mo Hax has left this session. [12:24] Second Life: dstmars Zuhrah has left this session. [12:24] Second Life: Pelgrim Beam has left this session. [12:24] Second Life: Piero Padar has left this session. [12:24] Second Life: Ric Dulce has left this session. [12:24] Mykael Goodman: I hope so! [12:25] Second Life: Mykael Goodman has left this session. [12:25] Second Life: Mo Hax has left this session. [12:25] Second Life: Mykael Goodman has left this session. [12:25] Second Life: Covisha Clift has left this session. [12:25] Second Life: Madeleine Fitzgerald has left this session. [12:25] Second Life: Pelgrim Beam has left this session. [12:25] WarKirby Magojiro: I'm giving it one hour, then I'm reopening the issue on Jira if this doesn't improve [12:25] Second Life: Sauron Dryke has left this session. [12:25] Second Life: Yohane Rockett has left this session. [12:25] Second Life: YourA Misfit has left this session. [12:25] Second Life: Saskia McLaglen has left this session. [12:25] Second Life: nightspirit Miles has left this session. [12:25] Second Life: Saskia McLaglen has left this session. [12:25] Second Life: YourA Misfit has left this session. [12:25] Second Life: Reginald Lineker has left this session. [12:25] Second Life: dstmars Zuhrah has left this session. [12:25] Second Life: Nardok Corrimal has left this session. [12:25] Second Life: Sauron Dryke has left this session. [12:25] Second Life: BrunoOlsen Oh has left this session. [12:26] Second Life: YourA Misfit has left this session. [12:26] Second Life: Sauron Dryke has left this session. [12:26] Second Life: SugarPlum Rockin has left this session. [12:26] Second Life: Mykael Goodman has left this session. [12:26] Second Life: YourA Misfit has left this session. [12:26] Fenigan London: yup [12:26] Second Life: Kianeira MacDiarmid has left this session. [12:26] Second Life: Secondblood Priestly has left this session. [12:26] Second Life: SugarPlum Rockin has left this session. [12:26] Second Life: Covisha Clift has left this session. [12:26] Second Life: Mykael Goodman has left this session. [12:26] Second Life: Cytherea Eagle has left this session. [12:26] Second Life: Chrome Heron has left this session. [12:26] Second Life: Pelgrim Beam has left this session. [12:26] Second Life: YourA Misfit has left this session. [12:26] Second Life: YourA Misfit has left this session. [12:26] Second Life: Mo Hax has left this session. [12:26] Second Life: Trent Platthy has left this session. [12:26] Second Life: Trent Platthy has left this session. [12:26] Second Life: Janine Cummings has left this session. [12:26] Second Life: Kianeira MacDiarmid has left this session. [12:26] Second Life: Covisha Clift has left this session. [12:26] Second Life: Secondblood Priestly has left this session. [12:27] Second Life: SugarPlum Rockin has left this session. [12:27] Second Life: Andronicus McMillan has left this session. I dare someone to count how many duplicate names are in that list. Can we put it back up to blocker, please Just to add. i'm not reopening the other issue. Just noticed it was closed as a duplicate, and not fixed.
This has issue has to go up to blocker or everyone is going to abbandon groups.
You can't leave a group IM discusion because when you try to close the session another "has left the session" IM pings up on your screen. So you open IM again to close the latest "has left a seesion" and round and round we go. Someones leaving the session never used to be posted in the session unless they had contributed to the session, why the change? Please leave this as Critical – it's a real nasty pain but it's not on the level as, say, all groups suddenly disbanding.
We should have a patch in for this ASAP, keep watching the blog @ http://blog.secondlife.com/ In relation to the issue of the group chat reappearing so that a user has to leave the chat multiple times, I'd like to point out that this only continues so long as the originator of the session remains in the chat. Once that person leaves, the session is completely terminated. I'm not sure if that means that once they leave it is terminated for everyone or if it still allows others to conitnue chatting and let everyone else leave.
Aside from the annoyance and inconvenience, this is definitely hurting business in SL too. Group communication is paramount for most businesses.
Quote from 4/26/07: [19:15] Second Life: Viola Bentham has left this session. Thank you for your help, Torley. All of the residents appreciate it.
And once again, I am still no longer noticing this problem. I have tested it with a friend... I left a Group IM session, and he continued chatting without those messages showing up on my end, then he left the session without that message showing up on my end. I no longer get the "Unable to deliver Group IM" (or whatever it says) error, and Group IMs post to the session within seconds like they're supposed to. Think you are one of the lucky ones then, I and almost everyone else in all the groups I belong to is still experiencing this.
there MAY be a problem with group IM's, michaellinden @ blog,secondlife.com
[10:53] Second Life: Ranandar Frobozz has left this session. I definitely experienced this too (all the "left this session" floodage).
Fix checked in internally, resolved and QAed in 1.15.0 (60987). Watch for it soon. Definitely seems to be fixed now. I experienced a properly working group chat session today.
Very very definitely NOT fixed now. In addition, messages are showing up out of order, with replies appearing before the original message...
Thank you sooo much, Torley, and all the other Lindens who have helped to fix this problem. This has been a major problem with those who like people to remain a part of their groups, hehe.
I am really looking forward to the update. Proposed fix: split the IM window into a participants and messages view, make it resemble IRC. being able to doubleclick on names to bring up profiles and/or muting people would be a bonus, and you would be able to tell who's participating in a group chat AND get rid of the spam.
IRC has been this way for ages and it's a proven convenient way of doing it. Well, it most certainly isn't fixed, and won't be for a while. Since we had an update that ran over time, and then another downtime that ran over time and didn't fix anything, personally I'd like to see a downtime now to properly fix it, even if a download is required.
Basically I have hardly been able to send any group messages since Wednesday. It's been slightly better since Friday, in that the odd one does get through but then it usually gets lost in the plethora of left session messages that spurt in so it might as well remain lost. I get both types, error transmitting and lack of perms. This is really badly affecting my ability to work. I see all these symproms as well. I have been forced to leave all my high volume groups because of it, I am hoping this will get fixed soon, so I can rejoin.
I would like a feature to turn these messages off completely. Two settings, really:
I have many groups only for script permissions. On those groups, I am not intersted in the chat session and would never want it to open. Let theothers chat, I don't want to see it. Other groups are 1000+ people, and to print a message for every one of them who is annoyed by the "bing-bing", and closes the session, makes no sense. It is most annoying with the vendor groups such as Jevn users to have a message saying so and so has left, thousands of times within 5 minutes. Makes it difficult when you have IM history showing up in chat. Had to turn that feature off until this issue has been resolved which makes it even more difficult because as stated in an earlier comment, you have to open the IM and close it again after checking to make sure that it is not an important message.
This is most definitely still a problem. I tried to call a group meeting this afternoon and couldn't send after several attempts. When it finally got through, it took so long for me to see that it worked that my brief opening line was seen as IM spam by most and my real message got lost in the flood of "X has left the session."
I hate to be catty (I'm in the IT business myself so I know this stuff can be hard), but you guys really need to test this stuff better before you unleash it on us. With notices still broken for large groups (mine is >1,000 now) and group IM about as useful as over-cooked asparagus, how the heck is a large group supposed to coordinate? If it weren't for our forum on an external site and an information HUD I built, we'd have nothing (and I live in dread of the day you "improve" llHTTPRequest and break my HUD). This isn't so much a plea to fix this issue, since I see you're working on it. This is a plea for some better QA before you release updates. Loraan, since you are in the IT business, you should understand that programs under light load will work a lot better than programs under heavy load. I'm sure that the Lindens perform extensive testing on all features before releasing any new updates, but since not everybody can be on the beta grid as though it were the live grid, then things cannot be tested as extensively as they need to be. Sometimes, problems like this won't show up until they are under a full database load. I'm not sure what you do in the IT business, but I'm not in the IT business, and I know this. Not to be an arse, or anything, but I hate it when people bark at the Lindens for "not doing their job" and "not being good programmers" and "not testing things the way they should".
I confirm that messages containing special (french) characters (éèàçù) cannot be sent.
(running on Mac OS X) Regarding to the fact that there should be more testing before application to the main grid, I'ld like to take the occasion and make a suggestion to LL :
The best way to avoid bugs on the main grid is to report them when they appear on the beta grid. If LL invited residents to log in the beta grid during main grid maintenance, they would first be very happy to still be able to do their stuff then would take the habit of going to the beta grid. Those invitations could be made in the blog posts announcing the future and on going maintenance, in the in-world pop up announcing the imminent maintenance, and in the login screen during the maintenance. I get both error messages still! I try to run business through IM and its hopeless. Instead I have to message people individually. When I do get a successful group IM going, I can only send the original message. It does not allow me to reply or add to the IM. Someone will ask me a question and I have to answer them in a separate IM window. Whatever LL did to IMs, I wish they would put it back, it is making it extremely difficult to run any business or group.
Yes francesca, that's because the problem has not yet been resolved, which is why this issue has not yet been marked "Resolved". Also, read the Second Life blog, and you will find that the Lindens have some things to say about this issue as well: http://blog.secondlife.com/2007/04/28/second-life-version-1150-issues/
@Simil: Re: "I confirm that messages containing special (french) characters (éèàçù) cannot be sent. " I think that's already a separate issue on the Issue Tracker.
And yes, during Main Grid downtime on the blog, we do invite Residents to try the Beta Test Grid, including links. (See previous posts.) @Leroy: Thanks for your continued help across issues. Just to reiterate, the fix for this (VWR-513) isn't in a public release yet – it's only internal, and looks like it's gone through Quality Assurance, so as part of the release process, is planned to be included in the next viewer deploy. This issue will be resolved when the fix is "live". Having the same problems with the mac OS X client.
Group and friends conference IM's are not working and I keep getting "has left this session floodege. I also keep getting the following messages: and: Hardware Overview: Machine Name: iMac Forgot to add:
Error starting a new IM session with group. Error making request, please try again later. There's been some confusion here about several different group issues. Jeska Linden just made a blog announcement re: group IM fixes for tomorrow:
» http://blog.secondlife.com/2007/05/01/grid-downtime-tomorrow-from-9am-until-11am-pdt/ As noted, these are included in the fixes: 1) "X has left the session" is not seen when someone has spoken then left the group IM session We'll revisit some of the finer points of this tomorrow. @WorkingOnIt : The special character issue is described in this report, that has a general title. I couldn't find the report that you mean.
I've checked all Grid Status post for the last 2 months and only found 3 invitations, I think you really need to tell residents that the beta grid can be just like the main and that there's nothing techy about it.. After the update, the spammy "X has left the session" are gone but now no matter how many times you close the tab, it will reopen everytime someone sends a message.
I can affirm what Simil wrote before. If you have a heavy chat, for example in a group with many members, f.e. concierge info, you can click 10 mins the close button. Now people make also a fun out of it. The problem with delay and "Error messaging chat session with group_name. You do not have sufficient permissions." still persists from time to time.
Post-May2nd-update:
I have the same problems:
::sighs:: Ditto me on Mac, but at least the looney left session spam has gone. But please, can't we supress those anyway? Who cares on a Group IM?
But the tab not staying closed is a major major irritation. And I'd like to ask why it is, that this implementation of messaging, along with dropping ratings, was suppossed to reduce load and therefore lag, but in fact lag seems to be worse since this 1.15.02 update.... Might as well give us our ratings back. Thanks for the additional info. The specific internal issue of "Group chat IM reopens and error is received when attempting to send a message after user has closed group chat session" (SL-41354) is still open, so no, I don't think that was fixed yesterday. I'll check with our devs to confirm.
This issue really hindered the ability to listen and comment on todays Town Hall. I would ask that we find another method like VOICE and Radio Linden to have these until GROUP IM's are working correctly again.
Alot of the content of the town hall was missed by many users wanting to hear and comment on the issues at hand. Town Hall related issues:
@jefferey: Agree, it was very difficult for all of us affected. We previously used repeaters but those busted ~1.13, and it was bad timing that group IM's problems exacerbated so heinously. We're continuing to work towards voice (we've held Town Halls with Skype before).
@Alexandria: Thanks for keeping track so tidily, I saw this too: Error messaging chat session with Linden Town Hall Closed Captioning. continues to be a problem even after "fix" this weekend. Especially on Lucky Chair Alliance group which works then doesn't work repeatedly. Attempts to post IMs either work, fail with our without a pop-up saying it failed or pop-up message says it fails but it does post.
Lag on posting appearing actually seems longer now. And I will see clusters of messages appear at once, among them one I posted awhile ago. Just had update 1.16.0.5 today and almost a MONTH since this started it is still happening ?
Can no one fix this? Still in today's update, 1.16.0(5), on Mac OSX, someone else opens a group IM session. I close the session quickly. Within seconds, the session reopens with another IM. Close again, the session reopens with another IM. Seems to be impossible to close a group IM session at the moment. I finally just deleted the group! No more problems.
This seems to be worse since the new build and I haven't see a group IM session working :?
This was thought to be fixed in 1.16; our original method doesn't repro:
Observed Result: but as noted, we're still seeing problems with this. Can you please confirm # of members in groups that you're seeing this with? We think it may just be larger groups and want to fix it for sure, but need the info. Thanks! Friends list is effected too. see https://jira.secondlife.com/browse/VWR-841
I forgot to add that the reason the friends conference issues and friends list issues are related is because when the friends list does not display any friends Evan though they are online friends conference will not start. The Friends conference depends on the friends list status as it connects ONLY to friends who show online on the friends list. Friends who are online but do not show up as off line will NOT be included in friends conference, that is why I reported this as a separate issue.
Still seeing issues with group chats, I get a false error message every time I send a message.
the message goes thru, but i still get the false error message, saying the message could not be delivered try again later. Relogging and restarting group chats does NOT clear up the problem. Of all the groups that I am a member of, Scripters of Second Life is the largest, and the IM for this group has this issue more consistently than any other group. I would say that at least once per log-in I get error messages for SoSL while many/all other groups are still working just fine.
I think this was closed in the last Wednesday update
I see it is fixed internally.. How about FIXING it externally and not letting it slip through the net again?
It's happening again. For a small group I am in, tonight (Tuesday) I got the "Error messaging chat session with [group name]. Error making request, please try again later." This came after a few seconds delay. Notices did not popup for this group either, so I had no way to communicate with it at all.
Reopeningn this. This issue is NOT fixed as of 1.17. Still getting Errors, messages not appearing.
Errors not fixed, but at least I can post in Japanese now. Kudos on that.
I've also confirmed, group IM errors are still present after today's required update. I can't send messages to Scripters of Second Life due to this error.
Errors not fixed, but at least I can post in Japanese now. Kudos on that.
A suggestion: when people log into the beta grid, have them auto-joined to a "test group IM" group. That way, you can stress test group IM under a larger load than you might otherwise get. SOSL is possible the most active group IM in SL, so you need to simulate the conditions that it has. You also need to have the jira menu stuff appear at the bottom of the page for these really long comment sections. BTW, the bug I am getting now says I lack permissions to post in IM group. Before it said there were problems establishing connection. This seems to be a new bug error, if not a new bug...
Still not fixed as of the new client downloaded today after the maintenance outage. This is getting ridiculous, folks...
Ok....we probably shouldn't have highlighted this as a great issue to have open. We fixed many things with group IM. There may be things that are still broken, but I'd like to ask that instead of reopening this issue, please open a /very specific/ issues that describes exactly one problem with group IM. If there are multiple problems, then enter multiple issues.
We're sorry if you're still having problems with group IM, and want to address any issues. However, reopening a vaguely worded issue is actually not going to be the best road to getting the problems resolved. For guidelines on effective JIRA use, see https://wiki.secondlife.com/wiki/Issue_tracker "Resolved/Fixed" is not the correct status for this bug. "Misfiled" or "Needs more info" is more appropriate. It is certainly not "Fixed".
Consider at least transferring the votes to VWR-1298, which seems to come closest to the root cause of the problems reported here. It doesn't seem reasonable that one of the top rated annoyances effectively has been dropped to zero votes. How is this fixed? Will it be implemented in a newer verion? Coz' as per today I have the same problem as described at the top.
I'm still getting this kind of error.
Seems less frequent know, but anyway its there. Could be related to osmekind of timeout. Please look at this again, it seriously harms our SL experience that we cannot have reliable chat sessions. Please don't use this issue anymore and use the more-specific issues for bugs (see under "related"). It's not useful to have everything in one place, since nobody knows which problem you're talking about.
Rob, please.
This error message is still appearing. I don't see how more specific you can get on a JIRA message that deals with a specific error message coming inworld in groups. Owners, members of groups attempt to open an IM session, and can't. Or they type, and get this error message. We're getting it now. By closing this proposal, and claiming that others duplicate it, what you do is cut off and freeze 94 – 94 count 'em! – votes! That's just plain wrong. And that's why this constant zeal to closure and claim as dupes or resolveds has to stop without the consent of the author. The 94 people who voted for this can't be expected to figure out that they now have to come on to the JIRA and re cast their votes in order to get them to count, and move up the popular list which means to Linden attention as a priority. It's just not right that these 94 votes get canned, and only some stragglers figure out to go re-vote on the new "better" proposal, which isn't demonstrably better. TUi Student Learning Group has been down for weeks. Our attendance is reflecting our inability to post classes as they're about to begin.
A group that I personally paid to create, Read Through the Bible this Year has also been down. I really appreciate any help. only surprise how fast the popup comes up , juts when u click IM in group :
Error starting new chat session with group since more then a week now in several groups , not depend on client , region , time or user L's SkyClub VIP has 'only' about 700 members , so as posted in other topics this can't be a 1000+ problem ; and if a group has this probem , its constantly ( no need to 'try again later' , it will not work for this group ) I get the following error on several clients but not with all groups that i'm involved in.
i know there are others online to but still get the error. The only way to get it to work is if both sides open the group IM window manualy. [5:43] Second Life: You are the only participant in this IM session. Your message is not being retransmitted or stored. I get this problem when i try to open and write on chat IM
Second Life: You are the only participant in this IM session. Your message is not being retransmitted or stored. And sometime i receive no error but the message even appear in the chat group...and i get the error messaging group all the day. i receive these error and message with all the version of the wiever Both, the TUi Student Learning Group and the TUi Neophyte (teachers) group channel are not working. This is a catastrophe.
Group IM's have been severly borked for months but now they have completely stopped working - havent' worked at all since sl was offline on Saturday 4/5 - basically bringing the rp community to a standstill!
TUI Student Learning Group continues to work on only a "hit-or-miss" basis.
Fashion Consolidated Cafe group IM ceased to work on April 10. I am told that Fashion Emergency group IM also ceased to work at around the same time.
By this I mean one can not post anything at all, get any messages, or any error messages. Updated affected versions
Various groups are intermittently affected: SecondLife Hobos Group IM failed for group Helpful Hands
Group IM initiated by Darlean Fairymeadow, I was with her on the same parcel in the same SIM and I never saw it. Two others, also on the same parcel, Rene Lefevre did not receive the group IM, Carmina Marchionne did get the group IM. Unknown at this time if other members in other places did or did not receive the IM. Second Life 1.21.0 (95157) Aug 26 2008 16:03:19 (Second Life Release Candidate) You are at 264638.8, 253751.3, 21.4 in Moy located at sim4592.agni.lindenlab.com (63.210.158.242:12035) CPU: Intel Core 2 Series Processor (1866 MHz) There have been a million damned JIRA issue raised on this and the total of what has been done, erm, well. Perhaps somebody could enlighten me on that matter.
This is something that affect everyone using group chat, which is a very large number of people. Group chat is unreliable and regularly just throws out messages with the error boxes attached - sometimes to then display them later, sometimes not. Group chat is a joke, now, and I absolutely do not accept that there is no alternative to this sort of joke. This, like "failed TPs", "expired region handoffs" and "severe rubberbanding or getting orbited crossing sim boundaries" seems to have slid into the growing category of "known issues so well-known that we're now expected to ignore them because they're hard to fix"
This problem has gotten worse and worse. it's getting to the point where group chats can't be used.
Hardware Overview: Machine Name: iMac GeForce FX 5200: Chipset Model: GeForce FX 5200 This isn't a showstopper, more like a nagging problem. Only set bugs to showstopper if it makes SL totally unusable.
It's a heckuvalot more than a "nagging problem" for many SL use cases.
There are forms and styles of RP that need this to work correctly, and it's pretty severely broken on an unpredictably intermittent basis. Also the fact that it sometimes delivers messages out of order is troublesome, too. I'm not downplaying the fact that it's a major issue. The point you missed was that it's not a showstopper: It doesn't make SL entirely unusable. A case could be made for a critical bug, but I'm inclined to lean against going even that high as it doesn't render basic core functionality (building, economy, local chat) unusable.
In fact, the guidelines for showstopper are written such that only a "nobody can login" situation is clearly a showstopper.
So I guess your point that this doesn't qualify either is well-taken. But depending on your own use cases, different components are "basic core functionality". If you spend all day standing around in an infohub, local chat is core....or maybe voice is. Building isn't core if you're not a builder. Economy may not matter to an educational or business conferencing user, etc. So when they come for your personal favorite functionality, just remember... it's not a showstopper. It's just a nagging problem. As it is, group chat has a been a perennial mess since 2007 and it currently has 166 votes, and it's still severely broken. I sure hope the infrastructure improvements FJ has people working on bring about a major improvement in stuff like this, because it's clear that the current implementation is far too brittle for the infrastructure it's being asked to run over today. Ms. Darwin,
The priority field is to give a general idea of just how severe the problem is to the overall health of the project (in this case, the entire metaverse as a whole; arguably this should be a SVC ticket and not a VWR ticket since the viewer's not doing anything wrong, it's just showing what it got from the grid). The vote count is a general idea of how many people have also encountered and confirmed the bug and want it to be fixed expediently. Let's not kid ourselves by confusing the two and claiming a few group IMs getting through is on par with an actual showstopping condition like a major network outage causing logins to unexpectedly fail. That's like calling 911 for a pothole (after all, the city owns the fire department and the road the pothole's on, and they get there faster if you tell the city you have an emergency, right?). Indeed, let's not kid ourselves.
VWR-513 documents ongoing failures that are a heckuva lot worse than "a few group IMs not getting though". It's massive data loss, albeit intermittant, and additional confusion caused by double posted and out-of-order chat. Sometimes I wish it was permanently broken, so we'd stop pretending it's working, because it isn't. Obviously you don't use it personally much, because otherwise you'd know how bad it is and wouldn;t be trying to minimize it. But other people do use it, and some of them rely on it to conduct business. Like product support, for example. I conceded that by the current status guidelines "showstopper" doesn't apply here, because, as you observe, nothing but a massive network outage or Linden balance corruption would fit. But by the same token, "PJIRA isn't for technical support". so maybe the status of "showstopper" is meaningless here and should probably be removed, because as far as I can see the situations it covers are mostly not suitable for PJIRA anyway. That said, I sympathize with frustrated residents who hope raising the severity – again, admittedly in contravention of the guidelines – in hopes of getting the frakking thing fixed. By the way, this should probably be moved to the SVC project, because I don't think anybody believes it's a viewer problem anymore. Anybody? I concur this is clearly a service issue not a Viewer issue.
group chat lag is still intermittently 3-4 min for me. So I added my vote. Seems to be worse in large groups. Someone will ask a question, then there well be a long wait, then so many responses post at the same time that they scroll off the window. People think no one is responding, so they do, when in fact it's the chat lag monster having lunch. Other times group chat is normal.
do we really have to vote when we can't use the basic functionality of a social networking site (game or not)?
This is why people get fustrated with linden. Its not that bugs popup but a) they make it fairly useless for a free member to get support (in my previous dealings) b) and they make a issue overcomplicated by asking people to vote to get it working Here's the thing. I can understand if it was a 1/1000 chance it would do this but it constantly happens to me. I've stopped reading or even opening much of my groups because I can't post or conversate (not a word but I'll use it anyways) with someone. This shouldn't be upto a vote! this should be fixed and it should be prioritzed because too many people get this issue and it was their update that screwed it all up. I mean this with all due respect to linden, you HAVE to get your stuff together and if needed get peple working on other projects such as mature ratings into fixing the issues instead of making new features onto old ones that don't work. That can apply to anything, not only this peticular issue.. Rant done Ok I was directed here by Minerva after asking for help with the sudden rapid deterioration in our group IM(Trilegy Corporation). The situation has deteriorated so much that the once active group IM is hardly used anymore. It may take 7 attempts (ctrl-c & ctrl-v) to get a message through. when a message does get sent by someone it closes the session of those who dont have the group IM window open. messages may or may not get through even when not rejected imediatly and if they do get through who knows what order they will appear as 3 min is not uncommon in between sending and it apearing. The group IM is the most important resource Trilegy has and theres a large number (approx 5500 members in trilegy) of frustrated residents at the end of there tether
There is a recent change to all these problems...
NOW, when a group IM message arrives, it appears in Local Chat and the tab appears briefly in the Communicate window. Then, a message pops up saying "Unable to open chat session with XXXXXX as the session no longer exists". 1) I'm NOT sending a message, I've just received one. And something else too - this error often causes a different (already open) IM tab to flash in error, as if there is a new message. When this tab is clicked on, it is perfectly obvious that there is no new message. As for the original error - posting into an active session and getting errors - this is now happening several times in a row, and I may have to repost my message half a dozen times (EACH TIME) just to get it to appear. Group IM is totally screwed up. This isn't caused by version 1.23 : I've been getting the new errors for at least a month and I'm still using 1.22 I think this is a server-side problem. I believe the same failure mode displays different error message text on 1.22 from 1.23 though.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Reopened
Major
Group IMs Not Working Properly (split into multiple issues)
When I click on a group to start a session, nothing happens, then if I send in some text the server says "Starting session with group_name please wait."
Then "Error messaging chat session with group_name. You do not have sufficient permissions."
Then if I retry I get a popup saying "Error messaging chat session with group_name. Error making request, please try again later."
Eventually my message gets to appear in the chat with a sever delay, and I get to see other people's messages, also some group tabs will jump in the floater for no reason.