-
-
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
Application fails to start after recent update. #6797
Comments
How far along into startup does it get? Do you see a window pop up in a loading state forever? Could you follow the instructions here to get a debuglog directly from disk: https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports |
Here are the 2 log files. |
I am experiencing the same GPU-related coredump failure on startup after my recent update. Please see my log files attached: |
Unfortunately, your logs don't seem to help, since the crash looks like it is happening before our logging system starts up. What happens if you try starting with |
Same thing unfortunately:
|
It appears that Signal Desktop can't use your graphics hardware. What happens if you try to run Chrome, Chromium, or maybe even https://www.electronjs.org/fiddle? Or maybe other Electron-based apps like Slack or Discord? |
I don't have chrome/chromium installed, but I was able to launch that fiddle app, and my discord app also runs without issue. |
@egro Ah, interesting. Thanks for that investigation. The next thing you could try is to use the fiddle app to pull down and run various versions of Electron to see which versions work and which don't. |
I ran the 'hello world' program in a dozen or so versions, from 27 through 30(beta2). Every time it terminated with this:
I was also able to install chromium (apt install chromium-browser) and it launches. |
@egro So it sounds like no recent versions of Electron work for you. What was the last version of Signal Desktop that worked for you? What if you try starting up with |
I think .46 might have been the last version that worked for me. This is what I see what I run with the requested '--disable-gpu-sandbox' switch:
|
@egro Well, here's to hoping that a future update to Electron will play nice with your graphics hardware. Electron is always a little behind chromium! |
Hi - something that I don't understand, is that I can launch Why would |
@DawidLoubser Specific electron versions could be at fault, since we're on Electron 29. But I did find another workaround you could try: start the app with these command-line arguments: |
@scottnonnenberg-signal Thanks for the continued help! Unfortunately no luck with those args either:
|
I also had no luck running those args. My error seems to be different from that of DawidLoubser
|
Update. My discord updated and has also stopped working. :| Same errors about GPU. [215674:0404/110525.772242:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=134 I didn't see any related open issues on the electron bug tracker. |
Hello! We have updated quite a few things. Could you give it another try to be sure? Thanks! |
It might be particularly interesting to try the latest nightly version of Electron in the fiddle to see if it has gotten any better. |
Still failing the same way.
These are the ElectronFiddle results I get with the 31.alpha build (the most recent I see in the interface)
|
I am also still having this problem on the latest signal-desktop
EDIT: Chromium still requires special flags to run natively under wayland. But using the x11 backend and also supplying those flags both work. My understanding is that signal-desktop is still forcing x11 for now. I don't think this is related but just wanted to mention it. EDIT2: I resolved it by deleting some cache directories and files per #6735 (comment) |
Oh, very interesting. Looks like the shader cache might have went bad. Thank you so much for sharing! |
Why has my ticket been closed? I'm still getting the error(s) and signal-desktop won't start. [70461:0423/145052.633413:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=134 |
@egro could you try a suggestion from #6735 (comment) ? |
I did the things in that ticket, it still doesn't launch. Fails with the same errors. I've go so far as to uninstall/delete everything and reinstall - it still fails. |
@indutny-signal Thanks! I removed those files/directories and now Signal runs again! @egro Did you delete, in
? |
Yes, I did. Also, I upgraded to 7.6.0 today, still not seeing a change.
Even deleted those files/folders after upgrading. Tried running Fiddle again, with 31.0.0A2, it still fails with the same message:
|
@egro Your logs have a different exit code than mine I just noticed. And it's also different from the original logs you posted. I'm not sure what that exit code means unfortunately, just wanted to point it out in case it was missed. Might just be the same issue with slightly different error handling in electron. Also sorry it didn't work for you, was really hoping it was as simple as it seemed. |
I found this in another issue ticket. Tried it but it didn't resolve my issue: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I still have the issue and I'm still investigating. Similar to: |
This issue has been closed due to inactivity. |
This is still an issue. |
I flattened the box and reinstalled the OS from scratch (24.04 LTS this
time, vs 22.04).
It seems to be working at this time. Sucks that I had to reinstall the OS
to get it to work. :|
…On Fri, Sep 13, 2024 at 11:58 AM Jamie Kyle ***@***.***> wrote:
Reopened #6797 <#6797>.
—
Reply to this email directly, view it on GitHub
<#6797 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKFUHZTKNWJJ3HOLZ7KCXLZWMKR3AVCNFSM6AAAAABDSHBV3OVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGI2TCNZWHEZTAMI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Same here. Deleteing the cache files did not resolve it, but simply reinstalling signal did the trick. |
Using a supported version?
Overall summary
Signal desktop fails to launch. GUI presents no error.
Running from command line give a error about the GPU process terminating unexpectedly.
Steps to reproduce
Click the icon.
Expected result
Application launches
Actual result
Running signal-desktop from command line returns a LOT of results, but terminates with these lines:
This failure started after a recent update to my system. I have other systems where I have not updated those continue to work as expected.
AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx (Minisforum UM350)
Ubuntu 22.04 LTS
Here is a complete list of packages that were updated at that time:
I have applied 6.48.0, which also fails.
Screenshots
No response
Signal version
6.47.1 6.48
Operating system
Ubuntu 22.04.4 LTS
Version of Signal on your phone
6.46.7
Link to debug log
No response
The text was updated successfully, but these errors were encountered: