Fix earlyinit with no Qt available
We need to wait with init_qtlog until after we know we have Qt available.
Closes #8220
(cherry picked from commit 1e1af23d34)
This commit is contained in:
parent
a8a84b81d1
commit
a6736dd0f4
|
|
@ -15,6 +15,16 @@ breaking changes (such as renamed commands) can happen in minor releases.
|
|||
// `Fixed` for any bug fixes.
|
||||
// `Security` to invite users to upgrade in case of vulnerabilities.
|
||||
|
||||
[[v3.2.1]]
|
||||
v3.2.1 (unreleased)
|
||||
-------------------
|
||||
|
||||
Fixed
|
||||
~~~~~
|
||||
|
||||
- When the selected Qt wrapper is unavailable, qutebrowser now again shows a
|
||||
GUI error message instead of only an exception in the terminal.
|
||||
|
||||
[[v3.2.0]]
|
||||
v3.2.0 (2024-06-03)
|
||||
-------------------
|
||||
|
|
|
|||
|
|
@ -337,11 +337,11 @@ def early_init(args):
|
|||
init_faulthandler()
|
||||
# Then we configure the selected Qt wrapper
|
||||
info = machinery.init(args)
|
||||
# Init Qt logging after machinery is initialized
|
||||
init_qtlog(args)
|
||||
# Here we check if QtCore is available, and if not, print a message to the
|
||||
# console or via Tk.
|
||||
check_qt_available(info)
|
||||
# Init Qt logging after machinery is initialized
|
||||
init_qtlog(args)
|
||||
# Now we can be sure QtCore is available, so we can print dialogs on
|
||||
# errors, so people only using the GUI notice them as well.
|
||||
check_libraries()
|
||||
|
|
|
|||
Loading…
Reference in New Issue