Note that this only updates packages in repositories. You should also ensure foreign packages from the AUR and other locations are also updated. Similarly, if you have replaced an official package with an unsupported variant, try to reproduce the problem with the official package before creating a topic.)
Ha, true. TBH, I don't know why I didn't remember that there was such a thing as qt5-styleplugins, probably because I use mostly Gnome and a lot of Gtk apps or whatever they are, so I guess Opensnitch-Ui needing qt5-styleplugins to be rebuilt didn't occur to me because I forgot that I had installed the package to make qt5ct use the gtk3 theme or whatever... a pretty random implementation detail. If pressed I would probably have recalled about qt5ct and having to set an env var but not that it was a separate AUR package since i don't use plasma or KDE.
How would we fix that? I don't know, I have rebuild-detector installed but it didn't do anything in this case, although it does tell me when firefox-nightly or obs-studio-git need to be rebuilt. I guess this incompatible qt error message could maybe tell me it was coming from qt5styleplugins or whichever qt program that package installs. Either way, yeah it's kind of user error but it's also a flaw in the usability of implementation of qt packages.
even this is solved I would like to hang myself on that topic as I have the same error message without a AUR package in use. For me same error message appears for xca which is in community repo. Could that anyhow be related? The filed bug was closed due to belief in incompatible qt style. See
Cleanbuilding qt5-styleplugins also worked for me, like frabjous already posted. I haven't tried it the following way (but without --rebuild, see linked thread), but in the comments in AUR it is described this way:
Based on that, I would look at /usr/lib/qt/plugins/sqldrivers/qsqlcipher.so, which is from kmymoney. If you uninstall that, does xca work again? Alternatively, you could rebuild the kmymoney package and see if that works instead of removing it.
I use a tool called oomox to generate GTK themes. After I generate the new theme, I would like to run a command that makes all currently open GTK applications use said new theme. I'm pretty sure desktop environments like GNOME have this functionality but I'm using a window manager. Is there any command, utility, or method of telling all currently open GTK applications to "refresh" their theme? I use some Qt applications and they use my GTK theme via qt5-styleplugins. I would also like to make these applications refresh to use the new theme.
To be clear, any applications I open after generating the theme already use it; I make the name the same and it replaces the old one. I would like a way specifically to update already open applications. Finally I would heavily prefer if I could do this from the command line but any solutions are appreciated.
Hey there,
I'm facing some trouble with a few Qt programs (bauh, Raven Reader): When I try to launch them, they crash with the error Cannot mix incompatible Qt library x with this library y If e.g. x is 5.15.3 and y is 5.15.4, the crash is understandable, though if I then downgrade qt5-base to 5.15.3 the error now shows x being 5.15.4 and y being 5.15.3 - HUH? Like what?
Can someone explain this to me?
Thanks!
I did read that forum post a while ago. The dumb part is, that garuda-update forces me to install stuff that inevitably breaks my system, but updating without it also does the same thing, apparently.
I solved the dependency problem with pacman -Sdd sweet-theme-full-git (all the garuda tools apart from the assistant are broken on wayfire anyways. Cool stuf, but hella useless like this) to avoid garuda update. That worked, but apparently garuda-update is required for the new grub-silent (Why tho, I want to see grub, I need it for backups) package to install properly...
However, but I'm just wondering if the original reason for that "incompatible Qt library" error message was something much simpler, in view of the fact that you appear from your posts to favour ignoring some upgrades.
Originally I thought it had something to do with qmplay2 being built on a newer qt5 base and maybe Manjaro Stable was still on an older qt version in between its 3-weekly updates (since I had no problems in Artix or Anarchy), but checking all the dependencies showed it was not the case. Once I realised that Manjaro Settings Manager (native to Manjaro) was also affected, I knew that could not be the reason.
Turns out the simple cause of it was that qt5-styleplugins [used in my old Manjaro install to theme/set the environment for qt apps] was no longer maintained by Arch/Manjaro and had been pushed to AUR, and Manjaro was theming Qt apps on their gtk desktops a different way going forward. I had been too lazy to update it from AUR or remove it, since I mistakenly thought it was no longer needed and not in use.
So the question is: Are you ignoring the update of some package, AUR or otherwise (how about from the artix repo you enabled)? Do you perhaps have a setup where theming of Qt apps is based on an older qt base?
3a8082e126