Open sl-service-account opened 1 year ago
sl-service-account
commented
1 year ago Kyle Linden commented at 2023-04-10T17:27:54Z
Hi Quartz,
Is this happening more frequently on just the GLTF viewer or any viewer?
This may be a server issue too so we need to rule out whether it is a specific viewer.
Thanks!
sl-service-account
commented
1 year ago Quartz Mole commented at 2023-04-10T18:20:18Z, updated at 2023-04-10T18:29:40Z
Hi, Ky!e
It's also happening with the latest release viewer. I couldn't say if it's happening more frequently with the GLTF viewer, since all of LDPW are using it right now, but I've just tested with the regular viewer and it's happening with that.
If it's any help, it seems to be an issue with large, complex, objects (e.g. New Linden Homes):
{{{}}}{}Second Life Release 6.6.10.579060 (64bit){}
{}Release Notes{}{}You are at 85.5, 163.8, 39.4 in SSP83X located at simhost-0106aacbdfc0427a7.agni{}
SLURL: [http://maps.secondlife.com/secondlife/SSP83X/86/164/39]
(global coordinates 295,254.0, 361,636.0, 39.4)
Second Life Server 2023-03-24.579022
{}Release Notes{}{}CPU: AMD Ryzen 5 5600X 6-Core Processor (3693.11 MHz){}
Memory: 16311 MB
OS Version: Microsoft Windows 10/11 64-bit (Build 22621.1413)
Graphics Card Vendor: NVIDIA Corporation
{}Graphics Card: GeForce GTX 660/PCIe/SSE2{}{}Windows Graphics Driver Version: 27.21.14.5671{}
{}OpenGL Version: 4.6.0 NVIDIA 456.71{}{}Window size: 1920x1009{}
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.125
Render quality: 5
Advanced Lighting Model: Enabled
Texture memory: 512MB
{}Disk cache: Max size 409.6 MB (100.0% used){}{}J2C Decoder Version: KDU v7.10.4{}
Audio Driver Version: FMOD Studio 2.02.09
Dullahan: 1.12.4.202209142021
CEF: 91.1.21+g9dd45fe+chromium-91.0.4472.114
Chromium: 91.0.4472.114
LibVLC Version: 3.0.16
Voice Server Version: Not Connected
Packets Lost: 6/1,165 (0.5%)
April 10 2023 11:17:57
sl-service-account
commented
1 year ago Maestro Linden commented at 2023-04-13T16:56:21Z, updated at 2023-04-13T16:58:53Z
Looking at a "regular" object that's shared with the LDPW group, such as the plywood box owned by Quartz.Mole shown in the screenshot at http://maps.secondlife.com/secondlife/SSP83X/86/164/40 , I see the following DebugPermissions:
B: VMCT
O: VMCT
G: VMC
E:
N: VMCT
F: VMCTAs expected, I as a group member can modify the box - I changed the color.
Looking at the house from the screenshot, I see this for the linkset:
B: VMCT
O: VMCT
G: V C
E:
N: VMCT
F: V CTSo the group doesn't have the modify bit set for some reason, even though the owner can modify the linkset. Given that the folded permissions are VCT, we know that the owner cannot modify some of the contents of the house - is this the reason the group can't modify things?
Looking at the contents of the house, there are several fullperm scripts in the root prim, and a no-modify (for the owner) "Color Picker HUD" object. However, none of the prim inventory items should affect the ability to modify the linkset.
I took a copy of the house, and dissected it to see what causes it to be "G: V C". I found that removing all inventory from the root prim did not impact the linkset's group permissions mask - as expected. I also see that when I toggle "Share with group" off and on again, the expected permissions are restored - the house becomes "G: VMC". It's unclear what's happening, here - perhaps some of the prims are not properly set to be shared with the group?
Going one step further, I unlinked the child prims from the home individually, then looked to see if the remaining linkset changed from "G: V C" to include the M bit. However, this didn't change anything - even when the root prim was by itself, it was still "G: V C" .
sl-service-account
commented
1 year ago Maestro Linden commented at 2023-04-14T15:23:22Z
We have an apparently bad-permissions object, but need more information in order to pursue this as a bug:
"G: VMC" mask, allowing all group members to edit? This would be the workaround for individual cases.How did the house get into this bad state - what are the steps to reproduce the issue?
For the repro steps, I found the following cases do not reproduce the issue:
"G: VMC""G: " (and appears as not shared)"G: VMC", even when the added inventory item is no-mod"G: VMC"
What just happened?
This seems to be an intermittent bug, since we've noticed it in the past. It has become a particular issue over the last few weeks.
All objects made by LDPW are set as full permissions and shared with the group, since we work collaboratively. However, it's frequently the case that objects belonging to one member of the group are not editable by other members with their LDPW tag active unless either they take their own copy of the object or the owner gives them editing rights.
What were you doing when it happened?
Attempting to edit other group members' full-perms content that is shared with LDPW.
What were you expecting to happen instead?
I was expecting to be able to edit their content and for them to be able to edit mine.
Other information
There's a workaround in that friending group members and granting them edit rights seems to work. It's an intermittent issue, but it's been particularly an issue over the last week on regions SSP83X and SSPQA, and is slowing down building and QA work for LDPW.
Attachments
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-233734 | | Summary | Full perms objects shared with LDPW group cannot be edited by group members who are not the owner | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Reporter | Quartz Mole (quartz.mole) | | Created at | 2023-04-08T20:05:33Z | | Updated at | 2023-04-14T15:23:27Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2023-04-10T12:27:53.566-0500', "Is there anything you'd like to add?": "There's a workaround in that friending group members and granting them edit rights seems to work. It's an intermittent issue, but it's been particularly an issue over the last week on regions SSP83X and SSPQA, and is slowing down building and QA work for LDPW.", 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Simulator', 'Target Viewer Version': 'viewer-development', 'What just happened?': "This seems to be an intermittent bug, since we've noticed it in the past. It has become a particular issue over the last few weeks. \r\n\r\nAll objects made by LDPW are set as full permissions and shared with the group, since we work collaboratively. However, it's frequently the case that objects belonging to one member of the group are not editable by other members with their LDPW tag active unless either they take their own copy of the object or the owner gives them editing rights.\r\n\r\n", 'What were you doing when it happened?': "Attempting to edit other group members' full-perms content that is shared with LDPW.", 'What were you expecting to happen instead?': 'I was expecting to be able to edit their content and for them to be able to edit mine.', 'Where': 'http://maps.secondlife.com/secondlife/SSP83X/86/164/39 Also noted on SSPQA', } ```