Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-97382

qt.conf not reladed properly after QCoreApplication::instance()

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P2: Important
    • 6.2.2, 6.3.0 Alpha
    • 6.2.0
    • WebEngine
    • None
    • Windows
    • e6db4206b81f3fcea13646461f56a5207d9608c2 (qt/qtbase/dev) 4a31673d0714f1b76b12dc502365daee4bfe3171 (qt/qtbase/6.2)

    Description

      if QLibraryInfo:path function is used BEFORE QCoreApplication::instance() is initialized,

      when you call QLibraryInfo:path AFTER QCoreApplication::instance() is inittialized,

      QLibrarySettings is not reloaded.

      So, qt.conf pathes are not taken into account

       

      reloadOnQAppAvailable variable is true, but havePaths function never test it.

       

      This was working with Qt5

      Attachments

        1. callstack.png
          49 kB
          Alban Pellet
        2. image-2021-10-11-14-26-00-398.png
          17 kB
          Alban Pellet
        3. image-2021-10-11-14-33-57-195.png
          36 kB
          Alban Pellet
        4. image-2021-10-11-14-34-22-693.png
          4 kB
          Alban Pellet

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-97383 [REG 5.15 -> 6.2] QtWebEngineProcess + change resources location with qt.conf

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-97947 [REG 5.15 -> 6.2] QtWebEngine resources + translations location no longer affected by qt.conf

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Activity

            People

              michal Michal Klocek
              alban_go2 Alban Pellet
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: