Bug#873275: always segfaults at start due to QSslSocket

2017-08-26 Thread 積丹尼 Dan Jacobson
Glad to have found the bug for you early.

I only use qgis offline, so was dismayed that I couldn't even start it
even if never planning to use SSL over the network.

I mean even researchers in some offline arctic lab will find the copy of
qgis they brought with them is unusable even without ever having
attempted to make a http, (not even https) connection.

There should be some fallback mode available.



Bug#873275: always segfaults at start due to QSslSocket

2017-08-26 Thread Lisandro Damián Nicanor Pérez Meyer
On sábado, 26 de agosto de 2017 17:39:28 -03 Sebastiaan Couwenberg wrote:
[snip] 
> > Sebastiaan: we might need to remove SSL support in Qt4 I'm afraid. How is
> > the qt5 port going?
> 
> Qt5 support will be available in QGIS 3.0.0 due in November this year,
> the 3.x release will need some time to mature to a long term release
> we'll include in Debian. The QGIS 3.4 LTR is due in November 2018. [0]
> 
> We could include QGIS 3.0.0 in Debian in the mean time and switch back
> to the LTR releases a year later to not hold up to Qt4 removal too much.
> Although I'd rather stick to the LTR releases in Debian.

That sounds truly achievable. I really don't think we would be able to remove 
Qt4 this year *but* I can't control OpenSSL 1.0 removal. If that happens I 
have no other choice than removing SSL support.

Cheers!

-- 
  "Waaah! Debian never keeps its release schedules!"
Okay, lets make a Debian-like distribution that hits its schedules and is
close to bleeding edge.
  "Waaah! Ubuntu ships buggy stuff!"
Grr.
(Not aimed at jwb in particular, BTW. Just pointing out that there's always
going to be some disappointed people.)
  vmole (subscriber, #111) - http://lwn.net/Articles/279111/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Bug#873275: always segfaults at start due to QSslSocket

2017-08-26 Thread Sebastiaan Couwenberg
On 08/26/2017 03:28 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
> On sábado, 26 de agosto de 2017 15:50:14 -03 Adrian Bunk wrote:
>> On Sat, Aug 26, 2017 at 09:31:01AM -0300, Lisandro Damián Nicanor Pérez 
> Meyer wrote:
>>> First of all sorry for the top posting. Actually this is not a bug in qt4,
>>> OpenSSL 1.0 Is getting removed and qt4 *needs* to switch to 1.1.
>>
>> That's clear.
>>
>>> I uploaded
>>> to experimental for people to check, so actually this should be an
>>> important bug against qgis. If necessary I'll explain more with a more
>>> comfortable mail client at hand.
>>
>> The problem as reported by Dan and reproduced by me is:
> [snip] 
>> To me this looks like qt4 built with OpenSSL 1.1 trying to use functions
>> that were removed in OpenSSL 1.1, example:
>>
>>   /usr/include/openssl/ssl.h:#define SSLv23_client_method   
>> TLS_client_method
>>
>>
>> In OpenSSL 1.0.2 this was a proper function, but qt4 trying to load this
>> from libssl.so.1.1 cannot work.
> 
> Indeed, so the upload did work after all: we now know that the proposed patch 
> is not enough.
> 
> Sebastiaan: we might need to remove SSL support in Qt4 I'm afraid. How is the 
> qt5 port going?

Qt5 support will be available in QGIS 3.0.0 due in November this year,
the 3.x release will need some time to mature to a long term release
we'll include in Debian. The QGIS 3.4 LTR is due in November 2018. [0]

We could include QGIS 3.0.0 in Debian in the mean time and switch back
to the LTR releases a year later to not hold up to Qt4 removal too much.
Although I'd rather stick to the LTR releases in Debian.

[0]
http://qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature


Bug#873275: always segfaults at start due to QSslSocket

2017-08-26 Thread Lisandro Damián Nicanor Pérez Meyer
On sábado, 26 de agosto de 2017 15:50:14 -03 Adrian Bunk wrote:
> On Sat, Aug 26, 2017 at 09:31:01AM -0300, Lisandro Damián Nicanor Pérez 
Meyer wrote:
> > First of all sorry for the top posting. Actually this is not a bug in qt4,
> > OpenSSL 1.0 Is getting removed and qt4 *needs* to switch to 1.1.
> 
> That's clear.
> 
> > I uploaded
> > to experimental for people to check, so actually this should be an
> > important bug against qgis. If necessary I'll explain more with a more
> > comfortable mail client at hand.
> 
> The problem as reported by Dan and reproduced by me is:
[snip] 
> To me this looks like qt4 built with OpenSSL 1.1 trying to use functions
> that were removed in OpenSSL 1.1, example:
> 
>   /usr/include/openssl/ssl.h:#define SSLv23_client_method   
> TLS_client_method
> 
> 
> In OpenSSL 1.0.2 this was a proper function, but qt4 trying to load this
> from libssl.so.1.1 cannot work.

Indeed, so the upload did work after all: we now know that the proposed patch 
is not enough.

Sebbastiaan: we might need to remove SSL support in Qt4 I'm afraid. How is the 
qt5 port going?

-- 
En los momentos de crisis, la imaginación es mas importante que el
conocimiento.
 Albert Einstein

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.


Bug#873275: always segfaults at start due to QSslSocket

2017-08-26 Thread Adrian Bunk
On Sat, Aug 26, 2017 at 09:31:01AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> First of all sorry for the top posting. Actually this is not a bug in qt4,
> OpenSSL 1.0 Is getting removed and qt4 *needs* to switch to 1.1.

That's clear.

> I uploaded
> to experimental for people to check, so actually this should be an
> important bug against qgis. If necessary I'll explain more with a more
> comfortable mail client at hand.

The problem as reported by Dan and reproduced by me is:

$ qgis
Warning: QSslSocket: cannot resolve CRYPTO_num_locks
Warning: QSslSocket: cannot resolve CRYPTO_set_id_callback
Warning: QSslSocket: cannot resolve CRYPTO_set_locking_callback
Warning: QSslSocket: cannot resolve sk_free
Warning: QSslSocket: cannot resolve sk_num
Warning: QSslSocket: cannot resolve sk_pop_free
Warning: QSslSocket: cannot resolve sk_value
Warning: QSslSocket: cannot resolve SSL_library_init
Warning: QSslSocket: cannot resolve SSL_load_error_strings
Warning: QSslSocket: cannot resolve X509_get_notAfter
Warning: QSslSocket: cannot resolve X509_get_notBefore
Warning: QSslSocket: cannot resolve SSLv2_client_method
Warning: QSslSocket: cannot resolve SSLv23_client_method
Warning: QSslSocket: cannot resolve SSLv2_server_method
Warning: QSslSocket: cannot resolve SSLv23_server_method
Warning: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
Warning: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
Warning: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
Warning: QSslSocket: cannot resolve SSLeay
Warning: QSslSocket: cannot call unresolved function SSL_library_init
Warning: QSslSocket: cannot call unresolved function SSLv23_client_method
Warning: QSslSocket: cannot call unresolved function sk_num
Warning: QSslSocket: cannot call unresolved function X509_get_notBefore
Warning: QSslSocket: cannot call unresolved function X509_get_notAfter
Segmentation fault


To me this looks like qt4 built with OpenSSL 1.1 trying to use functions 
that were removed in OpenSSL 1.1, example:

  /usr/include/openssl/ssl.h:#define SSLv23_client_methodTLS_client_method


In OpenSSL 1.0.2 this was a proper function, but qt4 trying to load this 
from libssl.so.1.1 cannot work.


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Bug#873275: always segfaults at start due to QSslSocket

2017-08-26 Thread Lisandro Damián Nicanor Pérez Meyer
First of all sorry for the top posting. Actually this is not a bug in qt4,
OpenSSL 1.0 Is getting removed and qt4 *needs* to switch to 1.1. I uploaded
to experimental for people to check, so actually this should be an
important bug against qgis. If necessary I'll explain more with a more
comfortable mail client at hand.

El 26 ago. 2017 8:36 a.m., "Adrian Bunk"  escribió:

Control: reopen -1
Control: severity -1 serious
Control: tags -1 - moreinfo
Control: tags -1 confirmed
Control: reassign -1 src:qt4-x11 4:4.8.7+dfsg-12
Control: affects -1 qgis

On Sat, Aug 26, 2017 at 08:45:21AM +0200, Sebastiaan Couwenberg wrote:
> tags 873275 unreproducible
> severity 873275 normal
> thanks
>
> qgis works fine here.
>
> On 08/26/2017 03:11 AM, 積丹尼 Dan Jacobson wrote:
> > -- System Information:
> > Debian Release: buster/sid
> >   APT prefers experimental
>
> This likely caused your problem, you shouldn't prefer experimental over
> unstable.
>...

This is supposed to work when the dependencies allow it,[1]
and such bug reports can be quite valuable for finding regressions
before they hit a large userbase in unstable.

Likely causes for such problems include for example library ABI changes
without a corresponding change of the so-name.

Based on the information in the bug it was in this case trivial to
narrow the regression down to Qt4 in experimental switching to
OpenSSL 1.1 - qgis works for me with Qt4 from stable/unstable
and segfaults as describes by Dan with Qt4 from experimental.

> Kind Regards,
>
> Bas

cu
Adrian

[1] apt preferring experimental is IMHO not a good idea,
but that doesn't turn bugs into non-bugs

--

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed


Processed: Re: Bug#873275: always segfaults at start due to QSslSocket

2017-08-26 Thread Debian Bug Tracking System
Processing control commands:

> reopen -1
Bug #873275 {Done: Sebastiaan Couwenberg } [qgis] always 
segfaults at start due to QSslSocket
Bug reopened
Ignoring request to alter fixed versions of bug #873275 to the same values 
previously set
> severity -1 serious
Bug #873275 [qgis] always segfaults at start due to QSslSocket
Severity set to 'serious' from 'normal'
> tags -1 - moreinfo
Bug #873275 [qgis] always segfaults at start due to QSslSocket
Ignoring request to alter tags of bug #873275 to the same tags previously set
> tags -1 confirmed
Bug #873275 [qgis] always segfaults at start due to QSslSocket
Added tag(s) confirmed.
> reassign -1 src:qt4-x11 4:4.8.7+dfsg-12
Bug #873275 [qgis] always segfaults at start due to QSslSocket
Bug reassigned from package 'qgis' to 'src:qt4-x11'.
No longer marked as found in versions qgis/2.14.18+dfsg-1.
Ignoring request to alter fixed versions of bug #873275 to the same values 
previously set
Bug #873275 [src:qt4-x11] always segfaults at start due to QSslSocket
Marked as found in versions qt4-x11/4:4.8.7+dfsg-12.
> affects -1 qgis
Bug #873275 [src:qt4-x11] always segfaults at start due to QSslSocket
Added indication that 873275 affects qgis

-- 
873275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#873275: always segfaults at start due to QSslSocket

2017-08-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 873275 unreproducible
Bug #873275 [qgis] always segfaults at start due to QSslSocket
Added tag(s) unreproducible.
> severity 873275 normal
Bug #873275 [qgis] always segfaults at start due to QSslSocket
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
873275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#873275: always segfaults at start due to QSslSocket

2017-08-25 Thread 積丹尼 Dan Jacobson
Package: qgis
Version: 2.14.18+dfsg-1
Severity: grave

# apt-get install qgis
$ qgis
Warning: QSslSocket: cannot resolve CRYPTO_num_locks
Warning: QSslSocket: cannot resolve CRYPTO_set_id_callback
Warning: QSslSocket: cannot resolve CRYPTO_set_locking_callback
Warning: QSslSocket: cannot resolve sk_free
Warning: QSslSocket: cannot resolve sk_num
Warning: QSslSocket: cannot resolve sk_pop_free
Warning: QSslSocket: cannot resolve sk_value
Warning: QSslSocket: cannot resolve SSL_library_init
Warning: QSslSocket: cannot resolve SSL_load_error_strings
Warning: QSslSocket: cannot resolve X509_get_notAfter
Warning: QSslSocket: cannot resolve X509_get_notBefore
Warning: QSslSocket: cannot resolve SSLv2_client_method
Warning: QSslSocket: cannot resolve SSLv23_client_method
Warning: QSslSocket: cannot resolve SSLv2_server_method
Warning: QSslSocket: cannot resolve SSLv23_server_method
Warning: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
Warning: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
Warning: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
Warning: QSslSocket: cannot resolve SSLeay
Warning: QSslSocket: cannot call unresolved function SSL_library_init
Warning: QSslSocket: cannot call unresolved function SSLv23_client_method
Warning: QSslSocket: cannot call unresolved function sk_num
Warning: QSslSocket: cannot call unresolved function X509_get_notBefore
Warning: QSslSocket: cannot call unresolved function X509_get_notAfter
Segmentation fault

-- System Information:
Debian Release: buster/sid
  APT prefers experimental
  APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages qgis depends on:
ii  libc6   2.25-0experimental1
ii  libexpat1   2.2.3-1
ii  libgcc1 1:7.2.0-1
ii  libgdal20 [gdal-abi-2-2-1]  2.2.1+dfsg-2+b1
ii  libgeos-c1v53.5.1-3
ii  libgsl232.4+dfsg-6
ii  libgslcblas02.4+dfsg-6
ii  libpq5  10~beta3-1
ii  libproj12   4.9.3-2
ii  libqca2 2.1.3-1
ii  libqgis-analysis2.14.18 2.14.18+dfsg-1
ii  libqgis-app2.14.18  2.14.18+dfsg-1
ii  libqgis-core2.14.18 2.14.18+dfsg-1
ii  libqgis-gui2.14.18  2.14.18+dfsg-1
ii  libqgis-networkanalysis2.14.18  2.14.18+dfsg-1
ii  libqscintilla2-12v5 2.9.3+dfsg-4+b1
ii  libqt4-network  4:4.8.7+dfsg-12
ii  libqt4-sql  4:4.8.7+dfsg-12
ii  libqt4-svg  4:4.8.7+dfsg-12
ii  libqt4-xml  4:4.8.7+dfsg-12
ii  libqtcore4  4:4.8.7+dfsg-12
ii  libqtgui4   4:4.8.7+dfsg-12
ii  libqtwebkit42.3.4.dfsg-9.1
ii  libqwt6abi1 6.1.2-6
ii  libspatialindex4v5  1.8.5-5
ii  libspatialite7  4.4.0~rc1-1~exp2
ii  libsqlite3-03.20.0-1
ii  libstdc++6  7.2.0-1
ii  python-qgis 2.14.18+dfsg-1
ii  qgis-common 2.14.18+dfsg-1
ii  qgis-providers  2.14.18+dfsg-1

Versions of packages qgis recommends:
pn  qgis-plugin-grass
pn  qgis-provider-grass  

Versions of packages qgis suggests:
ii  gpsbabel  1.5.3-2

-- no debconf information