Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2118832
| Summary: | anaconda help shows up blank on live images since Fedora-37-20220814.n.0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
| Component: | anaconda | Assignee: | Vladimír Slávik <vslavik> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 37 | CC: | amigadave, anaconda-maint-list, caillon+fedoraproject, gnome-sig, jhorak, jonathan, kellin, kparal, lruzicka, mcatanza, mclasen, rhughes, robatino, rstrode, sandmann, stransky, tpopela, vanmeeuwen+fedora, vponcova, vslavik, w |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | AcceptedBlocker openqa AcceptedFreezeException | ||
| Fixed In Version: | anaconda-37.12.2-1.fc37 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-02 22:27:42 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2009538, 2009539 | ||
|
Description
Adam Williamson
2022-08-16 22:11:14 UTC
Confirmed with Fedora-Workstation-Live-x86_64-37-20220814.n.0.iso On Silverblue Rawhide (20220816), this is also happening to all tested applications in openQA, see https://openqa.stg.fedoraproject.org/tests/1972844#step/help/2 https://openqa.stg.fedoraproject.org/tests/1972840#step/help/3 https://openqa.stg.fedoraproject.org/tests/1972842#step/show_help/2 The similar Silverblue problem has existed for longer, so I'm not sure it's the same problem. That one is reported at https://github.com/fedora-silverblue/issue-tracker/issues/305 . Hmmmm. It's a little hard to decide what to do with this ticket. On the one hand, running GTK apps as root is not a good idea and not something we'd ordinarily spend time investigating. On the other hand, this is how anaconda has always worked, and that's hardly simple to change. But running WebKitGTK as root is super not a good idea, and that's probably where we can draw a clear red line. Don't run web engines as root, right? This will probably break in other ways in the future, e.g. when the sandbox becomes mandatory it will probably crash when trying to use bwrap. And if not, we should probably add an explicit check to crash if run as root. So anaconda really needs to not do this. All that said, none of that changes the fact that it shouldn't crash in this particular way with an X11 error. There's no way to pretend that is not a bug. If you get a backtrace with GDK_SYNCHRONIZE, then we can report a bug upstream. That said, X11-specific issues are already low priority, and issues that occur only when run as root are probably lowest imaginable priority, so "don't do that" is probably a safe path forward here. We could assign this to WebKitGTK to fix the crash, but it's probably more helpful to move this to anaconda to figure out how to avoid running yelp as root, so let's do that. +5 in https://pagure.io/fedora-qa/blocker-review/issue/855 , marking accepted. Wait, wait <record skip> - are you saying we're on *X.org* here? We *shouldn't* be. The default is Wayland and openQA should use the default. We aren't explicitly testing X.org or something. I wonder if that's why this "suddenly broke"? Are live images hitting the X.org fallback path? I'll have to look into it. Yes, you can see it died to an X window system error. (To investigate it, we'd need a backtrace with GDK_SYNCHRONIZE=1, like the error message says.) I never remember if we get those errors only when running on an actual X server, or if we also get them for XWayland. Anyhow, I'll look into it. Both! These errors can come from XWayland because XWayland is an X server. Okay. BTW, the problem with telling anaconda "don't do that" is that it will probably get dumped in anaconda's "we're rewriting the UI anyway" bucket, i.e. they're not going to want to put a lot of effort into changing how the current UI works, so if "don't do that" turns out to involve major surgery, it may not happen. I'll try and get a better backtrace soon. (This would actually be a good thing to keep in mind when rewriting the anaconda UI. The cockpit process must NOT run as root, or it will break in the future at a maximally-inconvenient time.) Sigh. Fun thing: testing this again right now, I can sure reproduce it from within anaconda, but not running the same command at a console, with or without GDK_SYNCHRONIZE , it works fine. :| Fix PR: https://github.com/rhinstaller/anaconda/pull/4302 It's a shame running yelp under "games" did not work, that account seems to be everywhere. Also proposing as a Beta FE, obviously it would be good to fix this for Beta. +3 Beta FE in https://pagure.io/fedora-qa/blocker-review/issue/855 , marking accepted. FEDORA-2022-6d44eb9c78 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-6d44eb9c78 FEDORA-2022-6d44eb9c78 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-6d44eb9c78` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6d44eb9c78 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. Fix confirmed here, if someone else can karma the update that'd be great. FEDORA-2022-6d44eb9c78 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. Still seems to be a problem on KDE :| I'll look into it and probably file a new bug. We're now seeing something similar for traditional installer images with mutter 43.1 - https://bugzilla.redhat.com/show_bug.cgi?id=2141124 . |