-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bad file descriptor error with Chrome/Edge 92 dev releases #12
Comments
CC @TheEvilSkeleton as this probably will affect com.microsoft.Edge. |
@tinywrkb please try the latest commit and see if it works, if so I'll cut a new release soon(-ish) so we can start getting ready for 92's release. |
@refi64 thanks, it's now working perfectly with the latest Chrome Unstable and Edge Dev releases. |
tinywrkb
added a commit
to tinywrkb/com.microsoft.Edge
that referenced
this issue
Jun 9, 2021
Fixes startup issue with 92.0.902.9-1, see refi64/zypak#12.
vladimiry
added a commit
to flathub/com.github.vladimiry.ElectronMail
that referenced
this issue
Jul 8, 2021
* Resolves the "Failed to send spawn request to supervisor: Bad file descriptor (errno 9)" error, see refi64/zypak#12 for details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zyapk v2021.02, Edge Dev 92.0.902.2, Chrome Unstable 92.0.4515.40.
Edge and Chrome are failing to start with the following errors:
Debug output for Chrome: chrome-unstable-strace.log
I'm using my own Flatpak packaging for Chrome Unstable and Edge Dev but I'm not doing something special so I expect that the Flathub packaged Chrome stable and Edge beta apps will also break when updated to 92.
Chrome Unstable 92.0.4496.0 and Edge Dev 92.0.891.1 didn't suffer from this issue.
The text was updated successfully, but these errors were encountered: