-
Notifications
You must be signed in to change notification settings - Fork 795
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
Exit after 10 seconds. "ERROR:gbm_wrapper.cc(72)] Failed to get fd for plane." #2842
Comments
We found a workaround fix for the second challenge Steps:
|
@rany2 Could you reproduce this issue? |
Is that error at all harmful? Does the browser function properly despite it?
At least from the looks of it, it seems like a corrupted Chromium config/cache issue? --delete-data is equivalent to just wiping I'll investigate further to see if I could try to trigger but I probably can't this week. |
I both updated and simplified these steps to reproduce above The most important updated step is that this challenge can only be reproduced after updating UC We were able to reproduce this challenge on a total of 4 different ungoogled-chromium (UC). Including 2 freshly installed (vanilla) UC. On 2 different devices. |
This issue has been automatically marked as stale as there has been no recent activity in response to our request for more information. Please respond so that we can proceed with this issue. |
OS/Platform
Debian, Ubuntu, and derivatives
Installed
Flatpak
Version
Version 124.0.6367.118 (Official Build, ungoogled-chromium) (64 bits)
Have you tested that this is not an upstream issue or an issue with your configuration?
--user-data-dir
command line argument and it could not be reproduced thereDescription
Start with Terminal displays: ERROR:gbm_wrapper.cc(72)] Failed to get fd for plane.
How to Reproduce?
Install Ungoogle-Chromium (UC) version 124.0.6367.201-1 from https://flathub.org/apps/details/com.github.Eloston.UngoogledChromium
Notes:
UC works fine. No challenge.
Install this Mesa OpenCL
sudo aptitude install "mesa-opencl-icd"
Wait for the next release of UC. Update UC to the new release 124.0.6367.207-1. This steps is the most important one. Because without an update, this challenge can not be reproduce.
Notes:
Using GNOME, start UC. It does open. It is important to start UC with GNOME. Otherwise this challenge can not be reproduce with starting UC from Terminal.
After roughly 10 seconds, UC exit. This is the challenge.
Notes:
After UC exit above. There is an unusual process still open.
wrap
. Which never exit and uses memory. Each time you repeat the steps above. At this present step, an additionalwrap
process is added and remains open. And so on.The same challenge can be reproduce many previous releases of UC. Maybe a few weeks back.
Actual behaviour
Find steps to reproduce above
Expected behaviour
Ungoogle-Chromium (UC) starts without error message and does not automatically exit after 10 seconds
Relevant log output
Find steps to reproduce above
Per the steps above, if you start UC from Terminal, this challenge can not be reproduce. But if somehow the Terminal log is useful for your discovery, here is it below.
Using Terminal, start UC
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=/app/bin/chromium --file-forwarding io.github.ungoogled_software.ungoogled_chromium @@u %U @@
Terminal display those errors. This is the first challenge.
Additional context
Debian 10 Bookworm
GNOME 43.9
Wayland
What we tried but did not work
Temporarily deactivate graphic acceleration at
chrome://settings/system
Remove Ungoogled-Chromium (UC). But keep its configuration. Then reinstall UC.
flatpak remove io.github.ungoogled_software.ungoogled_chromium
flatpak install flathub io.github.ungoogled_software.ungoogled_chromium
IDU
@Francewhoa :) Note to myself IDU_7B9EF9S3
The text was updated successfully, but these errors were encountered: