Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Qt5 updates will require some Qt5 Apps to be rebuilt against newer versions
Date: Fri, 17 Jun 2022 19:12:23 +0200	[thread overview]
Message-ID: <20220617171223.PrV5lkfy38e3YzjiVvUk6gPQkWsSpr9LpLV3DBU_GGQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37598@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]

Closed issue by TeusLollo on void-packages repository

https://github.com/void-linux/void-packages/issues/37598

Description:
### Is this a new report?

Yes

### System Info

Void 5.15.47_1 x86_64 GenuineIntel uptodate rFFFF

### Package(s) Affected

corectrl-1.2.3_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

Recent updates of Qt5 libraries apparently broke several depending packages that must be rebuilt for it, which should otherwise work. 

### Actual behaviour

Qt5-based applications currently crash due to the recent update of Qt5 libraries. When launching CoreCtrl, for example, here's the output I get:

[17-06-22 14:20:26.361][W] vulkaninfo command failed
Cannot mix incompatible Qt library (5.15.2) with this library (5.15.4)
zsh: IOT instruction  corectrl

Fairly self-explanatory. 

An user on reddit con also confirm that VirtualBox has also been broken:
https://reddit.com/r/voidlinux/comments/ve9gky/todays_qt5_updates_broke_virtualbox/

### Steps to reproduce

1 Update a given x86_64 Void Linux system with the most recent Qt5 libraries into repositories. 
2 Try to launch CoreCtrl (Or, more likely, most qt5 applications which have not been rebuilt against newer libraries)
3 See failure-to-launch outputs for yourself

I presume at least some applications will need to be rebuilt for the newer qt5 libraries. 
Just dropping this bug report here, feel free to remove if it's felt inappropriate and/or pestering. 

Thanks for all your work, devs!

  parent reply	other threads:[~2022-06-17 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 12:36 [ISSUE] " TeusLollo
2022-06-17 12:44 ` paper42
2022-06-17 15:01 ` paoloschi
2022-06-17 15:03 ` Johnnynator
2022-06-17 15:10 ` paoloschi
2022-06-17 15:16 ` RicArch97
2022-06-17 16:28 ` TeusLollo
2022-06-17 17:12 ` Johnnynator [this message]
2022-11-20 10:47 ` paoloschi
2022-11-20 13:03 ` JamiKettunen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220617171223.PrV5lkfy38e3YzjiVvUk6gPQkWsSpr9LpLV3DBU_GGQ@z \
    --to=johnnynator@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).