Ivan Vilata i Balaguer (2019-11-20 00:30:24 -0500) wrote:
> Thanks Christopher! I'm currently working in a complete patch, it's
> building and running (and it's not suffering from the errors I found!), but
> I still need to locate the appropriate icons and include them in the
> package.
>
>
Christopher Lemmer Webber (2019-11-19 14:00:20 -0500) wrote:
> Efraim Flashner writes:
>
> > I also noticed that there's a newer version of mumble out, 1,3.0, which
> > builds against qt5. We should probably just go ahead and upgrade it.
>
> I've also gotten this. I have an older version of
Efraim Flashner writes:
> On Sun, Nov 03, 2019 at 11:04:05PM -0500, Ivan Vilata i Balaguer wrote:
>> Hi! I'm using Mumble 1.2.19 from Guix commit 7f81cce3 on Debian Sid. On
>> start, it logs the following messages:
>>
>> QSslSocket: cannot resolve CRYPTO_num_locks
>> QSslSocket: cannot
On Sun, Nov 03, 2019 at 11:04:05PM -0500, Ivan Vilata i Balaguer wrote:
> Hi! I'm using Mumble 1.2.19 from Guix commit 7f81cce3 on Debian Sid. On
> start, it logs the following messages:
>
> QSslSocket: cannot resolve CRYPTO_num_locks
> QSslSocket: cannot resolve CRYPTO_set_id_callback
Hi! I'm using Mumble 1.2.19 from Guix commit 7f81cce3 on Debian Sid. On
start, it logs the following messages:
QSslSocket: cannot resolve CRYPTO_num_locks
QSslSocket: cannot resolve CRYPTO_set_id_callback
QSslSocket: cannot resolve CRYPTO_set_locking_callback
QSslSocket: cannot
