From: CaptainDrewBoy <CaptainDrewBoy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] libmbedcrypto breaking some apps
Date: Fri, 24 Jun 2022 03:31:09 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37665@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
New issue by CaptainDrewBoy on void-packages repository
https://github.com/void-linux/void-packages/issues/37665
Description:
(notes with an asterix are largely anecdotal and people smarter than me can probably think of reasons to disregard them)
mpv and qutebrowser won't start for me anymore, both citing an `error while loading shared libraries: /usr/lib64/libmbedcrypto.so.3: file too short`
* I have also had difficulties getting apps to register mic input, but I can't tell if these are related.
The cited file does exist, but is empty. I have `mbedtls` installed, but Void's version appears to be out of date from upstream.
* I suspect, but don't have the technical know-how to prove, that this is related to a recent update that pulled `librist` onto my system, which depends on `mbedtls`.
next reply other threads:[~2022-06-24 1:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 1:31 CaptainDrewBoy [this message]
2022-06-24 1:39 ` HadetTheUndying
2022-06-24 4:26 ` sgn
2022-06-24 12:35 ` CaptainDrewBoy
2022-06-24 13:35 ` sgn
2022-06-24 18:18 ` CaptainDrewBoy
2022-06-24 18:18 ` CaptainDrewBoy
2022-06-24 18:18 ` CaptainDrewBoy
2022-06-24 18:19 ` CaptainDrewBoy
2022-06-24 18:57 ` paper42
2022-06-25 3:11 ` sgn
2022-06-25 10:47 ` CaptainDrewBoy
2022-06-25 13:36 ` sgn
2022-06-25 14:50 ` CaptainDrewBoy
2022-06-25 14:52 ` CaptainDrewBoy
2022-06-25 14:54 ` sgn
2022-06-25 15:02 ` CaptainDrewBoy
2022-06-25 15:02 ` [ISSUE] [CLOSED] " CaptainDrewBoy
2022-06-25 15:04 ` sgn
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37665@inbox.vuxu.org \
--to=captaindrewboy@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).