Skip to content
This repository has been archived by the owner on Jun 4, 2023. It is now read-only.

White Screen of Death? #313

Closed
ghost opened this issue Aug 30, 2019 · 7 comments
Closed

White Screen of Death? #313

ghost opened this issue Aug 30, 2019 · 7 comments

Comments

@ghost
Copy link

ghost commented Aug 30, 2019

Bug description
Every time I go into the "Address Bar" settings, a white screen appears and requires a close of the browser to fix.

To Reproduce

  1. Open Wexond
  2. Go to Settings
  3. Open Address Bar settings

Expected behavior
The address bar settings were supposed to appear.

Screenshots
Just a white screen, should be obvious.

Details:

  • Operating System: Windows 10 (x64; Insider; Version 1903)
  • Wexond version: 3.1.0
  • Last known working Wexond version: 3.0.1
@sentialx
Copy link
Member

Please show me your ~/.wexond/settings.json file and try opening dev tools with Ctrl+Shift+F12 while the error occurs.

@ghost
Copy link
Author

ghost commented Sep 1, 2019

No problem.

@ghost
Copy link
Author

ghost commented Sep 1, 2019

This is the .wexond/settings.json file:

{"darkTheme":false,"shield":true,"multrin":true,"animations":true,"overlayBookmarks":true,"suggestions":true,"searchEngines":[],"searchEngine":-1,"startupBehavior":{"type":"continue"},"version":"3.1.0"}

This is the development tools prompt in the settings in Wexond (it's a GIF, so click on it to view it):

ezgif com-optimize

@sentialx
Copy link
Member

sentialx commented Sep 1, 2019

I don't know how is it possible you have searchEngine in settings.json set to -1. Also, I've been testing removing .wexond, installing 3.0.1 and upgrading to 3.1.0 and everything worked fine. So you may want to just set the searchEngine field to 0 instead of -1 or just to remove settings.json.

@ghost
Copy link
Author

ghost commented Sep 1, 2019

Very peculiar, but thank you for the prompt response!

@ghost ghost closed this as completed Sep 1, 2019
@xylobol
Copy link

xylobol commented Sep 29, 2019

This seems to be a really strange bug-- I've just encountered it on Windows 10. The steps @sentialx posted fixed it, but this shouldn't really be possible in the first place. I'm going to play around later to see what causes this.

@sentialx
Copy link
Member

I think I've fixed it recently. It happened when changing the search engine.

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

No branches or pull requests

2 participants