Added comment to remind how to upgrade in case of system qt bumpHEADmaster

1 files changed, 15 insertions, 0 deletions

diff --git a/llamachat/__main__.py b/llamachat/__main__.py
index c051939..0df65a1 100644
--- a/llamachat/__main__.py
+++ b/llamachat/__main__.py
@@ -126,6 +126,21 @@ def _use_system_qt_theme() -> None:
     Fusion. Adding the system plugin directory fixes that, but only when
     the two Qt builds are the same version: loading a plugin built against
     a different Qt would crash rather than look wrong.
+
+    So a system Qt patch bump silently unthemes the app until the venv is
+    updated to match: the versions differ, this returns early, and the
+    window comes up in Fusion with no error anywhere. The fix is to match
+    them again, not to loosen the check or to set QT_PLUGIN_PATH by hand.
+    Both of those crash instead:
+
+        ~/.local/share/llamachat-venv/bin/pip install -U PySide6
+
+    QT_PLUGIN_PATH replaces the plugin search path rather than adding to
+    it, so pointing it at the system directory also hides PySide6's own
+    platform plugins and Qt exits with "no Qt platform plugin could be
+    initialized".
+
+    A distro-packaged PySide6 instead of a venv one would end the cycle.
     """
     if os.environ.get("QT_PLUGIN_PATH"):
         return  # the user has already chosen; do not override