xorg with i915kms crashes with GLSL compile failure when xsane starts

[tech-lists]

Hi,

I'm not sure whether this should go here or should I raise a bug or 
directly raise the issue with xorg?


This almost exact bug (xorg/i915kms) was patched/resolved in 2016 on
debian according to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834054
my issue is slightly different in that I'm using FreeBSD and it happens only 
when xsane starts and regardless of whether the scanner is even plugged in.


context:

12.0-STABLE r346338 GENERIC amd64

packages installed via pkg from default freebsd repos
nothing xorg related has been manually defined

drm-kmod-g20181126 (which has installed
drm-fbsd12.0-kmod-4.16.g20190305)
x11/xorg
x11/mate
graphics/xsane

The machine itself is quite old (c. 2010) but xorg/i915kms works fine on it
otherwise for stuff like firefox/libreoffice. It has 8GB ram and runs zfs. 
The crash happens shortly after xsane is started.


xorg error:

0:13(14): error: operands to arithmetic operators must be numeric
0:13(13): error: operands to arithmetic operators must be numeric

[  1338.766] Program source:
#define ATLAS_DIM_INV 0.0009765625
attribute vec2 primitive;
attribute vec2 source;
varying vec2 glyph_pos;
uniform vec2 fill_offset;
uniform vec2 fill_size_inv;
varying vec2 fill_pos;
uniform vec4 v_matrix;
void main() {
  gl_Position.xy = primitive.xy * v_matrix.xz + v_matrix.yw;
  gl_Position.zw = vec2(0.0,1.0);
  glyph_pos = source.xy * ATLAS_DIM_INV;
  fill_pos = (fill_offset + primitive.xy + pos) * fill_size_inv;
}
[  1338.766] (EE) 
Fatal server error:

[  1338.766] (EE) GLSL compile failure
[  1338.766] (EE) 
[  1338.766] (EE) 
Please consult the The X.Org Foundation support 
at http://wiki.x.org

for help.
[  1338.766] (EE) Please also check the log file at
"/var/log/Xorg.0.log" for additional information.
[  1338.767] (EE) 
[  1338.767] (II) AIGLX: Suspending AIGLX clients for VT switch

[  1338.772] (EE) Server terminated with error (1). Closing log file.

in the meantime I'm going to try building xorg/xsane from the ports

thanks,
--
J.


signature.asc
Description: PGP signature

Re: ltmain.sh not found

[@lbutlr]

On 25 Apr 2019, at 07:14, Willem Offermans  wrote:
> When I have time, I will dig into poudriere. I assume there is 
> documentation/tutorial around that will get me going.
> The man pages will also be helpful.

Loos like



and 



might be the places to start.

(I am also on postmaster and am at least partially, if not mostly, posting this 
to the list so I have an archive of the links :)


-- 
I AM ZOMBOR! (kelly) ZOMBOR!


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: PHP 7.2: SIGSEGV in OpenSSL

[Marcel Bonnet]

Hi.
I installed more extensions and noticed that ldap.so, indeed must follow
openssl to avoid Segmentation Fault.

mod_php73-7.3.4

php73-7.3.4

php73-bcmath-7.3.4

php73-bz2-7.3.4

php73-ctype-7.3.4

php73-curl-7.3.4

php73-dom-7.3.4

php73-exif-7.3.4

php73-extensions-1.0

php73-fileinfo-7.3.4

php73-filter-7.3.4

php73-gd-7.3.4

php73-gettext-7.3.4

php73-hash-7.3.4

php73-iconv-7.3.4

php73-intl-7.3.4

php73-json-7.3.4

php73-ldap-7.3.4

php73-mbstring-7.3.4

php73-opcache-7.3.4

php73-openssl-7.3.4

php73-pdo-7.3.4

php73-pdo_mysql-7.3.4

php73-pdo_sqlite-7.3.4

php73-phar-7.3.4

php73-posix-7.3.4

php73-session-7.3.4

php73-simplexml-7.3.4

php73-soap-7.3.4

php73-sockets-7.3.4

php73-sqlite3-7.3.4

php73-tokenizer-7.3.4

php73-xml-7.3.4

php73-xmlreader-7.3.4

php73-xmlwriter-7.3.4

php73-zip-7.3.4

php73-zlib-7.3.4



extension=session.so

extension=fileinfo.so

extension=simplexml.so

extension=ctype.so

extension=mbstring.so

extension=tokenizer.so

extension=filter.so

extension=xmlwriter.so

extension=gd.so

extension=gettext.so

extension=iconv.so

extension=exif.so

extension=zlib.so

extension=bz2.so

extension=openssl.so

; LDAP and CURL must be loaded after openssl

extension=ldap.so

extension=curl.so

extension=dom.so

extension=hash.so

extension=xmlreader.so

extension=bcmath.so

extension=soap.so

extension=pdo.so

extension=pdo_mysql.so

extension=pdo_sqlite.so

extension=sockets.so

extension=xml.so

; additional extension(s) not known by fixphpextorder.sh

extension=intl.so

extension=json.so

extension=posix.so

extension=sqlite3.so

extension=zip.so

extension=phar.so

On Thu, 25 Apr 2019 at 17:07, Marcel Bonnet  wrote:

>
>
> On Wed, 24 Apr 2019 at 18:03, Stefan Bethke  wrote:
>
>> Am 24.04.2019 um 22:50 schrieb Mathieu Arnold :
>>
>> On Wed, Apr 24, 2019 at 06:34:06PM +0200, Stefan Bethke wrote:
>>
>> Am 23.04.2019 um 18:01 schrieb Kurt Jaeger :
>>
>> Hi!
>>
>> Did you find a solution? Please let me know.
>>
>>
>> There's a well-known problem in the sequence in which php modules
>> are loaded. I don't know if this is the case here as well,
>> but that's what we do:
>>
>> fetch -o fixphpextorder \
>>   https://people.freebsd.org/~ohauer/scripts/fixphpextorder.sh
>> chmod 755 fixphpextorder
>>
>> cd /usr/local/etc/php
>> cat ext-*ini > extensions.ini
>> fixphpextorder
>> mv extensions.ini.new extensions.ini
>> rm ext-*ini
>>
>> Please test and report if it fixes the problem.
>>
>>
>> Thanks Kurt, it appears to fix (or at least work around) the problem.
>>
>> Why is the default load order broken? Why does it not affect everyone?
>>
>> I moved all the individual inis into a bak subdir, and now only have an
>> extensions.ini.
>>
>> If I understand correctly, mod_php/PHP reads the individual inis in
>> order. Why aren’t they in the right order? Can this be fixed in the ports
>> for the PHP modules?
>>
>>
>> Could you give the order that works for you, so that we can try to
>> figure out which module is making it break ?
>>
>> Because there is no "right" order, there is an order that can work for
>> most people, and from time to time, two libs have conflicting symbols,
>> but it is not possible to detect that.  So I made up an order that
>> should be ok, but some time is not.
>>
>>
>> This is the order I’m actively using now:
>> $ cat extensions.ini
>> extension=session.so
>> extension=fileinfo.so
>> extension=ldap.so
>> extension=simplexml.so
>> extension=ctype.so
>> extension=mbstring.so
>> extension=tokenizer.so
>> extension=filter.so
>> extension=pgsql.so
>> extension=mcrypt.so
>> extension=gd.so
>> extension=gettext.so
>> extension=iconv.so
>> extension=zlib.so
>> extension=curl.so
>> extension=xmlrpc.so
>> extension=bz2.so
>> extension=openssl.so
>> extension=dom.so
>> extension=hash.so
>> extension=wddx.so
>> extension=memcache.so
>> extension=soap.so
>> extension=pdo.so
>> extension=pdo_mysql.so
>> extension=mysqli.so
>> extension=sockets.so
>> extension=xml.so
>> ; additional extension(s) not known by fixphpextorder.sh
>> extension=intl.so
>> extension=json.so
>> extension=sqlite3.so
>> extension=zip.so
>> extension=memcached.so
>> extension=pdo_pgsql.so
>> extension=phar.so
>>
>> This is the order as installed by the ports (at least I think that’s the
>> order PHP will read the files):
>> $ cat $(echo bak/*.ini|sort)
>> zend_extension=opcache.so
>> extension=session.so
>> extension=bz2.so
>> extension=ctype.so
>> extension=curl.so
>> extension=dom.so
>> extension=fileinfo.so
>> extension=filter.so
>> extension=gd.so
>> extension=gettext.so
>> extension=hash.so
>> extension=iconv.so
>> extension=intl.so
>> extension=json.so
>> extension=ldap.so
>> extension=mbstring.so
>> extension=mcrypt.so
>> extension=mysqli.so
>> extension=openssl.so
>> extension=pdo.so
>> extension=pgsql.so
>> extension=simplexml.so
>> extension=soap.so
>> extension=sockets.so
>> extension=sqlite3.so
>> extension=tokenizer.so
>> extension=xml.so
>> extension=zip.so
>> extension=zlib.so
>> extension=m

Re: PHP 7.2: SIGSEGV in OpenSSL

[Marcel Bonnet]

On Wed, 24 Apr 2019 at 18:03, Stefan Bethke  wrote:

> Am 24.04.2019 um 22:50 schrieb Mathieu Arnold :
>
> On Wed, Apr 24, 2019 at 06:34:06PM +0200, Stefan Bethke wrote:
>
> Am 23.04.2019 um 18:01 schrieb Kurt Jaeger :
>
> Hi!
>
> Did you find a solution? Please let me know.
>
>
> There's a well-known problem in the sequence in which php modules
> are loaded. I don't know if this is the case here as well,
> but that's what we do:
>
> fetch -o fixphpextorder \
>   https://people.freebsd.org/~ohauer/scripts/fixphpextorder.sh
> chmod 755 fixphpextorder
>
> cd /usr/local/etc/php
> cat ext-*ini > extensions.ini
> fixphpextorder
> mv extensions.ini.new extensions.ini
> rm ext-*ini
>
> Please test and report if it fixes the problem.
>
>
> Thanks Kurt, it appears to fix (or at least work around) the problem.
>
> Why is the default load order broken? Why does it not affect everyone?
>
> I moved all the individual inis into a bak subdir, and now only have an
> extensions.ini.
>
> If I understand correctly, mod_php/PHP reads the individual inis in order.
> Why aren’t they in the right order? Can this be fixed in the ports for the
> PHP modules?
>
>
> Could you give the order that works for you, so that we can try to
> figure out which module is making it break ?
>
> Because there is no "right" order, there is an order that can work for
> most people, and from time to time, two libs have conflicting symbols,
> but it is not possible to detect that.  So I made up an order that
> should be ok, but some time is not.
>
>
> This is the order I’m actively using now:
> $ cat extensions.ini
> extension=session.so
> extension=fileinfo.so
> extension=ldap.so
> extension=simplexml.so
> extension=ctype.so
> extension=mbstring.so
> extension=tokenizer.so
> extension=filter.so
> extension=pgsql.so
> extension=mcrypt.so
> extension=gd.so
> extension=gettext.so
> extension=iconv.so
> extension=zlib.so
> extension=curl.so
> extension=xmlrpc.so
> extension=bz2.so
> extension=openssl.so
> extension=dom.so
> extension=hash.so
> extension=wddx.so
> extension=memcache.so
> extension=soap.so
> extension=pdo.so
> extension=pdo_mysql.so
> extension=mysqli.so
> extension=sockets.so
> extension=xml.so
> ; additional extension(s) not known by fixphpextorder.sh
> extension=intl.so
> extension=json.so
> extension=sqlite3.so
> extension=zip.so
> extension=memcached.so
> extension=pdo_pgsql.so
> extension=phar.so
>
> This is the order as installed by the ports (at least I think that’s the
> order PHP will read the files):
> $ cat $(echo bak/*.ini|sort)
> zend_extension=opcache.so
> extension=session.so
> extension=bz2.so
> extension=ctype.so
> extension=curl.so
> extension=dom.so
> extension=fileinfo.so
> extension=filter.so
> extension=gd.so
> extension=gettext.so
> extension=hash.so
> extension=iconv.so
> extension=intl.so
> extension=json.so
> extension=ldap.so
> extension=mbstring.so
> extension=mcrypt.so
> extension=mysqli.so
> extension=openssl.so
> extension=pdo.so
> extension=pgsql.so
> extension=simplexml.so
> extension=soap.so
> extension=sockets.so
> extension=sqlite3.so
> extension=tokenizer.so
> extension=xml.so
> extension=zip.so
> extension=zlib.so
> extension=memcache.so
> extension=memcached.so
> extension=pdo_mysql.so
> extension=pdo_pgsql.so
> extension=phar.so
> extension=wddx.so
> extension=xmlrpc.so
>
> This is the contents of bak (the former contents of /usr/local/etc/php):
> $ ls bak
> ext-10-opcache.ini ext-20-intl.ini ext-20-sqlite3.ini
> ext-18-session.ini ext-20-json.ini ext-20-tokenizer.ini
> ext-20-bz2.ini ext-20-ldap.ini ext-20-xml.ini
> ext-20-ctype.ini ext-20-mbstring.ini ext-20-zip.ini
> ext-20-curl.ini ext-20-mcrypt.ini ext-20-zlib.ini
> ext-20-dom.ini ext-20-mysqli.ini ext-30-memcache.ini
> ext-20-fileinfo.ini ext-20-openssl.ini ext-30-memcached.ini
> ext-20-filter.ini ext-20-pdo.ini ext-30-pdo_mysql.ini
> ext-20-gd.ini ext-20-pgsql.ini ext-30-pdo_pgsql.ini
> ext-20-gettext.ini ext-20-simplexml.ini ext-30-phar.ini
> ext-20-hash.ini ext-20-soap.ini ext-30-wddx.ini
> ext-20-iconv.ini ext-20-sockets.ini ext-30-xmlrpc.ini
>
>
> These are the PHP packages I have installed, minus the web apps:
> $ pkg info -r php72
> php72-7.2.17_2:
> php72-xml-7.2.17_2
> php72-hash-7.2.17_2
> php72-session-7.2.17_2
> php72-openssl-7.2.17_2
> php72-xmlrpc-7.2.17_2
> php72-mysqli-7.2.17_2
> php72-mbstring-7.2.17_2
> php72-phar-7.2.17_2
> php72-ctype-7.2.17_2
> php72-tokenizer-7.2.17_2
> php72-json-7.2.17_2
> php72-filter-7.2.17_2
> php72-gd-7.2.17_2
> php72-zlib-7.2.17_2
> php72-zip-7.2.17_2
> php72-bz2-7.2.17_2
> php72-iconv-7.2.17_2
> php72-fileinfo-7.2.17_2
> php72-pgsql-7.2.17_2
> php72-opcache-7.2.17_2
> php72-wddx-7.2.17_2
> php72-simplexml-7.2.17_2
> php72-dom-7.2.17_2
> php72-pecl-mcrypt-1.0.2
> php72-soap-7.2.17_2
> php72-ldap-7.2.17_2
> php72-curl-7.2.17_2
> php72-sqlite3-7.2.17_2
> php72-pdo-7.2.17_2
> php72-memcache-4.0.3
> php72-pecl-memcached-3.1.3
> php72-sockets-7.2.17_2
> php72-intl-7.2.17_2
> php72-gettext-7.2.17_2

Re: What is procedure to add new USES makefile (Mk/Uses/name.mk)?

[Mathieu Arnold]

On Thu, Apr 25, 2019 at 09:40:37PM +0300, Lev Serebryakov wrote:
> 
>  I want to swtich subversion port selection from custom variable to
> DEFAULT_VERSIONS and USES infrastructure. Now it is broken for at least
> two ports, and may be for more.
> 
>  Does I need additional review for my changes, as it touches not only
> personal port(s) but infrastructure makefiles?

Everything in Mk must be reviewed, create reviews on phabricator,
portmgr will be poked about it.

-- 
Mathieu Arnold


signature.asc
Description: PGP signature

What is procedure to add new USES makefile (Mk/Uses/name.mk)?

[Lev Serebryakov]

 I want to swtich subversion port selection from custom variable to
DEFAULT_VERSIONS and USES infrastructure. Now it is broken for at least
two ports, and may be for more.

 Does I need additional review for my changes, as it touches not only
personal port(s) but infrastructure makefiles?

-- 
// Lev Serebryakov



signature.asc
Description: OpenPGP digital signature

Re: ltmain.sh not found

[Willem Offermans]

Dear FreeBSD friends,

No, I have not yet considered using poudriere.

I’m using portmaster for years now and I was too lazy to look for a 
better/another tool.

When I have time, I will dig into poudriere. I assume there is 
documentation/tutorial around that will get me going.
The man pages will also be helpful.

Thank you for your suggestion.



Wiel Offermans
wil...@offermans.rompen.nl




> On 25 Apr 2019, at 14:58, Andreas Nilsson  wrote:
> 
> 
> 
> On Thu, Apr 25, 2019 at 2:28 AM Kevin Oberman  > wrote:
> On Wed, Apr 24, 2019 at 9:05 AM Christoph Moench-Tegeder  >
> wrote:
> 
> > ## Willem Offermans (wil...@offermans.rompen.nl 
> > ):
> >
> > > Unfortunately it is probably not gawk in my case, which causes trouble.
> > > However, your response indicates that the problem will be solved after I
> > > have updated/reinstalled the guilty one.
> >
> > There's sysutils/bsdadminscripts, which provides pkg_libchk: that's a
> > tool for checking if any port misses a shared library. It has been
> > rather helpful back when I was using portupgrade...
> >
> > Regards,
> > Christoph
> >
> 
> I believe bsdadminscripts has been withdrawn. You should use "pkg check -B"
> to check.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com 
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> 
> 
> Have you considered using poudriere to build your packages? It usually avoids 
> these types of failures.
> 
> Best regards
> Andreas 

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
databases/mysql-connector-odbc  | 5.3.4   | 8.0.16
+-+
emulators/mame  | 0.200   | mame0209
+-+
emulators/mess  | 0.200   | mame0209
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"