-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Crash: "EPERM: operation not permitted)" #3106
Comments
I got the same error when the SignalBeta/1.21.0-beta.4 update arrived. Note that the Signal Desktop Beta was running for a few hours already without an update prompt. My stable Signal Desktop got the update immediately after start up.
debug log: after restart/update to SignalBeta/1.21.0-beta.4: |
Did this happen repeatedly, or just once? Have you been able to update to |
I've since updated to -beta.4 and now see a different error. I'll close this and reopen if i see it again. |
This happened to me immediately before updating to the latest beta.
Immediately after starting Signal after the crash, I received a "A new version of Signal is available" message so if I had to guess, this is an issue with the updater. This has never happened before. Will report back if it happens again with the latest beta. Edit: I'm currently using beta 4, so the update itself doesn't seem to be an issue. |
I get this crash since today with this log:
Platform InfoSignal Version: v1.21.1 |
@scottnonnenberg-signal Hey there, I commented a few days ago regarding this same error (I had to make a new account just now) about MacOS (Sierra 10.12.6) showing the "Unhandled Promise Rejection" error on the previous version. I am running Signal V1.21.1 now and the error is still popping up unfortunately. The update worked for a few days but it has returned. I can open up a new bug report here on GitHub if this isn't the right place to comment and/or I can share the text that the error message pops up. Thanks. |
@rocketleaguefan1 What's the line right below the 'unhandled promise rejection?" That's the real error message. |
@scottnonnenberg-signal It says: I went to the GitHub website it mentions there at the bottom and I wasn't sure what to do. Someone mentioned removing "Atom" but I don't think I have that downloaded. Please forgive my ignorance in these matters since I know very little about this field. Thank you. |
@rocketleaguefan1 You get that error because macOS has Signal in a read-only quarantine zone. You need to move Signal.app, with Finder, to |
Just happend to my girlfriend at work:
debug log: https://debuglogs.org/2c76d9c22936115967c67ff2a2f0fa070ac1e474a33e802a65fa606a400c5426 |
Yep, in v1.22.0 we downgraded our install/update infrastructure, which should prevent these errors for all updates after v1.22.0 or v1.22.0-beta.2. There's always a delay, since the new, fixed infrastructure has to be in charge of the new version download. |
Experienced the same error today. I was on no beta branch. Screenshotsan error box with the error text "Error: EPERM: operation not permitted ..." appeared, exiting the error box terminated signal. Platform InfoSignal Version: Operating System: Linked Device Version: Link to Debug Loghttps://debuglogs.org/f0bd968e473f76b3194d4624ccbade799ed2d4aea79cd86c147f6bc4bc3ae823 |
Yep, again we expect this to continue to happen until the upgrade v1.22.0->next, v1.22.0-beta.2->next. |
I am also getting the same error after updating Signal. |
@TYeniyayla could you send us a debug log, please? |
Ok, I solved the problem. Now let me tell you how. I'm using Signal on my PC at work. I am not the administrator on this pc and every program is installed, admin permission is required. Signal is one of the rare programs installed without admin permission and I have been using it for a long time. After I did the last update, I started getting an error (error: Signal nhandled Promise Rejection Error: EPERM: operation not permitted, unlink 'C:\Users\ahmet.yeniyayla\AppData\Roaming\Signal\logs\app.log.3') and it was asking for admin permission to read the log files. That's why I couldn't share the log files here and tried to reach the system administrator. I just arrived today. We tried to read the log files together, but even though it gave me permission for the log files, the file was giving me an access block error, it wouldn't open. Meanwhile, I restarted the computer and signal worked, the log files were opened without any problems. We don't have the slightest clue why it happened, but somehow the problem was solved. Now I am attaching the log files as well. Maybe you have an idea. |
Bug Description
Intermittent crashes after computer sleeps.
Steps to Reproduce
Actual Result:
Signal crashes with the following window:
Expected Result:
Signal continues to work.
Screenshots
Platform Info
Signal Version:
v1.21.0-beta.3
Operating System:
Windows
Linked Device Version:
Link to Debug Log
Header: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) SignalBeta/1.21.0-beta.3 Chrome/66.0.3359.181 Electron/3.0.14 Safari/537.36 node/10.2.0 env/production
The text was updated successfully, but these errors were encountered: