Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-230483] SL Official Viewer - Key Mapping Version 6.4.17.557391 Is Over Written by Default 6.4.13.555567 After Install Via Update Checker #8152

Closed
sl-service-account opened this issue Mar 30, 2021 · 1 comment

Comments

@sl-service-account
Copy link

What just happened?

The other day I was running the Default 6.4.13.555567 Official Viewer and was promoted that Mapping Version 6.4.17.557391 was downloaded (without my permission to do so) and asked me if I'd like to install it. I skipped it because I don't like installing things that download load without my permission.

Today I had little trouble process a linden $ purchase and thought it might be the viewer so I attempted to install the Key Mapping Version 6.4.17.557391 from the SL Website and after the install I launched the viewer and checked the version and was still Default 6.4.13.555567.

After trying to installing Key Mapping Version 6.4.17.557391 again it looks like an update checker wanted to put me back on Default 6.4.13.555567

After installing it again and once the update checker started to work I closed it from downloading / installing and wala I'm running Key Mapping Version 6.4.17.557391.

I'm really not sure if Key Mapping Version 6.4.17.557391 is better than Default 6.4.13.555567 and for that reason i'm going back to Default 6.4.13.555567.

I don't feel comfortable being in a viewer version without knowing how secure it is and reason why I should use it vs the Default?

I only tried it cause I was troubleshooting a personal issue and found that.

All good.

What were you doing when it happened?

Attempting to install another version of the viewer.

What were you expecting to happen instead?

To not have the desired version of viewer overwritten after with an update checker type thing?

Other information

nope

Original Jira Fields
Field Value
Issue BUG-230483
Summary SL Official Viewer - Key Mapping Version 6.4.17.557391 Is Over Written by Default 6.4.13.555567 After Install Via Update Checker
Type Bug
Priority Unset
Status Closed
Resolution Duplicate
Reporter Paulsian (paulsian)
Created at 2021-03-30T00:21:29Z
Updated at 2021-03-31T22:01:29Z
{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'Date of First Response': '2021-03-31T17:00:16.804-0500',
  "Is there anything you'd like to add?": 'nope',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': "The other day I was running the Default 6.4.13.555567 Official Viewer and was promoted that Mapping Version 6.4.17.557391 was downloaded (without my permission to do so) and asked me if I'd like to install it. I skipped it because I don't like installing things that download load without my permission. \r\n\r\nToday I had little trouble process a linden $ purchase and thought it might be the viewer so I attempted to install the Key Mapping Version 6.4.17.557391 from the SL Website and after the install I launched the viewer and checked the version and was still Default 6.4.13.555567. \r\n\r\nAfter trying to installing Key Mapping Version 6.4.17.557391 again it looks like an update checker wanted to put me back on Default 6.4.13.555567\r\n\r\nAfter installing it again and once the update checker started to work I closed it from downloading / installing and wala I'm running Key Mapping Version 6.4.17.557391.\r\n\r\nI'm really not sure if Key Mapping Version 6.4.17.557391 is better than Default 6.4.13.555567 and for that reason i'm going back to Default 6.4.13.555567. \r\n\r\nI don't feel comfortable being in a viewer version without knowing how secure it is and reason why I should use it vs the Default? \r\n\r\nI only tried it cause I was troubleshooting a personal issue and found that. \r\n\r\nAll good. ",
  'What were you doing when it happened?': 'Attempting to install another version of the viewer. ',
  'What were you expecting to happen instead?': 'To not have the desired version of viewer overwritten after with an update checker type thing? ',
}
@sl-service-account
Copy link
Author

Dan Linden commented at 2021-03-31T22:00:17Z

Thank you for the report, Paulsian.

This immediate update to another viewer after installation sounds like an issue we have filed internally.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant