secondlife / jira-archive

2 stars 0 forks source link

[BUG-216383] Opening SL Launcher causes SL to reinstall #3766

Open sl-service-account opened 6 years ago

sl-service-account commented 6 years ago

Steps to Reproduce

trying to open the viewer

Actual Behavior

Instead of launching Second Life as it should, the launcher searches for updates then asks to run the set up app. If I agree then the entirte program reinstalls. If I don't I am told that the viewer has failed to launch.

Expected Behavior

the viewer to open

Other information

Any help would be deeply appreciated, I have tried uninstalling and reinstlling everything but no luck.

Links

Related

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-216383 | | Summary | Opening SL Launcher causes SL to reinstall | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Reporter | LeonarasLenin (leonaraslenin) | | Created at | 2018-06-02T18:34:20Z | | Updated at | 2018-06-04T00:22:53Z | ``` { 'Business Unit': ['Platform'], 'Date of First Response': '2018-06-02T13:51:59.562-0500', "Is there anything you'd like to add?": 'Any help would be deeply appreciated, I have tried uninstalling and reinstlling everything but no luck.', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': "Instead of launching Second Life as it should, the launcher searches for updates then asks to run the set up app. If I agree then the entirte program reinstalls. If I don't I am told that the viewer has failed to launch.", 'What were you doing when it happened?': 'trying to open the viewer', 'What were you expecting to happen instead?': 'the viewer to open', } ```
sl-service-account commented 6 years ago

Alexa Linden commented at 2018-06-02T18:52:00Z

We're sorry you're experiencing this issue along with others. We've done this blog post to explain how to fix this issue https://community.secondlife.com/forums/topic/423151-viewer-515515811-release-issues-for-5312018/

"Greetings Residents!

To all our 32 bit Windows users and a select group of 64bit Intel HD graphics users too, we’re sorry.

Before noon (PDT) yesterday, 5/31/2018, we released the latest version of Second Life, version 5.1.5.515811. At the time of release there was an error defining the location of the 32 bit version of the Second Life viewer download. Because of that error, we delivered the 64 bit version of Second Life to everyone, even if your system was not capable of running it.

This morning we saw an increase of bug reports and community blog posts about viewer updates being stuck in a loop and began investigating immediately. Ultimately we discovered the flaw was the lack of a valid download link to the 32 bit version of Second Life in our update system. We corrected this swiftly just before noon today, 6/1/2018.

Anyone that did not attempt to log in to Second Life during that 24 hour window will not experience any issues. Anyone capable of running the 64 bit version of Second Life, was not impacted and shouldn’t have noticed anything but a normal Second Life viewer update.

Unfortunately, anyone limited to the 32 bit version of Second Life, that did attempt to log in to Second Life during that 24 hour window is now likely stuck in an endless loop of trying to install the 64 bit version of Second Life.

There is a way out of this loop. Updated Instructions.

Uninstall the the 64 bit version of Second Life

Open your file explorer in Windows

In the address bar type in %appdata% and press Enter

Locate the SecondLife folder and open it

Locate the downloads folder and delete it (this is where the incorrect 64 bit version keeps trying to install from)

Install the 32 bit version from: http://download.cloud.secondlife.com/Viewer_5/Second_Life_5_1_5_515811_i686_Setup.exe

Launch Second Life as normal (if this does not resolve your issue please file a bug report at https://jira.secondlife.com)

Thank you for your patience and understanding, we stumbled and we’ll make corrections to our processes to ensure this doesn’t happen again."

Does this resolve your issue?