I want to use the dark cosmic theme with kweather from flatpak. I’ve tried lots of stuff, but I don’t understand how to determine what is a valid theme from terminal, or how to add to use it with a flatpak.

  • 3H3x36tBElshOaOPEnglish
    3·
    2 months ago

    I finally looked at the source for kweather, and saw

        if (qEnvironmentVariableIsEmpty("QT_QPA_PLATFORMTHEME")) {
        qputenv("QT_QPA_PLATFORMTHEME", "kde");
    }

    I tried

    export QT_QPA_PLATFORMTHEME=qt6ct

    After installing qt6ct and configuring it. It didn’t work. I don’t really think this is going to be easily resolvable if it’s possible. The app looks mostly good, so I’m just not going to worry about it.

    • 3H3x36tBElshOaOPEnglish
      1·
      2 months ago

      The QT theme can be set under cosmic. I think it’s some kind of issue with using qt6ct with flatpak. If I install qbittorrent through apt install qbittorrent then add

      alias qbittorrent="export QT_QPA_PLATFORMTHEME=qt6ct; /usr/bin/qbittorrent"

      To my ~/.bashrc file, then I can launch qbittorrent with the settings from qt6ct when using qbittorrent from cosmic-term.

      This doesn’t change qbittorrent in the applications launcher. I think that requires changing the .desktop file. I haven’t been able to determine how to launch qbittorrent with qt6ct with the version from flatpak yet.

      edit: If this fails, it’s usually because qbittorrent was already running. I’m able to have it work consistently by opening the “System Monitor” and killing all processes under qbittorrent then laucnhing it from cosmic-term.

      edit: I found out later that editing ~/.profile with exports is more frequently recommended. I haven’t tested it, but I just used the discouraged system wide /etc/environment file. This works for the other shortcut like ways to open files. The reason I used the /etc/environment was because I didn’t really care, and also wanted to fix the mouse and resolution issues I was having that I found very annoying.

      export XCURSOR_SIZE=24
export QT_SCALE_FACTOR=1
export QT_QPA_PLATFORMTHEME=qt6ct

      I guess I might end facing consequences for it sometime? I don’t know, I think the worse I’m expecting is that it just applies automatically to new users, but I guess I’ll find out…

        • 3H3x36tBElshOaOPEnglish
          1·
          2 months ago

          I finally managed to theme the org.kde.kweather flatpak, but I didn’t use qt6ct.

          I just ended up doing

          sudo apt install plasma-desktop

          Then opening KDE Settings, changing the theme to Breeze Dark and then

          sudo apt remove plasma-desktop
sudo apt autoremove

          I think these steps should also work for other applications that were originally made for KDE, but I’m new to using Desktop Linux as a primary DE. I don’t really know if there are any consequences for doing this, but it seemed to work…

          I think org.kde.kweather uses abnormal theming intended for KDE. I did a bunch of testing, I went back to older versions of it from months ago. I finally found a version that was compatible with Kvantum, and installed a package that makes Kvantum work with qt6ct.

          The kvantum theme was mostly broken with org.kde.kweather in the older verison. And, then I found out that KDE applications read from ~/.config/kdeglobals, so I found a sample version and confirmed that I could in fact change the theme by creating the file. After this, I realized just using KDE to change the theme was probably going to be the easiest way forward, and that’s how I ended up at the above solution.

          • 3H3x36tBElshOaOPEnglish
            1·
            2 months ago

            I forgot to say, it’s also possible to use Kvantum with KDE applications that are flatpaks.

            I just had to set the theme to Kvantum in the KDE Settings. I also noticed that the theme works slightly better if the platform theme on KDE applications is exported as QT_QPA_PLATFORMTHEME=kde, though it’s not necessary. One other note, QT works by using plugins. I think the export is specifying the installed plugin. That was confusing to me, I was searching for config files but it’s a plugin to QT.

            edit: When opening the KDE settings, I think I also had to change the export to QT_QPA_PLATFORM=kde temporarily so that KDE recognized that it was supposed to change configuration files on the filesystem. Otherwise, I think it expects that qt6ct is managing it, and it shouldn’t do anything. (because qt6ct was likely set earlier in in either the /etc/environment or in the ~/.profile)

            I don’t remember it was a requirement or not. Just that I had to change it so that KDE Settings would use the theme when I opened it.