http://bugzilla.opensuse.org/show_bug.cgi?id=1190288 http://bugzilla.opensuse.org/show_bug.cgi?id=1190288#c14 --- Comment #14 from Yifan Jiang <yfjiang@suse.com> --- (In reply to Max Lin from comment #12)
(In reply to Dominique Leuenberger from comment #8)
Nov 24 06:22:30.133424 localhost.localdomain org.opensuse.opensuse_welcome.desktop[1967]: /usr/bin/opensuse-welcome: symbol lookup error: /usr/lib64/libQt5WebEngineCore.so.5: undefined symbol: hb_subset_input_set_drop_hints
Who updated to harfbuzz 3.0??
Hi All,
I did a snapshot review again today then I realized this is an _different_ issue now after updated to hardbuzz 3.0, the origin report here is about opensuse-welcome fails to work on GNOME's overview mode *only*, it still worked on other desktop eg. KDE, see https://openqa.opensuse.org/tests/1953048#step/first_boot/1
Just some information may be duplicated with the previous findings: I had similar thoughts that they were different issues in lunch time, so I did try a bit on the latest TW snapshot 20211122, which uses the sane Harfbuzz 2.9.x as well as core gnome 41 stack. But I can not see the problem (Overview mode) with either Xorg or Wayland sessions in both automatic log-in and manual log-in paths. Meanwhile, there are still pretty much difference between TW and SLE 15 SP4's about GNOME stack, though many submissions are on the way of staging (see: https://build.suse.de/project/users/SUSE:SLE-15-SP4:GA:Staging:E). It is worthy of standing by a bit for these fixes' merge and see if the problem getting better.
For the reference regarding qtwebengine, I've had a discussion with Antonio about new harfbuzz(actually plus new icu), we need to update qtwebengine to SLE15 SP4, https://bugzilla.opensuse.org/show_bug.cgi?id=1192880 and https://jira.suse.com/browse/PM-3173
@Max, just to ensure I understood correctly, am I right the rebuild qtwebengine will happen on internal build service (build.suse.de) as well - maybe by forking the package on sle15sp4? (https://bugzilla.opensuse.org/show_bug.cgi?id=1192880) -- You are receiving this mail because: You are on the CC list for the bug.