sl-service-account
commented
8 years ago Chaser Zaks commented at 2016-08-07T04:25:33Z
If I had to take a guess, I would say that one of the prim in the linkset has become locked. Unfortunately I don't know of a way to check because there is no LSL function and the flags are not transmitted on rez, or at least I don't know where the flag is at. Maybe LL can export the asset directly from the asset server and check?
Below may not be what causes it and is just a potential test for it I'd say abuse race conditions to test if this would cause it:
- Rez 3 cubes
- Race condition a lock on link 2 or 3 while linking them
- shift+copy to test
OR Test if LSL Link manipulation allows linking to locked prims.
I'll test these once I am less tired but if anyone wants to go ahead and test, please do feel free to!
I'm unsure if this should go in viewer or simulator, probably simulator.
I'm unsure if this is a bug or whether this particular asset is just corrupted in some way.
Filing just in case it is a new bug though, it's certainly odd!
Steps to Reproduce
TP to http://maps.secondlife.com/secondlife/Testylvania%20Sandbox/122/190/22 & take a copy of the brown table named "BUG-37624 repro object - Catelynn's Picnic Table".
Rez the table.
Edit table -> Object tab.
Observe the table is not locked.
Shift copy the table.
Edit the new copy of the table (the one left behind) -> Objects tab.
Observed Behaviour
The new copy of the table created by shift+copy is locked.
If you rez another copy of the table from inventory, unlink it then re-link it, the bug does not reproduce.
Expected Behaviour
The new copy of the table should not be locked.
Other Information
This table is the only asset I have found so far that behaves this way.
I have no idea how an object can get into this state.
The table was created a long time ago, so possibly it was created when there was a bug?
Reproduces on Main Channel & RC regions.
Reproduces on all viewers.
Can anyone work out how to build a new object that behaves in this way?
Attachments
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-37624 | | Summary | New copy of an object created by shift+drag is locked | | Type | Bug | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Whirly Fizzle (whirly.fizzle) | | Created at | 2016-08-07T00:55:02Z | | Updated at | 2016-08-08T17:19:42Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2016-08-06T23:25:32.958-0500', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'Filling in...', 'What were you doing when it happened?': '...', 'What were you expecting to happen instead?': '....', } ```