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

Error: Cannot find module after upgrading to 1.34.4 on Windows 10 #4411

Closed
1 task done
hwinnemoe opened this issue Jul 17, 2020 · 11 comments
Closed
1 task done

Error: Cannot find module after upgrading to 1.34.4 on Windows 10 #4411

hwinnemoe opened this issue Jul 17, 2020 · 11 comments

Comments

@hwinnemoe
Copy link

hwinnemoe commented Jul 17, 2020

  • I have searched open and closed issues for duplicates

Bug Description

After updating from 1.34.1 directly to 1.34.4, I only see the following error mesage (see Screenshots) and cannot use the app. The stacktrace reads very similar to #4394 (comment).

Steps to Reproduce

  1. Update to 1.34.4
  2. Restart the App

Actual Result:
See error message.

Expected Result:
Signal continues to work.

Screenshots

signal error

Platform Info

Signal Version: 1.34.4

Operating System: Windows 10 1909

Linked Device Version: 4.66.5

Link to Debug Log

The app does not open.

@scottnonnenberg-signal
Copy link
Contributor

Please provide your full debug log - you can find it at C:\Users\<You>\AppData\Roaming\Signal\logs.

@hwinnemoe
Copy link
Author

hwinnemoe commented Jul 17, 2020

Please provide your full debug log - you can find it at C:\Users\<You>\AppData\Roaming\Signal\logs.

Can I send to you directly?

@scottnonnenberg-signal
Copy link
Contributor

If you would be more comfortable with that, go right ahead.

@hwinnemoe
Copy link
Author

I just did some quick search and replace, here you go:
log_san.log

Thanks for the quick reaction :)

@scottnonnenberg-signal
Copy link
Contributor

Screen Shot 2020-07-17 at 10 03 24 AM

I think you'll need to zip that up.

@hwinnemoe
Copy link
Author

hwinnemoe commented Jul 17, 2020

log_san.zip

You can also just press the up arrow and press keep. Also, this is a second machine, I could have just reinstalled the app but I wanted to file the issue since there might be more users who have that issue.

@scottnonnenberg-signal
Copy link
Contributor

No hints in the log, unfortunately. I'd recommend two things:

  • First, you might go into C:\Users\<You>\AppData\Local\Programs\Signal to see if you can find the file it's not able to access on disk
  • Second, you can try reinstalling from https://signal.org/download to see if it fixes things. Reinstalling on top of an existing install will preserve all of your data (uninstall will remove it, though).

@hwinnemoe
Copy link
Author

hwinnemoe commented Jul 18, 2020

* First, you might go into `C:\Users\<You>\AppData\Local\Programs\Signal` to see if you can find the file it's not able to access on disk

I managed to extract the app.asar file and the node_sqlite3.node file is in there and extracted fine. The paths to node_sqlite3.node say that this is Electron v8.2. It should be v8.3.4, shouldn't it? I can upload it or look for anything else if it's of any help for you.

* Second, you can try reinstalling from https://signal.org/download to see if it fixes things. Reinstalling on top of an existing install will preserve all of your data (uninstall will remove it, though).

Thanks, I will do this when you tell me that there is nothing left for me to investigate.

@awforsythe
Copy link

I had the same issue; re-running the latest Windows installer fixed it for me.

@hwinnemoe
Copy link
Author

I had the same issue; re-running the latest Windows installer fixed it for me.

I installed 1.34.4 and it now starts and works fine. I preserved the previous app.asar file if it is of any interest for further investigation.

@hwinnemoe
Copy link
Author

Closing this as resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants