Re: www/otter-browser crash on startup net/libproxy / x11/qt5 related?

2016-04-18 Thread Adam Wolk
On Mon, 18 Apr 2016 19:15:53 +0200
Antoine Jacoutot  wrote:

> On Mon, Apr 18, 2016 at 07:00:35PM +0200, Adam Wolk wrote:
> > On Mon, 18 Apr 2016 17:34:28 +0200
> > Adam Wolk  wrote:
> >   
> > > On Wed, 30 Mar 2016 17:10:34 +0100
> > > Stuart Henderson  wrote:
> > >   
> > > > On 2016/03/30 15:49, Adam Wolk wrote:
> > > > > Roughly I'm interested if anyone else can confirm that they
> > > > > get otter crashing on startup by default.  
> > > > 
> > > > FWIW it's starting OK for me, with a recently updated pkg snap.
> > > > I'm not seeing any qt4 libraries being pulled in:
> > > > 
> > > 
> > > Well I now have a second qt5 port that segfaults when trying to
> > > use libproxy.
> > > 
> > > devel/zeal
> > > https://gist.github.com/mulander/84f9f577fd4489fc581c593cabd15895
> > > 
> > > Here's the interesting part though. It doesn't crash when I'm
> > > running xfce4. The segfaults happen only when I'm running gnome3
> > > (3.18.2).
> > > 
> > > Did anyone hit similar problems with qt5 based ports on Gnome?
> > > 
> > > Regards,
> > > Adam
> > >   
> > 
> > With help from sthen@ I managed to pin point the crash to a null
> > pointer dereference in libproxy.
> > 
> > The issue has been reported upstream:
> >  https://github.com/libproxy/libproxy/issues/24
> > with a patch to fix the problem:
> >  https://github.com/libproxy/libproxy/pull/25
> > 
> > I would like to suggest adding the patch to our current libproxy
> > port as the bug prevents www/otter-browser & devel/zeal from even
> > starting up on Gnome 3. It might impact more qt5 related ports when
> > ran under Gnome 3 (anything network related using libproxy).
> > 
> > Any OK's for adding the patch?  
> 
> OK for me with 2 nitpicks :
> 
> 
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/net/libproxy/Makefile,v
> > retrieving revision 1.47
> > diff -u -p -r1.47 Makefile
> > --- Makefile20 Mar 2016 17:59:21 -  1.47
> > +++ Makefile18 Apr 2016 16:55:33 -
> > @@ -6,7 +6,7 @@ COMMENT-webkit= pacrunner libproxy
> > plug GH_ACCOUNT=libproxy
> >  GH_PROJECT=libproxy
> >  GH_TAGNAME=0.4.12
> > -REVISION=  0
> > +REVISION=  1  
> 
> You are bumping 2 packages here.
> Use this instead:
> REVISION-main=1
> 

Done.

> >  SUBST_VARS=GH_TAGNAME
> >  
> >  PKGNAME-main=  ${DISTNAME}
> > Index: patches/patch-libproxy_modules_ignore_ip_cpp
> > ===
> > RCS file: patches/patch-libproxy_modules_ignore_ip_cpp
> > diff -N patches/patch-libproxy_modules_ignore_ip_cpp
> > --- /dev/null   1 Jan 1970 00:00:00 -
> > +++ patches/patch-libproxy_modules_ignore_ip_cpp18 Apr 2016
> > 16:55:33 - @@ -0,0 +1,22 @@
> > +$OpenBSD$  
> 
> Just add this:
> 
> https://github.com/libproxy/libproxy/issues/24
> 
> It's enough. And people who want to know more can follow the link.
> 

Limited the info just to the link.

Committed. Let me know if something needs changes.

> > +Fix a null pointer dereference for qt5 applications when using
> > +gnome 3.
> > +
> > +Prevents a crash of the following ports on gnome 3:
> > + - devel/zeal
> > + - www/otter-browser
> > +
> > +Reported upstream with a fix:
> > + - https://github.com/libproxy/libproxy/issues/24
> > + - https://github.com/libproxy/libproxy/pull/25
> > +--- libproxy/modules/ignore_ip.cpp.origMon Apr 18 18:14:53
> > 2016  libproxy/modules/ignore_ip.cppMon Apr 18 18:15:26
> > 2016 +@@ -147,7 +147,7 @@ class ip_ignore_extension : public
> > ignore_extension { 
> > +   else
> > +   {
> > +   /* If CIDR notation was used, get
> > the netmask */ +-   if
> > (sscanf(mask.c_str(), "%d", &cidr) == 1)
> > ++  if (ign_ip &&
> > sscanf(mask.c_str(), "%d", &cidr) == 1)
> > +   net_ip =
> > sockaddr_from_cidr(ign_ip->sa_family, cidr);
> > +   }
> > + 
> >   
> 



Re: www/otter-browser crash on startup net/libproxy / x11/qt5 related?

2016-04-18 Thread Antoine Jacoutot
On Mon, Apr 18, 2016 at 07:00:35PM +0200, Adam Wolk wrote:
> On Mon, 18 Apr 2016 17:34:28 +0200
> Adam Wolk  wrote:
> 
> > On Wed, 30 Mar 2016 17:10:34 +0100
> > Stuart Henderson  wrote:
> > 
> > > On 2016/03/30 15:49, Adam Wolk wrote:  
> > > > Roughly I'm interested if anyone else can confirm that they get
> > > > otter crashing on startup by default.
> > > 
> > > FWIW it's starting OK for me, with a recently updated pkg snap.
> > > I'm not seeing any qt4 libraries being pulled in:
> > >   
> > 
> > Well I now have a second qt5 port that segfaults when trying to use
> > libproxy.
> > 
> > devel/zeal
> > https://gist.github.com/mulander/84f9f577fd4489fc581c593cabd15895
> > 
> > Here's the interesting part though. It doesn't crash when I'm running
> > xfce4. The segfaults happen only when I'm running gnome3 (3.18.2).
> > 
> > Did anyone hit similar problems with qt5 based ports on Gnome?
> > 
> > Regards,
> > Adam
> > 
> 
> With help from sthen@ I managed to pin point the crash to a null
> pointer dereference in libproxy.
> 
> The issue has been reported upstream:
>  https://github.com/libproxy/libproxy/issues/24
> with a patch to fix the problem:
>  https://github.com/libproxy/libproxy/pull/25
> 
> I would like to suggest adding the patch to our current libproxy port
> as the bug prevents www/otter-browser & devel/zeal from even starting
> up on Gnome 3. It might impact more qt5 related ports when ran under
> Gnome 3 (anything network related using libproxy).
> 
> Any OK's for adding the patch?

OK for me with 2 nitpicks :


> Index: Makefile
> ===
> RCS file: /cvs/ports/net/libproxy/Makefile,v
> retrieving revision 1.47
> diff -u -p -r1.47 Makefile
> --- Makefile  20 Mar 2016 17:59:21 -  1.47
> +++ Makefile  18 Apr 2016 16:55:33 -
> @@ -6,7 +6,7 @@ COMMENT-webkit=   pacrunner libproxy plug
>  GH_ACCOUNT=  libproxy
>  GH_PROJECT=  libproxy
>  GH_TAGNAME=  0.4.12
> -REVISION=0
> +REVISION=1

You are bumping 2 packages here.
Use this instead:
REVISION-main=  1

>  SUBST_VARS=  GH_TAGNAME
>  
>  PKGNAME-main=${DISTNAME}
> Index: patches/patch-libproxy_modules_ignore_ip_cpp
> ===
> RCS file: patches/patch-libproxy_modules_ignore_ip_cpp
> diff -N patches/patch-libproxy_modules_ignore_ip_cpp
> --- /dev/null 1 Jan 1970 00:00:00 -
> +++ patches/patch-libproxy_modules_ignore_ip_cpp  18 Apr 2016 16:55:33 
> -
> @@ -0,0 +1,22 @@
> +$OpenBSD$

Just add this:

https://github.com/libproxy/libproxy/issues/24

It's enough. And people who want to know more can follow the link.

> +Fix a null pointer dereference for qt5 applications when using
> +gnome 3.
> +
> +Prevents a crash of the following ports on gnome 3:
> + - devel/zeal
> + - www/otter-browser
> +
> +Reported upstream with a fix:
> + - https://github.com/libproxy/libproxy/issues/24
> + - https://github.com/libproxy/libproxy/pull/25
> +--- libproxy/modules/ignore_ip.cpp.orig  Mon Apr 18 18:14:53 2016
>  libproxy/modules/ignore_ip.cpp   Mon Apr 18 18:15:26 2016
> +@@ -147,7 +147,7 @@ class ip_ignore_extension : public ignore_extension { 
> + else
> + {
> + /* If CIDR notation was used, get the netmask */
> +-if (sscanf(mask.c_str(), "%d", &cidr) == 1)
> ++if (ign_ip && sscanf(mask.c_str(), "%d", &cidr) 
> == 1)
> + net_ip = 
> sockaddr_from_cidr(ign_ip->sa_family, cidr);
> + }
> + 
> 

-- 
Antoine



Re: www/otter-browser crash on startup net/libproxy / x11/qt5 related?

2016-04-18 Thread Adam Wolk
On Mon, 18 Apr 2016 17:34:28 +0200
Adam Wolk  wrote:

> On Wed, 30 Mar 2016 17:10:34 +0100
> Stuart Henderson  wrote:
> 
> > On 2016/03/30 15:49, Adam Wolk wrote:  
> > > Roughly I'm interested if anyone else can confirm that they get
> > > otter crashing on startup by default.
> > 
> > FWIW it's starting OK for me, with a recently updated pkg snap.
> > I'm not seeing any qt4 libraries being pulled in:
> >   
> 
> Well I now have a second qt5 port that segfaults when trying to use
> libproxy.
> 
> devel/zeal
> https://gist.github.com/mulander/84f9f577fd4489fc581c593cabd15895
> 
> Here's the interesting part though. It doesn't crash when I'm running
> xfce4. The segfaults happen only when I'm running gnome3 (3.18.2).
> 
> Did anyone hit similar problems with qt5 based ports on Gnome?
> 
> Regards,
> Adam
> 

With help from sthen@ I managed to pin point the crash to a null
pointer dereference in libproxy.

The issue has been reported upstream:
 https://github.com/libproxy/libproxy/issues/24
with a patch to fix the problem:
 https://github.com/libproxy/libproxy/pull/25

I would like to suggest adding the patch to our current libproxy port
as the bug prevents www/otter-browser & devel/zeal from even starting
up on Gnome 3. It might impact more qt5 related ports when ran under
Gnome 3 (anything network related using libproxy).

Any OK's for adding the patch?

Index: Makefile
===
RCS file: /cvs/ports/net/libproxy/Makefile,v
retrieving revision 1.47
diff -u -p -r1.47 Makefile
--- Makefile20 Mar 2016 17:59:21 -  1.47
+++ Makefile18 Apr 2016 16:55:33 -
@@ -6,7 +6,7 @@ COMMENT-webkit= pacrunner libproxy plug
 GH_ACCOUNT=libproxy
 GH_PROJECT=libproxy
 GH_TAGNAME=0.4.12
-REVISION=  0
+REVISION=  1
 SUBST_VARS=GH_TAGNAME
 
 PKGNAME-main=  ${DISTNAME}
Index: patches/patch-libproxy_modules_ignore_ip_cpp
===
RCS file: patches/patch-libproxy_modules_ignore_ip_cpp
diff -N patches/patch-libproxy_modules_ignore_ip_cpp
--- /dev/null   1 Jan 1970 00:00:00 -
+++ patches/patch-libproxy_modules_ignore_ip_cpp18 Apr 2016 16:55:33 
-
@@ -0,0 +1,22 @@
+$OpenBSD$
+Fix a null pointer dereference for qt5 applications when using
+gnome 3.
+
+Prevents a crash of the following ports on gnome 3:
+ - devel/zeal
+ - www/otter-browser
+
+Reported upstream with a fix:
+ - https://github.com/libproxy/libproxy/issues/24
+ - https://github.com/libproxy/libproxy/pull/25
+--- libproxy/modules/ignore_ip.cpp.origMon Apr 18 18:14:53 2016
 libproxy/modules/ignore_ip.cpp Mon Apr 18 18:15:26 2016
+@@ -147,7 +147,7 @@ class ip_ignore_extension : public ignore_extension { 
+   else
+   {
+   /* If CIDR notation was used, get the netmask */
+-  if (sscanf(mask.c_str(), "%d", &cidr) == 1)
++  if (ign_ip && sscanf(mask.c_str(), "%d", &cidr) 
== 1)
+   net_ip = 
sockaddr_from_cidr(ign_ip->sa_family, cidr);
+   }
+ 



Re: www/otter-browser crash on startup net/libproxy / x11/qt5 related?

2016-04-18 Thread Adam Wolk
On Wed, 30 Mar 2016 17:10:34 +0100
Stuart Henderson  wrote:

> On 2016/03/30 15:49, Adam Wolk wrote:
> > Roughly I'm interested if anyone else can confirm that they get
> > otter crashing on startup by default.  
> 
> FWIW it's starting OK for me, with a recently updated pkg snap.
> I'm not seeing any qt4 libraries being pulled in:
> 

Well I now have a second qt5 port that segfaults when trying to use
libproxy.

devel/zeal
https://gist.github.com/mulander/84f9f577fd4489fc581c593cabd15895

Here's the interesting part though. It doesn't crash when I'm running
xfce4. The segfaults happen only when I'm running gnome3 (3.18.2).

Did anyone hit similar problems with qt5 based ports on Gnome?

Regards,
Adam



Re: www/otter-browser crash on startup net/libproxy / x11/qt5 related?

2016-03-30 Thread Adam Wolk
Dnia 2016-03-30, o godz. 17:10:34
Stuart Henderson  napisaƂ(a):

> On 2016/03/30 15:49, Adam Wolk wrote:
> > Roughly I'm interested if anyone else can confirm that they get
> > otter crashing on startup by default.
> 
> FWIW it's starting OK for me, with a recently updated pkg snap.
> I'm not seeing any qt4 libraries being pulled in:
> 

My last snap was between lib major bumps. Perhaps I upgraded when not
all packages were rebuilt. Thanks for testing. I'll bump my snapshot
and will retry.

> $ ldd /usr/local/bin/otter-browser 
> /usr/local/bin/otter-browser:
>   StartEnd  Type Open Ref GrpRef Name
>   1f5fa480 1f5fa50a6000 exe  20
> 0  /usr/local/bin/otter-browser 1f6263008000 1f626348c000
> rlib 01   0  /usr/local/lib/qt5/./libQt5DBus.so.1.1
> 1f628ee73000 1f628f36a000 rlib 01
> 0  /usr/local/lib/qt5/./libQt5Multimedia.so.1.1 1f6228921000
> 1f6228d94000 rlib 02
> 0  /usr/local/lib/qt5/./libQt5PrintSupport.so.1.1
> 1f6290c0e000 1f6291245000 rlib 01
> 0  /usr/local/lib/qt5/./libQt5Script.so.1.1 1f627b9b7000
> 1f627bdfa000 rlib 03
> 0  /usr/local/lib/qt5/./libQt5Sql.so.1.1 1f6202947000
> 1f6202d95000 rlib 01
> 0  /usr/local/lib/qt5/./libQt5WebKitWidgets.so.1.1
> 1f62346b7000 1f62351a3000 rlib 04
> 0  /usr/local/lib/qt5/./libQt5Widgets.so.1.1 1f61bad0b000
> 1f61bb538000 rlib 01
> 0  /usr/local/lib/qt5/./libQt5XmlPatterns.so.1.1 1f61e10ce000
> 1f61e3896000 rlib 02
> 0  /usr/local/lib/qt5/./libQt5WebKit.so.1.1 1f62491e4000
> 1f6249ad9000 rlib 08
> 0  /usr/local/lib/qt5/./libQt5Gui.so.1.1 1f61ecf71000
> 1f61ed4e3000 rlib 08
> 0  /usr/local/lib/qt5/./libQt5Network.so.1.1 1f621da8d000
> 1f621e33e000 rlib 018
> 0  /usr/local/lib/qt5/./libQt5Core.so.1.1 1f61bdd5d000
> 1f61be28b000 rlib 019
> 0  /usr/local/lib/libestdc++.so.17.0 1f62560ad000
> 1f62564d5000 rlib 046   0  /usr/lib/libm.so.9.0
> 1f61e8994000 1f61e8e5d000 rlib 03
> 0  /usr/lib/libc.so.85.0 1f61ba3bf000 1f61ba7d1000 rlib
> 046   0  /usr/lib/libpthread.so.21.0 1f6263787000
> 1f6263bd4000 rlib 01   0  /usr/local/lib/libpulse.so.5.0
> 1f61d716c000 1f61d7614000 rlib 08
> 0  /usr/X11R6/lib/libGL.so.16.0 1f626a6b2000 1f626aac4000
> rlib 09   0  /usr/X11R6/lib/libXext.so.13.0 1f61f8009000
> 1f61f8542000 rlib 014   0  /usr/X11R6/lib/libX11.so.16.1
> 1f6266ef6000 1f6267331000 rlib 02
> 0  /usr/local/lib/libxslt.so.3.8 1f61ea815000
> 1f61eac2a000 rlib 013   0  /usr/lib/libz.so.5.0
> 1f61dcc4 1f61dd13e000 rlib 021
> 0  /usr/local/lib/libiconv.so.6.0 1f624c80f000
> 1f624cd71000 rlib 03   0  /usr/local/lib/libxml2.so.15.1
> 1f61e95e9000 1f61e9b6f000 rlib 02
> 0  /usr/local/lib/libgio-2.0.so.4200.2 1f61ab139000
> 1f61ab546000 rlib 02
> 0  /usr/local/lib/libgstapp-1.0.so.2.0 1f628ccc5000
> 1f628d0ef000 rlib 02
> 0  /usr/local/lib/libgstpbutils-1.0.so.2.0 1f61a7f8b000
> 1f61a8413000 rlib 03
> 0  /usr/local/lib/libgstvideo-1.0.so.2.0 1f6203045000
> 1f6203498000 rlib 03
> 0  /usr/local/lib/libgstaudio-1.0.so.2.0 1f61e7dc7000
> 1f61e8228000 rlib 07
> 0  /usr/local/lib/libgstbase-1.0.so.2.0 1f61cbfd2000
> 1f61cc4f3000 rlib 08
> 0  /usr/local/lib/libgstreamer-1.0.so.2.0 1f61ddcb8000
> 1f61de109000 rlib 011
> 0  /usr/local/lib/libgobject-2.0.so.4200.2 1f61ee82a000
> 1f61eed37000 rlib 016
> 0  /usr/local/lib/libglib-2.0.so.4200.2 1f624eadb000
> 1f624eee5000 rlib 020   0  /usr/local/lib/libintl.so.6.0
> 1f6281f57000 1f6282434000 rlib 02
> 0  /usr/lib/libsqlite3.so.32.0 1f626ed5f000 1f626f41
> rlib 03   0  /usr/local/lib/libicui18n.so.9.0
> 1f61abc9f000 1f61ac241000 rlib 04
> 0  /usr/local/lib/libicuuc.so.9.0 1f625d8d2000
> 1f625f52 rlib 05
> 0  /usr/local/lib/libicudata.so.9.0 1f62a0973000
> 1f62a0db rlib 02
> 0  /usr/local/lib/qt5/libQt5Sensors.so.1.1 1f6274a2
> 1f6274e6 rlib 02
> 0  /usr/local/lib/qt5/libQt5Positioning.so.1.1 1f623c655000
> 1f623cab2000 rlib 01
> 0  /usr/local/lib/qt5/libQt5OpenGL.so.1.1 1f61f23ee000
> 1f61f27f8000 rlib 01
> 0  /usr/X11R6/lib/libXrender.so.6.0 1f61c996d000
> 1f61c9da7000 rlib 01   0  /usr/local/lib/libjpeg.so.67.0
> 1f628ac51000 1f628b081000 rlib 02
> 0  /usr/local/lib/libpng.so.17.2 1f61d56bd000
> 1f61d5b1b000 rlib 01   0  /usr/local/lib/libwebp.so.2.1
> 1f620c804000 1f620d012000 rlib 01
> 0  /usr/local/lib/qt5/libQt5Quick.so.1.1 1f6256a4200

Re: www/otter-browser crash on startup net/libproxy / x11/qt5 related?

2016-03-30 Thread Stuart Henderson
On 2016/03/30 15:49, Adam Wolk wrote:
> Roughly I'm interested if anyone else can confirm that they get otter
> crashing on startup by default.

FWIW it's starting OK for me, with a recently updated pkg snap.
I'm not seeing any qt4 libraries being pulled in:

$ ldd /usr/local/bin/otter-browser 
/usr/local/bin/otter-browser:
StartEnd  Type Open Ref GrpRef Name
1f5fa480 1f5fa50a6000 exe  20   0  
/usr/local/bin/otter-browser
1f6263008000 1f626348c000 rlib 01   0  
/usr/local/lib/qt5/./libQt5DBus.so.1.1
1f628ee73000 1f628f36a000 rlib 01   0  
/usr/local/lib/qt5/./libQt5Multimedia.so.1.1
1f6228921000 1f6228d94000 rlib 02   0  
/usr/local/lib/qt5/./libQt5PrintSupport.so.1.1
1f6290c0e000 1f6291245000 rlib 01   0  
/usr/local/lib/qt5/./libQt5Script.so.1.1
1f627b9b7000 1f627bdfa000 rlib 03   0  
/usr/local/lib/qt5/./libQt5Sql.so.1.1
1f6202947000 1f6202d95000 rlib 01   0  
/usr/local/lib/qt5/./libQt5WebKitWidgets.so.1.1
1f62346b7000 1f62351a3000 rlib 04   0  
/usr/local/lib/qt5/./libQt5Widgets.so.1.1
1f61bad0b000 1f61bb538000 rlib 01   0  
/usr/local/lib/qt5/./libQt5XmlPatterns.so.1.1
1f61e10ce000 1f61e3896000 rlib 02   0  
/usr/local/lib/qt5/./libQt5WebKit.so.1.1
1f62491e4000 1f6249ad9000 rlib 08   0  
/usr/local/lib/qt5/./libQt5Gui.so.1.1
1f61ecf71000 1f61ed4e3000 rlib 08   0  
/usr/local/lib/qt5/./libQt5Network.so.1.1
1f621da8d000 1f621e33e000 rlib 018   0  
/usr/local/lib/qt5/./libQt5Core.so.1.1
1f61bdd5d000 1f61be28b000 rlib 019   0  
/usr/local/lib/libestdc++.so.17.0
1f62560ad000 1f62564d5000 rlib 046   0  
/usr/lib/libm.so.9.0
1f61e8994000 1f61e8e5d000 rlib 03   0  
/usr/lib/libc.so.85.0
1f61ba3bf000 1f61ba7d1000 rlib 046   0  
/usr/lib/libpthread.so.21.0
1f6263787000 1f6263bd4000 rlib 01   0  
/usr/local/lib/libpulse.so.5.0
1f61d716c000 1f61d7614000 rlib 08   0  
/usr/X11R6/lib/libGL.so.16.0
1f626a6b2000 1f626aac4000 rlib 09   0  
/usr/X11R6/lib/libXext.so.13.0
1f61f8009000 1f61f8542000 rlib 014   0  
/usr/X11R6/lib/libX11.so.16.1
1f6266ef6000 1f6267331000 rlib 02   0  
/usr/local/lib/libxslt.so.3.8
1f61ea815000 1f61eac2a000 rlib 013   0  
/usr/lib/libz.so.5.0
1f61dcc4 1f61dd13e000 rlib 021   0  
/usr/local/lib/libiconv.so.6.0
1f624c80f000 1f624cd71000 rlib 03   0  
/usr/local/lib/libxml2.so.15.1
1f61e95e9000 1f61e9b6f000 rlib 02   0  
/usr/local/lib/libgio-2.0.so.4200.2
1f61ab139000 1f61ab546000 rlib 02   0  
/usr/local/lib/libgstapp-1.0.so.2.0
1f628ccc5000 1f628d0ef000 rlib 02   0  
/usr/local/lib/libgstpbutils-1.0.so.2.0
1f61a7f8b000 1f61a8413000 rlib 03   0  
/usr/local/lib/libgstvideo-1.0.so.2.0
1f6203045000 1f6203498000 rlib 03   0  
/usr/local/lib/libgstaudio-1.0.so.2.0
1f61e7dc7000 1f61e8228000 rlib 07   0  
/usr/local/lib/libgstbase-1.0.so.2.0
1f61cbfd2000 1f61cc4f3000 rlib 08   0  
/usr/local/lib/libgstreamer-1.0.so.2.0
1f61ddcb8000 1f61de109000 rlib 011   0  
/usr/local/lib/libgobject-2.0.so.4200.2
1f61ee82a000 1f61eed37000 rlib 016   0  
/usr/local/lib/libglib-2.0.so.4200.2
1f624eadb000 1f624eee5000 rlib 020   0  
/usr/local/lib/libintl.so.6.0
1f6281f57000 1f6282434000 rlib 02   0  
/usr/lib/libsqlite3.so.32.0
1f626ed5f000 1f626f41 rlib 03   0  
/usr/local/lib/libicui18n.so.9.0
1f61abc9f000 1f61ac241000 rlib 04   0  
/usr/local/lib/libicuuc.so.9.0
1f625d8d2000 1f625f52 rlib 05   0  
/usr/local/lib/libicudata.so.9.0
1f62a0973000 1f62a0db rlib 02   0  
/usr/local/lib/qt5/libQt5Sensors.so.1.1
1f6274a2 1f6274e6 rlib 02   0  
/usr/local/lib/qt5/libQt5Positioning.so.1.1
1f623c655000 1f623cab2000 rlib 01   0  
/usr/local/lib/qt5/libQt5OpenGL.so.1.1
1f61f23ee000 1f61f27f8000 rlib 01   0  
/usr/X11R6/lib/libXrender.so.6.0
1f61c996d000 1f61c9da7000 rlib 01   0  
/usr/local/lib/libjpeg.so.67.0
1f628ac51000 1f628b081000 rlib 02   0  
/usr/local/lib/libpng.so.17.2
1f61d56bd000 1f61d5b1b000 rlib 01   0  
/usr/local/lib/libwebp.so.2.1
1f620c804000 1f620

www/otter-browser crash on startup net/libproxy / x11/qt5 related?

2016-03-30 Thread Adam Wolk

Otter browser is experiencing crashes on startup on my amd64 -current
laptop. The backtrace suggest libproxy and upstream otter suggested
that this is a known issue at least on Linux systems which have
libproxy-kde installed as they tend to pull in both qt versions (4 & 5)

Upstream provided a backlog chat with the qt upstream:
 http://wklej.org/id/2190844/

which suggests that libproxy is used by qt since 5.5 and they suggest
building qt without it (lol).

I'm not sure which change exactly started killing otter on startup. I
did have a working browser 100% around the time it was bumped to the
new beta (2 months, 3 weeks ago).

The biggest suspects so far are:
 - bump to qt 5.5.1 3 weeks 3 days ago by zhuk@
 - enabling kde support by aja@ 2 months 1 week ago (not likely as it's
   flavour only?)

Here is the backtrace I get from otter:

https://gist.github.com/mulander/ef25ad07e15cbe8a00b8f9738abb8e7f

Workaround from upstream proving that otter starts up and works
correctly with disabled system proxy:

cat ~/.config/otter/otter.conf
[Network]
ProxyMode=noproxy

Roughly I'm interested if anyone else can confirm that they get otter
crashing on startup by default. Did anyone notice libproxy
crashesh in other qt5 apps? Potentially also discussing if we should
build qt without the -no-libproxy flag?

Regards,
Adam