demm
It's different from previous, it's working, but does not stop loading, right now as well, the page is loaded but indicator didn't stop.

  • demm replied to this.

      bvbfan but does not stop loading, right now as well, the page is loaded but indicator didn't stop.

      What does not load? What indicator?

        In Falkon. But i see a problem, Qt5WebEngineCoreConfig.cmake wants a Qt5Quick 5.15.3 and i cannot build Qt application now. Probably it's better to get only commits with CVE's ? Or you can edit the cmake to be 5.15.2

        • demm replied to this.

          bvbfan only commits with CVE's

          Those are from Chromium 87, released QtWebengine uses 80, and needs all kinds of patches to build with that new version.
          If Falkon does not work properly anymore, then this is a no go, Falkon is default, so version of webengine has to work with Falkon first.
          5.15.3 will be removed from the build repo.

            Read my reply, this is not about fixing builds, this is about qtwebengine losing functionality (if you need those lines, no need to wait for an update, you can edit that yourself now too).

            I don't think it looses functionality or at least i can't notice it. Only issue is that, page is loaded but indicator shows it does not in Falkon (notice circle in tab at its left)

              bvbfan

              You can please give an example of such a page? I don't have problem with indicator on 5.15.3-1

                  Any Kmail users? Please test with qtwebengine 5.15.3 too.

                  Haven't found any problems with qtwebengine 5.13.3 with Kmail or any other programs yet.

                    Will be good if can update only Chromium to 87 without touching Qt changes. That will be something like get git till last Qt 5.15.2 commit submodules to 87, if it can compile of course.

                    nezzie That post should have said 5.15.3. Still no problems have appeared. Kmail is definitely working OK.

                        nezzie
                        KMail is tricky to be tested, you should update to new QtWebEngine then you should logout or reboot then test.

                          #bvbfan.
                          I've done both a couple of times. System is fully updated, Using 5.15.3 from build repo, rebooted twice so far.
                          Tried Kmail, Kontact, Kmymoney, Falkon, akonadi-contacts, akregator and no noticeable problems. Will try digikam later.
                          Edit: Marble and Digikam appear to be working OK. emailed photos direct from digikam through kmail.

                          Edit.2. Not working on another PC updated and including a full update from build repo.

                          On my older test PC using the Build Repo. These outputs are not on normal PC.(no Build repo)
                          Running the following from the CL gives these outputs. Kontact and Kmail appear to work OK.
                          Maybe they are acceptable.

                          kontact
                          Found no modules in speech-dispatcher. No text to speech possible.
                          Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls")
                          kf.xmlgui: 0x1be06d0 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.
                          FolderCollectionMonitor::FolderCollectionMonitor() MailCommon::FolderCollectionMonitor(0x1c32c40)
                          kf.xmlgui: 0x1bc1d28 deleted without having been removed from the factory first. This will leak standalone popupmenus and could lead to crashes.

                          kmail
                          Found no modules in speech-dispatcher. No text to speech possible.
                          Cannot initialize model with data QJsonObject() . missing: QJsonValue(string, "urls")
                          [96694:96700:0312/203632.825760:ERROR:command_buffer_proxy_impl.cc(141)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
                          FolderCollectionMonitor::FolderCollectionMonitor() MailCommon::FolderCollectionMonitor(0x1925c60)