Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.4.1 blank screen #11034

Closed
rev138 opened this issue Oct 2, 2019 · 11 comments
Closed

1.4.1 blank screen #11034

rev138 opened this issue Oct 2, 2019 · 11 comments
Labels

Comments

@rev138
Copy link

rev138 commented Oct 2, 2019

Description

I am experiencing the problem described in #10983 using 1.4.1

image

@rev138 rev138 added the T-Defect label Oct 2, 2019
@turt2live
Copy link
Member

matrix.gibberfish.org reports using 1.3.5, not 1.4.1 - are you sure this is with 1.4.1?

@rev138
Copy link
Author

rev138 commented Oct 2, 2019

Yes. I switched back because it's broken.

@turt2live
Copy link
Member

Have you self-compiled Riot or are you using a downloaded release? The error you're getting should only be present if the thing was compiled itself without the required attention (this release is a bit weird).

@rev138
Copy link
Author

rev138 commented Oct 2, 2019

Self compiled. Did I miss something?

@turt2live
Copy link
Member

Try:

  1. Delete node_modules of all 3 layers.
  2. yarn cache clean
  3. The regular compilation process.

@rev138
Copy link
Author

rev138 commented Oct 2, 2019

Ok, I did this:

rm -rf node_modules/*
yarn install

This complained it couldn't find "rimraf", so:

npm i rimraf
yarn install
yarn dist

This created dist/riot-v1.4.1-dirty.tar.gz, which when unpacked still gives a blank screen.

@turt2live
Copy link
Member

Is the error fixed? The error in your original post is a dependency error and so should be fixed using the instructions.

Using npm probably didn't help - try yarn add rimraf instead.

@turt2live
Copy link
Member

Also the cache clean is important.

@rev138
Copy link
Author

rev138 commented Oct 2, 2019

Sorry, yes. I did the clean. Using npm got me past the rimraf error. I'm not sure what to do next.
Why was that tarball "dirty"?

@turt2live
Copy link
Member

Repeat the steps, but use the yarn command I mentioned instead of the npm command.

That could be one of the reasons the tarball is dirty.

We also publish signed tarballs at https://github.com/vector-im/riot-web/releases for every release, if you want to avoid compiling yourself.

@rev138
Copy link
Author

rev138 commented Oct 2, 2019

The official tarball worked. I'll just stick to those in the future. Thanks!

@rev138 rev138 closed this as completed Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants