search

secondlife / jira-archive

2 stars 0 forks source link

[BUG-231862] teleporter failed to grant capabilities #9240

Open sl-service-account opened 2 years ago

sl-service-account commented 2 years ago

What just happened?

Every time we try to go to our sim we get this message. we get this message wherever we are in Second life      Teleporter Failed to Grant Capabilities 

Sky-Life, Dockweiler - Moderate           Sky-Life, Dockweiler (191, 16, 61) - Moderate

What were you expecting to happen instead?

teleported to my Sim   The Consortium  TriPirMex (130.82.62)

Other information

thas been happening all weekend and started on Feb 25th 26th 27th and now Monday, February 28th

Attachments

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-231862 | | Summary | teleporter failed to grant capabilities | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Created at | 2022-02-28T12:53:34Z | | Updated at | 2022-03-04T19:36:37Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2022-03-04T13:36:21.820-0600', "Is there anything you'd like to add?": 'thas been happening all weekend and started on Feb 25th 26th 27th and now Monday, February 28th', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'every time we try to go to our sim we get this message. we get this message whereever we are in Second life', 'What were you doing when it happened?': 'Sky-Life, Dockweiler - Moderate ', 'What were you expecting to happen instead?': 'teleported to my Sim TriPirMex 54 54 52', 'Where': 'windows 10 Second Life Release 6.5.2.567427 (64bit)', } ```
sl-service-account commented 2 years ago

JIRAUSER340679 commented at 2022-02-28T15:00:34Z

Problem Solved With My Region Restart        20/28/2022

sl-service-account commented 2 years ago

Kyle Linden commented at 2022-03-04T19:36:22Z

Hi Philamondi,

Thank you for letting us know that a region restart resolved the issue. I'm going to set the state of this report as "Needs More Information" so that if it ever happens again you can update this Jira and give us the chance to try and reproduce the issue while it is still happening.

Thanks