GNOME Bugzilla – Bug 790811
yelp crashes in recent Fedora Rawhide when 'welcome tour' should be displayed
Last modified: 2018-03-02 17:52:15 UTC
At some point since Fedora-Rawhide-20171106.n.0 - the last time this worked - a bug has appeared in GNOME which prevents the 'welcome tour' showing up on first boot / first login, as it should. Instead, yelp crashes. I'll attach the best traceback I've been able to get (Fedora doesn't seem to be able to find *all* the relevant debuginfo packages). The crash can easily be reproduced on an affected install by simply running `/usr/libexec/gnome-welcome-tour` or just `yelp help:gnome-help/getting-started`. To reproduce, just boot a recent Fedora Rawhide Workstation live image - e.g. https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20171124.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-Rawhide-20171124.n.0.iso - install it (actually, it may be possible to reproduce from the live environment), reboot, and on first login, note you get a crash notification instead of the 'welcome tour'. Then use either of the above commands to reproduce at will. I can't pinpoint *precisely* when this appeared, as there were some Rawhide bugs in the relevant time period which broke install entirely for a short time. But it was between Fedora-Rawhide-20171106.n.0 (which worked) and Fedora-Rawhide-20171114.n.0 (which ran into this issue). The composes between those two all hit other failures before they would have run into this issue.
Created attachment 364368 [details] backtrace
Just running plain 'yelp' results in a crash, also.
Ping? This has been sitting around a while, and it's quite significant...
So after some debugging in #fedora-desktop today we decided this is https://bugzilla.redhat.com/show_bug.cgi?id=1518674 , and it's dependent on graphics hardware to some extent (it happens in VMs, does not happen on bare metal, anyhow).
We have now the same error on Leap15 / SLE15 beta, when using Wayland exclusively and QXL / Virtio, with evolution. The bug is probably in webkit2gtk3 (or Mesa), not yelp.
bug fixed in upstream webkit2gtk3: https://trac.webkit.org/changeset/228272/webkit https://bugs.webkit.org/show_bug.cgi?id=182490
Thanks Fred!