bug#38054: mumble: "QSslSocket: cannot resolve ", Certificate Expiry, segfault
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.
>
> I'll get back to you real soon!
Hi there! I finally completed the update patch and managed to get the icons
working. It seems to work as expected without plugin issues.
It wasn't an easy task but I learnt some good stuff during the way… `:D`
Enjoy the new Mumble!
--
Ivan Vilata i Balaguer -- https://elvil.net/
>From 987f03ca1721c1aa54a078a9be143abbac82bf11 Mon Sep 17 00:00:00 2001
From: Ivan Vilata-i-Balaguer
Date: Fri, 22 Nov 2019 01:15:53 -0500
Subject: [PATCH] gnu: mumble: Update to 1.3.0.
Besides the update in itself, bundled software components are enabled as long
as they are not already implemented in an existing package (in which case the
package is used instead). Some comments were added to indicate why bundled
software components are kept or removed, why features are disabled, and the
reason to include each license.
* gnu/packages/telephony.scm (mumble): Update to 1.3.0.
* gnu/packages/patches/mumble-1.2.19-abs.patch: Remove file.
---
gnu/packages/patches/mumble-1.2.19-abs.patch | 31 -
gnu/packages/telephony.scm | 114 ---
2 files changed, 70 insertions(+), 75 deletions(-)
delete mode 100644 gnu/packages/patches/mumble-1.2.19-abs.patch
diff --git a/gnu/packages/patches/mumble-1.2.19-abs.patch
b/gnu/packages/patches/mumble-1.2.19-abs.patch
deleted file mode 100644
index 683325f4bc..00
--- a/gnu/packages/patches/mumble-1.2.19-abs.patch
+++ /dev/null
@@ -1,31 +0,0 @@
-From ea861fe86743c8402bbad77d8d1dd9de8dce447e Mon Sep 17 00:00:00 2001
-From: Mikkel Krautz
-Date: Fri, 29 Dec 2017 14:47:25 +0100
-Subject: [PATCH] AudioOutput: do not use non-existant template version of
- std::abs.
-
-This change fixes AudioOutput to use the float overload of std::abs:
-
-float std::abs(float);
-
-instead of a non-existant template version (for newer Boost 1.66).
-
-Fixes mumble-voip/mumble#3281
-
- src/mumble/AudioOutput.cpp | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/mumble/AudioOutput.cpp b/src/mumble/AudioOutput.cpp
-index cbe0c0e2b..7a0a5e2ab 100644
a/src/mumble/AudioOutput.cpp
-+++ b/src/mumble/AudioOutput.cpp
-@@ -437,7 +437,7 @@ bool AudioOutput::mix(void *outbuff, unsigned int nsamp) {
- top[2] = 0.0f;
- }
-
-- if (std::abs(front[0] * top[0] +
front[1] * top[1] + front[2] * top[2]) > 0.01f) {
-+ if (std::abs(front[0] * top[0] + front[1] *
top[1] + front[2] * top[2]) > 0.01f) {
- // Not perpendicular. Assume Y up and
rotate 90 degrees.
-
- float azimuth = 0.0f;
diff --git a/gnu/packages/telephony.scm b/gnu/packages/telephony.scm
index abb68f62b2..e1ad2f90f5 100644
--- a/gnu/packages/telephony.scm
+++ b/gnu/packages/telephony.scm
@@ -12,6 +12,7 @@
;;; Copyright © 2018 Jovany Leandro G.C
;;; Copyright © 2018 Tim Gesthuizen
;;; Copyright © 2019 Pierre Neidhardt
+;;; Copyright © 2019 Ivan Vilata i Balaguer
;;;
;;; This file is part of GNU Guix.
;;;
@@ -43,6 +44,7 @@
#:use-module (gnu packages file)
#:use-module (gnu packages protobuf)
#:use-module (gnu packages gettext)
+ #:use-module (gnu packages gl)
#:use-module (gnu packages glib)
#:use-module (gnu packages gnome)
#:use-module (gnu packages gnupg)
@@ -378,30 +380,34 @@ address of one of the participants.")
(define-public mumble
(package
(name "mumble")
-(version "1.2.19")
+(version "1.3.0")
(source (origin
(method url-fetch)
(uri (string-append "https://mumble.info/snapshot/";
name "-" version ".tar.gz"))
(sha256
(base32
-"1s60vaici3v034jzzi20x23hsj6mkjlc0glipjq4hffrg9qgnizh"))
- (patches (search-patches "mumble-1.2.19-abs.patch"))
+"03dqg5yf6d7ilc1wydpshnv1ndssppcbadqcq20jm5j4fdaf53cs"))
(modules '((guix build utils)))
(snippet
`(begin
;; Remove bundled software.
- (for-each delete-file-recursively '("3rdparty"
- "speex"
- "speexbuild"
- "opus-build"
- "opus-src"
- "sbcelt-helper-build"
- "sbcelt-lib-build"
- "sbcelt-src"))
-
bug#38054: mumble: "QSslSocket: cannot resolve ", Certificate Expiry, segfault
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 Mumble installed from > a previous generation and that one does still run. > > I tried updating it here, but looks like it's upset about not finding > the (un)bundled speex... weird because it must not have been bothered by > that before. > > Incomplete patch attached. I'm unsure if switching from qt-4 to qtbase > is the right way to upgrade to QT 5 or not? I'm guessing so? 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. I'll get back to you real soon! -- Ivan Vilata i Balaguer -- https://elvil.net/
bug#38054: mumble: "QSslSocket: cannot resolve ", Certificate Expiry, segfault
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 resolve CRYPTO_set_id_callback
>> QSslSocket: cannot resolve CRYPTO_set_locking_callback
>> QSslSocket: cannot resolve sk_free
>> QSslSocket: cannot resolve sk_num
>> QSslSocket: cannot resolve sk_pop_free
>> QSslSocket: cannot resolve sk_value
>> QSslSocket: cannot resolve SSL_library_init
>> QSslSocket: cannot resolve SSL_load_error_strings
>> QSslSocket: cannot resolve SSLv3_client_method
>> QSslSocket: cannot resolve SSLv23_client_method
>> QSslSocket: cannot resolve SSLv3_server_method
>> QSslSocket: cannot resolve SSLv23_server_method
>> QSslSocket: cannot resolve X509_STORE_CTX_get_chain
>> QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
>> QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
>> QSslSocket: cannot resolve SSLeay
>> QSslSocket: cannot call unresolved function CRYPTO_num_locks
>> QSslSocket: cannot call unresolved function CRYPTO_set_id_callback
>> QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback
>> QSslSocket: cannot call unresolved function SSL_library_init
>> QSslSocket: cannot call unresolved function SSLv23_client_method
>> QSslSocket: cannot call unresolved function sk_num
>>
>> Then it complains about "Certificate Expiry: Your certificate is about to
>> expire. You need to renew it, or you will no longer be able to connect to
>> servers you are registered on.". If I proceed to connect it goes:
>>
>> OpenSSL Support: 1 (OpenSSL 1.1.1d 10 Sep 2019)
>> Segmentation fault
>>
>> and dies. It is curious that `guix package -s openssl` reports version
>> 1.1.1c
>> instead of 1.1.1d, which matches the Debian system's version of OpenSSL, so
>> Mumble may be trying to load system libraries instead of Guix's.
>>
>> If I revert to a previous profile generation with a build of Mumble linked
>> against glibc 2.28 instead of 2.29, it doesn't print the errors and works
>> without issues.
>>
>> Thank you very much!
>>
>> --
>
> I'd have to guess that the error is that it's linked against openssl-1.1
> instead of openssl-1.1.
>
> 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 Mumble installed from
a previous generation and that one does still run.
I tried updating it here, but looks like it's upset about not finding
the (un)bundled speex... weird because it must not have been bothered by
that before.
Incomplete patch attached. I'm unsure if switching from qt-4 to qtbase
is the right way to upgrade to QT 5 or not? I'm guessing so?
diff --git a/gnu/packages/telephony.scm b/gnu/packages/telephony.scm
index 81e710a536..82ebe48931 100644
--- a/gnu/packages/telephony.scm
+++ b/gnu/packages/telephony.scm
@@ -377,15 +377,15 @@ address of one of the participants.")
(define-public mumble
(package
(name "mumble")
-(version "1.2.19")
+(version "1.3.0")
(source (origin
(method url-fetch)
(uri (string-append "https://mumble.info/snapshot/";
name "-" version ".tar.gz"))
(sha256
(base32
-"1s60vaici3v034jzzi20x23hsj6mkjlc0glipjq4hffrg9qgnizh"))
- (patches (search-patches "mumble-1.2.19-abs.patch"))
+"03dqg5yf6d7ilc1wydpshnv1ndssppcbadqcq20jm5j4fdaf53cs"))
+ ;; (patches (search-patches "mumble-1.2.19-abs.patch"))
(modules '((guix build utils)))
(snippet
`(begin
@@ -474,7 +474,7 @@ address of one of the participants.")
("speech-dispatcher" ,speech-dispatcher)
("libx11" ,libx11)
("libxi" ,libxi)
- ("qt-4" ,qt-4)
+ ("qt-4" ,qtbase)
("alsa-lib" ,alsa-lib)
("pulseaudio" ,pulseaudio)))
(native-inputs
bug#38054: mumble: "QSslSocket: cannot resolve ", Certificate Expiry, segfault
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 > QSslSocket: cannot resolve CRYPTO_set_locking_callback > QSslSocket: cannot resolve sk_free > QSslSocket: cannot resolve sk_num > QSslSocket: cannot resolve sk_pop_free > QSslSocket: cannot resolve sk_value > QSslSocket: cannot resolve SSL_library_init > QSslSocket: cannot resolve SSL_load_error_strings > QSslSocket: cannot resolve SSLv3_client_method > QSslSocket: cannot resolve SSLv23_client_method > QSslSocket: cannot resolve SSLv3_server_method > QSslSocket: cannot resolve SSLv23_server_method > QSslSocket: cannot resolve X509_STORE_CTX_get_chain > QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf > QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf > QSslSocket: cannot resolve SSLeay > QSslSocket: cannot call unresolved function CRYPTO_num_locks > QSslSocket: cannot call unresolved function CRYPTO_set_id_callback > QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback > QSslSocket: cannot call unresolved function SSL_library_init > QSslSocket: cannot call unresolved function SSLv23_client_method > QSslSocket: cannot call unresolved function sk_num > > Then it complains about "Certificate Expiry: Your certificate is about to > expire. You need to renew it, or you will no longer be able to connect to > servers you are registered on.". If I proceed to connect it goes: > > OpenSSL Support: 1 (OpenSSL 1.1.1d 10 Sep 2019) > Segmentation fault > > and dies. It is curious that `guix package -s openssl` reports version 1.1.1c > instead of 1.1.1d, which matches the Debian system's version of OpenSSL, so > Mumble may be trying to load system libraries instead of Guix's. > > If I revert to a previous profile generation with a build of Mumble linked > against glibc 2.28 instead of 2.29, it doesn't print the errors and works > without issues. > > Thank you very much! > > -- I'd have to guess that the error is that it's linked against openssl-1.1 instead of openssl-1.1. 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. -- Efraim Flashner אפרים פלשנר GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351 Confidentiality cannot be guaranteed on emails sent or received unencrypted signature.asc Description: PGP signature
bug#38054: mumble: "QSslSocket: cannot resolve ", Certificate Expiry, segfault
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 resolve sk_free QSslSocket: cannot resolve sk_num QSslSocket: cannot resolve sk_pop_free QSslSocket: cannot resolve sk_value QSslSocket: cannot resolve SSL_library_init QSslSocket: cannot resolve SSL_load_error_strings QSslSocket: cannot resolve SSLv3_client_method QSslSocket: cannot resolve SSLv23_client_method QSslSocket: cannot resolve SSLv3_server_method QSslSocket: cannot resolve SSLv23_server_method QSslSocket: cannot resolve X509_STORE_CTX_get_chain QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf QSslSocket: cannot resolve SSLeay QSslSocket: cannot call unresolved function CRYPTO_num_locks QSslSocket: cannot call unresolved function CRYPTO_set_id_callback QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback QSslSocket: cannot call unresolved function SSL_library_init QSslSocket: cannot call unresolved function SSLv23_client_method QSslSocket: cannot call unresolved function sk_num Then it complains about "Certificate Expiry: Your certificate is about to expire. You need to renew it, or you will no longer be able to connect to servers you are registered on.". If I proceed to connect it goes: OpenSSL Support: 1 (OpenSSL 1.1.1d 10 Sep 2019) Segmentation fault and dies. It is curious that `guix package -s openssl` reports version 1.1.1c instead of 1.1.1d, which matches the Debian system's version of OpenSSL, so Mumble may be trying to load system libraries instead of Guix's. If I revert to a previous profile generation with a build of Mumble linked against glibc 2.28 instead of 2.29, it doesn't print the errors and works without issues. Thank you very much! -- Ivan Vilata i Balaguer -- https://elvil.net/
