Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Problem with Qt after the last update (Cannot mix incompatible Qt library) (Read 3348 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Problem with Qt after the last update (Cannot mix incompatible Qt library)

Hello guys.
I'm having problems with the latest version of Qt 5.15.3, which I seem to install today (I did an upgrade today to update Firefox, for security reasons).
Now  I can't use apps like KeepassXC, which, when I try to start, gives the error:
"Cannot mix incompatible Qt library (5.15.2) with this library (5.15.3)"

This is my pacman.conf:
Code: [Select]
#
# /etc/pacman.conf
#
# See the pacman.conf(5) manpage for option and repository directives

#
# GENERAL OPTIONS
#
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir     = /
#DBPath      = /var/lib/pacman/
#CacheDir    = /var/cache/pacman/pkg/
#LogFile     = /var/log/pacman.log
#GPGDir      = /etc/pacman.d/gnupg/
#HookDir     = /etc/pacman.d/hooks/
HoldPkg     = pacman glibc
#XferCommand = /usr/bin/curl -L -C - -f -o %o %u
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#CleanMethod = KeepInstalled
Architecture = auto

# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg   = ungoogled-chromium
#IgnoreGroup =

#NoUpgrade   =
#NoExtract   =

# Misc options
#UseSyslog
#Color
#NoProgressBar
CheckSpace
#VerbosePkgLists
#ParallelDownloads = 5

# By default, pacman accepts packages signed by keys that its local keyring
# trusts (see pacman-key and its man page), as well as unsigned packages.
SigLevel    = Required DatabaseOptional
LocalFileSigLevel = Optional
#RemoteFileSigLevel = Required

# NOTE: You must run `pacman-key --init` before first using pacman; the local
# keyring can then be populated with the keys of all official Artix Linux
# packagers with `pacman-key --populate artix`.

#
# REPOSITORIES
#   - can be defined here or included from another file
#   - pacman will search repositories in the order defined here
#   - local/custom mirrors can be added here or in separate files
#   - repositories listed first will take precedence when packages
#     have identical names, regardless of version number
#   - URLs will have $repo replaced by the name of the current repo
#   - URLs will have $arch replaced by the name of the architecture
#
# Repository entries are of the format:
#       [repo-name]
#       Server = ServerName
#       Include = IncludePath
#
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
#

# The gremlins repositories are disabled by default. To enable, uncomment the
# repo name header and Include lines. You can add preferred servers immediately
# after the header, and they will be used before the default mirrors.

#[gremlins]
#Include = /etc/pacman.d/mirrorlist

[system]
Include = /etc/pacman.d/mirrorlist

[world]
Include = /etc/pacman.d/mirrorlist

#[galaxy-gremlins]
#Include = /etc/pacman.d/mirrorlist

[galaxy]
Include = /etc/pacman.d/mirrorlist

# If you want to run 32 bit applications on your x86_64 system,
# enable the lib32 repositories as required here.

#[lib32-gremlins]
#Include = /etc/pacman.d/mirrorlist

#[lib32]
#Include = /etc/pacman.d/mirrorlist

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
#Include = /etc/pacman.d/mirrorlist-arch


[extra]
Include = /etc/pacman.d/mirrorlist-arch


#[community-testing]
#Include = /etc/pacman.d/mirrorlist-arch


[community]
Include = /etc/pacman.d/mirrorlist-arch


#[multilib-testing]
#Include = /etc/pacman.d/mirrorlist-arch


[multilib]
Include = /etc/pacman.d/mirrorlist-arch

[home_ungoogled_chromium_Arch]
SigLevel = Required TrustAll
Server = https://download.opensuse.org/repositories/home:/ungoogled_chromium/Arch/$arch

Am I doing anything wrong, or is this a new bug?


Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #2

Fortunately, I can reboot the system normally.
The problem is that some apps that rely on Qt (I'm unable to use KeepassXC), refuse to startup, showing the error that I mention in OP:
"Cannot mix incompatible Qt library (5.15.2) with this library (5.15.3)".
I hope this is some kind of bug that can fix both of our problems ASAP.
Btw, I forgot to add  some data:
Kernel: 5.16.12-artix1-1
DE: Xfce 4.16
Init: runit


Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #3
Kernel: 5.16.12-artix1-1
DE: Xfce 4.16
Init: runit

I using Plasma
i3-3210 / 10GB / VGA Intel HD 2500 / SSD 240GB / Arch Linux / Openbox / Ungoogled-Chromium

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #4

Plasma is heavily dependent on Qt, maybe that's why your system is not starting.
Can you install Xfce and see if your system starts?

Meanwhile, I tested some other packages that depend on Qt and can not start any...

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #5
qt5-base in Artix repo needs to be upgraded to 5.15.3.

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #6
qt-base in Artix repo needs to be upgraded to 5.15.3.

It's so good! But what the case for me? How i can walk around the problem? (https://forum.artixlinux.org/index.php/topic,3780.0.html)
i3-3210 / 10GB / VGA Intel HD 2500 / SSD 240GB / Arch Linux / Openbox / Ungoogled-Chromium

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #7
qt-base in Artix repo needs to be upgraded to 5.15.3.

Hi.
So is not a problem just on my side? It's a package that needs to be upgraded by the Artix's staff, right?
Anyways, I hope this gets fixed ASAP,  because I'm (and probably others) unable to use very important packages (like KeepassXC).
Also, thank you very much for the information.

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #8

I hope too!
i3-3210 / 10GB / VGA Intel HD 2500 / SSD 240GB / Arch Linux / Openbox / Ungoogled-Chromium

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #9
Hi.
So is not a problem just on my side? It's a package that needs to be upgraded by the Artix's staff, right?
Anyways, I hope this gets fixed ASAP,  because I'm (and probably others) unable to use very important packages (like KeepassXC).
Also, thank you very much for the information.

qt5-base needs to be upgraded.

You could either

wait for the update from Artix repo

or,

install it from Arch repo.

Code: [Select]
extra/qt5-base 5.15.3+kde+r133-1

I suggest you wait. It should be updated soon.

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #10
qt5-base needs to be upgraded.

You could either

wait for the update from Artix repo

or,

install it from Arch repo.

Code: [Select]
extra/qt5-base 5.15.3+kde+r133-1

I suggest you wait. It should be updated soon.


But I upgraded to that package (as you can see in my pacman.conf, I have the extra repository enabled).
Meanwhile, I restarted my machine and suddenly it says I don't have free space and the various elements of my system are borked...
This is a nightmare...


Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #12
Qt is in the process of being upgraded. Patience, please.

https://gitea.artixlinux.org/artixlinux/packages-qt5/commits/branch/master
and so on. There has been a massive upgrade of all Qt-related packages.

I understand that, but I would suggest to publish a PSA in the news section about this kind situations in the future, to avoid these problems (I always read the news section in the main Artix page, before upgrading).
Will all Qt-related packages be fully upgraded and ready for user upgrade today?
Anyway, thank you very much for your help.


 

Re: Problem with Qt after the last update (Cannot mix incompatible Qt library)

Reply #14
It usually takes one to two hours after the package has been built for it to be propagated to mirrors.
8) my lxqt session fails to start for about a day (since last night's lucky upgrade)