Bug#917896: Method of setting WheelEmulation button, or ScrollButton by user not documented or does not exist.

2018-12-31 Thread Roger Gammans 
Source: libinput
Severity: important
Tags: a11y

(I've tagged this as a11y as it's part of my RSI mitigation - using
an actuall scroll wheel is physically painful, so tagged as important as 
this bug makes using the machine painful)

In stretch I used to run these two commands at login to set the up
a trackball so that I could avoid needing to use the scroll wheel this
worked very well for me.

xinput set-prop "Logitech M570" "Evdev Wheel Emulation" 1
xinput set-prop "Logitech M570" "Evdev Wheel Emulation Button" 8

In buster the wayland compositor sits between X and evdev/libinput and
mask the actuall device from xinput. So it can't be used to make these
settings.

The existance of these settings is still documented in 'man 4 libinput'
and 'man 4 evdev', but no command line or other mechanism to actually
set these values is documented (except Xorg.conf).

I really like to be able to do it on the commandline as an ordinary user,
so I can swtich it on or off in pair programming situations.

I'm using the gnome destktop environment, so it possible the setting
should be part of one of the Gnome packages (and in other DEs as well
presumably)  in the new scheme things, in which case I'm sorry if
I've raised the bug against the wrong package.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.18.0-3-amd64 (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF8), 
LANGUAGE=en_GB:en (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#917896: Acknowledgement (Method of setting WheelEmulation button, or ScrollButton by user not documented or does not exist.)

2018-12-31 Thread Roger Gammans 
Having spend three days without luck looking for settings, I have
another look in dconf after sending the report  and find :

 org/gnome/desktop/peripherals/scroll-wheel-emulation-button

So It a documentation issue at worst..

-- 
Roger Gammans 
Gamma Science Ltd. (GB Nr. 07356014 )

Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

2018-12-31 Thread Alexander Meyer 
* Thomas Dickey  [2018-12-30 23:14]:

> On Sun, Dec 30, 2018 at 10:15:53PM +0100, Sven Joachim wrote:
>> On 2018-12-30 18:26 +0100, Alexander Meyer wrote:
>>> So the segfault only happens with that fonts.conf.
>> 
>> Thanks, that explains why others did not see it - and possibly also why
>> I could still reproduce #916349 in xterm 340, as I have my own
>> fonts.conf, albeit a much shorter and simpler one than yours.
>> 
>> Alas, with your file (saved as /tmp/fonts.conf) xterm does not even start
>> here, although I have fonts-noto-mono and fonts-noto-color-emoji
>> installed:
> 
> If xterm sees the latter, it will not start.  That's a problem that can
> only be solved by modifying Xft.  Not xterm.
> 
> But the short term goal is to get xterm working as well as feasible with
> Xft before moving on to see what can be done to make Xft handle the
> color bitmap fonts.
> 
> I'm looking for details on how to reproduce the segmentation violation
> which was reported.
>  
>> ,
>> | $ FONTCONFIG_FILE=/tmp/foo/fonts.conf xterm -fa 'Noto Mono'  
> 
> Back up a step: with that fonts.conf, I get no result for
>   fc-match 'Noto Mono'
> 
> while without it, I do get a match.  A quick look at strace tells me
> that setting FONTCONFIG_FILE eliminates a lot of the normal configuration
> information, and probably isn't what you want to do in reproducing the
> problem.

For the record: I disabled/enabled my fonts.conf by moving it out of
~/.config/fontconfig/ and then back inside. I did not set FONTCONFIG_FILE.

Also, as described in my original report, the segfault is not limited to
"Noto Mono" but seems to happen with any other font, too. (I've randomly
tried a few from my fc-list.)

>> | xterm: cannot match normal font "Noto Mono"
>> | xterm: Selected font has no non-zero height for ISO-8859-1 encoding
> 
> ...and because there's no match, for _this_ case I get the same failure.
> 
> However, that's not a bug (in xterm), but a problem with configuration.
> 
>> So I am a bit at a loss here.  And I am definitely not a an expert on
>> fontconfig (or fonts in general) either.
> 
> I'd like to see the XFT_DEBUG information from the known broken scenario.
> If it tells me that Xft is still loading the color-noto font, there's
> probably nothing that I can do to address that in xterm.

Please find attached the gzipped output of

$ XFT_DEBUG=1023 xterm -fa 'Noto Mono'

with xterm 341. All output happens directly after startup, there's no
output after issuing the command that displays the character that causes
the segfault.

Best
Alex


xterm-341-XFT_DEBUG_1023.log.gz
Description: application/gzip

Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

2018-12-31 Thread Alexander Meyer 
* Thomas Dickey  [2018-12-31 00:51]:

> On Sun, Dec 30, 2018 at 06:26:44PM +0100, Alexander Meyer wrote:
> ...
>> This is the behaviour I get across xterm versions:
>> (everything with libfontconfig1 2.13.1-2)
>> 
>> fonts.conf enabled:
>> 337: works
>> 338: segfault
>> 340: segfault
>> 341: segfault
> 
> Can you make a backtrace for #341, please?

Here it is:


Reading symbols from /usr/bin/xterm...Reading symbols from 
/usr/lib/debug/.build-id/b8/d462fb6f4969a6a228262ceff981af02a1a4d5.debug...done.
done.
(gdb) run -fa 'Noto Mono'
Starting program: /usr/bin/xterm -fa 'Noto Mono'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x77d662d1 in FcConfigEvaluate (p=0x556f2430, p_pat=0x559dea90, 
kind=kind@entry=FcMatchFont, e=0x0) at fccfg.c:977
(gdb) bt full
#0  0x77d662d1 in FcConfigEvaluate (p=0x556f2430, 
p_pat=0x559dea90, kind=kind@entry=FcMatchFont, e=0x0) at fccfg.c:977
v = {type = FcTypeVoid, u = {s = 0x556f1ad0 " \033oUUU", i = 
1433344720, b = 1433344720, d = 4.6355706220021174e-310, m = 0x556f1ad0, c 
= 0x556f1ad0, f = 0x556f1ad0, 
l = 0x556f1ad0, r = 0x556f1ad0}}
vl = {type = 1433014944, u = {s = 0x0, i = 0, b = 0, d = 0, m = 0x0, c 
= 0x0, f = 0x0, l = 0x0, r = 0x0}}
vr = {type = 1436412560, u = {s = 0x0, i = 0, b = 0, d = 0, m = 0x0, c 
= 0x0, f = 0x0, l = 0x0, r = 0x0}}
vle = 
vre = 
m = 
str = 
op = 
buf1 = {u = {d = 0, i = 0, l = 0, 
c = 
"\000\000\000\000\000\000\000\000\200\032oUUU\000\000\270\022jUUU\000\000\000\000\000\000\000\000\000\000\220\352\235UUU",
 '\000' , 
"\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000\060\032oUUU\000\000\320\022jUUU\000\000\000\000\000\000\000\000\000\000\220\352\235UUU",
 '\000' , 
"\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000\340\031oUUU\000\000\350\022jUUU\000\000\000\000\000\000\000\000\000\000\220\352\235UUU",
 '\000' , 
"\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000"...}}
buf2 = {u = {d = 0, i = 0, l = 0, 
c = 
"\000\000\000\000\000\000\000\000@\031oUUU\000\000\030\023jUUU\000\000\000\000\000\000\000\000\000\000\025",
 '\000' , "\a\000\000\000\000\000\000\000 
\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000\020\300aUUU\000\000\017\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\260\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\060",
 '\000' , "[\000\000\000w", '\000' , 
"n\000\000\000|\000\000\000\t\000\000\000\000\000\000\000\017\000\000\000\000\000\000\000\025",
 '\000' , "\260\377\377\377\377\377\377\377"...}}
#1  0x77d66418 in FcConfigEvaluate (p=p@entry=0x556f2430, 
p_pat=p_pat@entry=0x559dea90, kind=kind@entry=FcMatchFont, 
e=e@entry=0x55681218) at fccfg.c:1003
m = {xx = 1.4821969375237396e-323, xy = 6.9533490418283141e-310, yx = 
1.4821969375237396e-323, yy = 1}
xx = 
yy = 
xy = 
yx = 
v = {type = FcTypeMatrix, u = {s = 0x3 , i = 3, b = 3, d = 1.4821969375237396e-323, m = 0x3, c = 0x3, f = 
0x3, l = 0x3, r = 0x3}}
vl = {type = FcTypeVoid, u = {s = 0x556f24b0 "Noto Color Emoji", i 
= 1433347248, b = 1433347248, d = 4.6355706221270172e-310, m = 0x556f24b0, 
c = 0x556f24b0, f = 0x556f24b0, 
l = 0x556f24b0, r = 0x556f24b0}}
vr = {type = FcTypeString, u = {s = 0x77d660a4 
 
"\205\300\017\224\300\017\266\300\351\267\375\377\377L\211\346H\211\327\350\364=",
 i = -136945500, b = -136945500, 
d = 6.9533490418283141e-310, m = 0x77d660a4 
, c = 0x77d660a4 , f = 
0x77d660a4 , 
l = 0x77d660a4 , r = 0x77d660a4 
}}
vle = 
vre = 
m = 
str = 
op = FcOpMatrix
buf1 = {u = {d = 4.6355706048940074e-310, i = 1432998448, l = 
93824993579568, 
c = 
"0\322iUUU\000\000\002\000\000\000\000\000\000\000\060\026jUUU\000\000\354c\326\367\377\177\000\000\000\000\000\000\000\000\000\000\003\000\000\000\000\000\000\000\003",
 '\000' , "\a\000\000\000\000\000\000\000 
\000\000\000\000\000\000\000\002\000\000\000UU\000\000\020\300aUUU\000\000\017\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\260\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\060",
 '\000' , 
"\f\341\327\367\377\177\000\000\000\000\000\000\257\060\000\000\000\240\316\365\301\035?\376\003\000\000\000\000\000\000\000\256\340\327\367\377\177\000\000\200\326\377\377\264\060\000\000\000"...}}
buf2 = {u = {d = 4.6355706320533889e-310, i = 1433548160, l = 
93824994129280, 
c = 
"\200\065rUUU\000\000\270\220B\365\377\177\000\000\000\000\000\000\000\000\000\000\362H\327\367\377\177\000\000
 ", '\000' , 
"\a\000\000\000\000\000\000\000\060\000\000\000\000

Processed: [bts-link] source package xkeyboard-config

2018-12-31 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package xkeyboard-config
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #296616 (http://bugs.debian.org/296616)
> # Bug title: xbase-clients: xkbcomp gives warnings
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=21761
> #  * remote status changed: REOPENED -> RESOLVED
> #  * remote resolution changed: (?) -> MOVED
> #  * closed upstream
> tags 296616 + fixed-upstream
Bug #296616 [xkb-data] xbase-clients: xkbcomp gives warnings
Bug #291853 [xkb-data] xkbcomp warns about  having 2 symbols
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 296616 - status-REOPENED
Usertags were: status-REOPENED.
Usertags are now: .
> usertags 296616 + status-RESOLVED resolution-MOVED
There were no usertags set.
Usertags are now: resolution-MOVED status-RESOLVED.
> # remote status report for #296616 (http://bugs.debian.org/296616)
> # Bug title: xbase-clients: xkbcomp gives warnings
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=21761
> #  * remote status changed: REOPENED -> RESOLVED
> #  * remote resolution changed: (?) -> MOVED
> #  * closed upstream
> tags 296616 + fixed-upstream
Bug #296616 [xkb-data] xbase-clients: xkbcomp gives warnings
Bug #291853 [xkb-data] xkbcomp warns about  having 2 symbols
Ignoring request to alter tags of bug #296616 to the same tags previously set
Ignoring request to alter tags of bug #291853 to the same tags previously set
> usertags 296616 - status-REOPENED
Usertags were: resolution-MOVED status-RESOLVED.
Usertags are now: resolution-MOVED status-RESOLVED.
> usertags 296616 + status-RESOLVED resolution-MOVED
Usertags were: status-RESOLVED resolution-MOVED.
Usertags are now: status-RESOLVED resolution-MOVED.
> # remote status report for #483687 (http://bugs.debian.org/483687)
> # Bug title: xkb-data: "grp:alts_toggle" correction patch
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=16164
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> MOVED
> #  * closed upstream
> tags 483687 + fixed-upstream
Bug #483687 [xkb-data] xkb-data: "grp:alts_toggle" correction patch
Bug #463373 [xkb-data] xkb-data: grp:alts_toggle broken
Bug #483683 [xkb-data] xkb-data: "grp:alts_toggle" correction patch
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 483687 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 483687 + status-RESOLVED resolution-MOVED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-MOVED.
> # remote status report for #483687 (http://bugs.debian.org/483687)
> # Bug title: xkb-data: "grp:alts_toggle" correction patch
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=16164
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> MOVED
> #  * closed upstream
> tags 483687 + fixed-upstream
Bug #483687 [xkb-data] xkb-data: "grp:alts_toggle" correction patch
Bug #463373 [xkb-data] xkb-data: grp:alts_toggle broken
Bug #483683 [xkb-data] xkb-data: "grp:alts_toggle" correction patch
Ignoring request to alter tags of bug #483687 to the same tags previously set
Ignoring request to alter tags of bug #463373 to the same tags previously set
Ignoring request to alter tags of bug #483683 to the same tags previously set
> usertags 483687 - status-NEW
Usertags were: status-RESOLVED resolution-MOVED.
Usertags are now: status-RESOLVED resolution-MOVED.
> usertags 483687 + status-RESOLVED resolution-MOVED
Usertags were: status-RESOLVED resolution-MOVED.
Usertags are now: status-RESOLVED resolution-MOVED.
> # remote status report for #483687 (http://bugs.debian.org/483687)
> # Bug title: xkb-data: "grp:alts_toggle" correction patch
> #  * https://bugs.freedesktop.org/show_bug.cgi?id=16164
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> MOVED
> #  * closed upstream
> tags 483687 + fixed-upstream
Bug #483687 [xkb-data] xkb-data: "grp:alts_toggle" correction patch
Bug #463373 [xkb-data] xkb-data: grp:alts_toggle broken
Bug #483683 [xkb-data] xkb-data: "grp:alts_toggle" correction patch
Ignoring request to alter tags of bug #483687 to the same tags previously set
Ignoring request to alter tags of bug #463373 to the same tags previously set
Ignoring request to alter tags of bug #483683 to the same tags previously set
> usertags 483687 - status-NEW
Usertags were: status-RESOLVED resolution-MOVED.
Usertags are now: status-RESOLVED resolution-MOVED.
> usertags 483687 + status-RESOLVED resolution-MOVED
Usertags were: status-RESOLVED resolution-MOVED.
Usertags are now: status-RESOLVED resolution-MOVED.
> # remote status report for #526004 (http://bugs.debian.o

[bts-link] source package xkeyboard-config

2018-12-31 Thread debian-bts-link 
#
# bts-link upstream status pull for source package xkeyboard-config
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#

user debian-bts-l...@lists.debian.org

# remote status report for #296616 (http://bugs.debian.org/296616)
# Bug title: xbase-clients: xkbcomp gives warnings
#  * https://bugs.freedesktop.org/show_bug.cgi?id=21761
#  * remote status changed: REOPENED -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 296616 + fixed-upstream
usertags 296616 - status-REOPENED
usertags 296616 + status-RESOLVED resolution-MOVED

# remote status report for #296616 (http://bugs.debian.org/296616)
# Bug title: xbase-clients: xkbcomp gives warnings
#  * https://bugs.freedesktop.org/show_bug.cgi?id=21761
#  * remote status changed: REOPENED -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 296616 + fixed-upstream
usertags 296616 - status-REOPENED
usertags 296616 + status-RESOLVED resolution-MOVED

# remote status report for #483687 (http://bugs.debian.org/483687)
# Bug title: xkb-data: "grp:alts_toggle" correction patch
#  * https://bugs.freedesktop.org/show_bug.cgi?id=16164
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 483687 + fixed-upstream
usertags 483687 - status-NEW
usertags 483687 + status-RESOLVED resolution-MOVED

# remote status report for #483687 (http://bugs.debian.org/483687)
# Bug title: xkb-data: "grp:alts_toggle" correction patch
#  * https://bugs.freedesktop.org/show_bug.cgi?id=16164
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 483687 + fixed-upstream
usertags 483687 - status-NEW
usertags 483687 + status-RESOLVED resolution-MOVED

# remote status report for #483687 (http://bugs.debian.org/483687)
# Bug title: xkb-data: "grp:alts_toggle" correction patch
#  * https://bugs.freedesktop.org/show_bug.cgi?id=16164
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 483687 + fixed-upstream
usertags 483687 - status-NEW
usertags 483687 + status-RESOLVED resolution-MOVED

# remote status report for #526004 (http://bugs.debian.org/526004)
# Bug title: It would be nice to have italian coder variant in xkb-data
#  * https://bugs.freedesktop.org/show_bug.cgi?id=27448
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 526004 + fixed-upstream
usertags 526004 - status-NEW
usertags 526004 + status-RESOLVED resolution-MOVED

# remote status report for #536006 (http://bugs.debian.org/536006)
# Bug title: rules/*.xml allow unsupported model/layout combinations
#  * https://bugs.freedesktop.org/show_bug.cgi?id=33670
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 536006 + fixed-upstream
usertags 536006 - status-NEW
usertags 536006 + status-RESOLVED resolution-MOVED

# remote status report for #742714 (http://bugs.debian.org/742714)
# Bug title: xkb-data: french Bepo - decimal separator
#  * https://bugs.freedesktop.org/show_bug.cgi?id=76654
#  * remote status changed: NEW -> RESOLVED
#  * remote resolution changed: (?) -> MOVED
#  * closed upstream
tags 742714 + fixed-upstream
usertags 742714 - status-NEW
usertags 742714 + status-RESOLVED resolution-MOVED

thanks

Bug#810548: xserver-xorg-video-radeon: gpu lockup and black screen

2018-12-31 Thread Alexandros Prekates 
Package: xserver-xorg-video-radeon
Version: 1:7.8.0-1+b1
Followup-For: Bug #810548

Dear Maintainer,

I have an radeon HD 5750

In phenomenicaly random moment ,  in frequency of one per day , and usually
while i play in the same time Stellaris (starting it from withing the steam
client)
linux will freeze and screen will become blank .Fans are still operational ,
also i tested another screen but still blank.

/var/log/syslog display hundred times :

ec 31 17:56:28 enous kernel: [20887.723072] radeon :01:00.0: GPU lockup
(current fence id 0x007c89d8 last fence id 0x007c89e0 on ring
0)
Dec 31 17:56:29 enous kernel: [20888.234984] radeon :01:00.0: ring 0
stalled for more than 216576msec
Dec 31 17:56:29 enous kernel: [20888.234987] radeon :01:00.0: GPU lockup
(current fence id 0x007c89d8 last fence id 0x007c89e0 on ring
0)
Dec 31 17:56:29 enous kernel: [20888.746986] radeon :01:00.0: ring 0
stalled for more than 217088msec


*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Juniper PRO [Radeon HD 5750] [1002:68be]

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 4.9.0-7-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-3+deb9u2 (2018-08-13)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 45343 Nov  2 13:41 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 46137 Dec 31 18:19 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 2.931] (--) Log file renamed from "/var/log/Xorg.pid-653.log" to 
"/var/log/Xorg.0.log"
[ 2.933] 
X.Org X Server 1.19.2
Release Date: 2017-03-02
[ 2.933] X Protocol Version 11, Revision 0
[ 2.933] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[ 2.933] Current Operating System: Linux enous 4.9.0-7-amd64 #1 SMP Debian 
4.9.110-3+deb9u2 (2018-08-13) x86_64
[ 2.933] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-7-amd64 
root=UUID=f92aef31-d231-4b0f-8d17-f120b6ec98f5 ro quiet
[ 2.933] Build Date: 03 November 2018  03:09:11AM
[ 2.933] xorg-server 2:1.19.2-1+deb9u5 (https://www.debian.org/support) 
[ 2.933] Current version of pixman: 0.34.0
[ 2.933]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 2.933] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2.933] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 31 18:19:28 
2018
[ 2.937] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 2.938] (==) No Layout section.  Using the first Screen section.
[ 2.938] (==) No screen section available. Using defaults.
[ 2.938] (**) |-->Screen "Default Screen Section" (0)
[ 2.938] (**) |   |-->Monitor ""
[ 2.939] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 2.939] (==) Automatically adding devices
[ 2.939] (==) Automatically enabling devices
[ 2.939] (==) Automatically adding GPU devices
[ 2.939] (==) Max clients allowed: 256, resource mask: 0x1f
[ 2.942] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 2.942]Entry deleted from font path.
[ 2.946] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 2.946] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 2.946] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 2.946] (II) Loader magic: 0x5642f9cdbe00
[ 2.946] (II) Module ABI versions:
[ 2.946]X.Org ANSI C Emulation: 0.4
[ 2.946]X.Org Video Driver: 23.0
[ 2.946]X.Org XInput driver : 24.1
[ 2.946]X.Org Server Extension : 10.0
[ 2.946]

Bug#917034: xterm crashes on certain Unicode characters when font was selected with -fa

2018-12-31 Thread Thomas Dickey 
On Mon, Dec 31, 2018 at 06:11:23PM +0100, Alexander Meyer wrote:
> * Thomas Dickey  [2018-12-31 00:51]:
> 
> > On Sun, Dec 30, 2018 at 06:26:44PM +0100, Alexander Meyer wrote:
> > ...
> >> This is the behaviour I get across xterm versions:
> >> (everything with libfontconfig1 2.13.1-2)
> >> 
> >> fonts.conf enabled:
> >> 337: works
> >> 338: segfault
> >> 340: segfault
> >> 341: segfault
> > 
> > Can you make a backtrace for #341, please?
> 
> Here it is:

thanks.  I added some notes, but have not been able to reproduce the problem.
 
> Reading symbols from /usr/bin/xterm...Reading symbols from 
> /usr/lib/debug/.build-id/b8/d462fb6f4969a6a228262ceff981af02a1a4d5.debug...done.
> done.
> (gdb) run -fa 'Noto Mono'

fwiw, my Debian/testing machine has these fonts (with "noto" in their names):

ii  fonts-noto20181130-1
all  metapackage to pull in all Noto fonts
ii  fonts-noto-cjk1:20170601+repack1-3  
all  "No Tofu" font families with large Unicode coverage (CJK 
regular and bold)
ii  fonts-noto-color-emoji0~20180810-1  
all  color emoji font from Google
ii  fonts-noto-hinted 20181130-1
all  "No Tofu" font families with large Unicode coverage 
(hinted)
ii  fonts-noto-mono   20181130-1
all  "No Tofu" monospaced font family with large Unicode 
coverage
ii  fonts-noto-unhinted   20181130-1
all  "No Tofu" font families with large Unicode coverage 
(unhinted)

> Starting program: /usr/bin/xterm -fa 'Noto Mono'
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x77d662d1 in FcConfigEvaluate (p=0x556f2430, 
> p_pat=0x559dea90, kind=kind@entry=FcMatchFont, e=0x0) at fccfg.c:977
> (gdb) bt full
> #0  0x77d662d1 in FcConfigEvaluate (p=0x556f2430, 
> p_pat=0x559dea90, kind=kind@entry=FcMatchFont, e=0x0) at fccfg.c:977
> v = {type = FcTypeVoid, u = {s = 0x556f1ad0 " \033oUUU", i = 
> 1433344720, b = 1433344720, d = 4.6355706220021174e-310, m = 0x556f1ad0, 
> c = 0x556f1ad0, f = 0x556f1ad0, 
> l = 0x556f1ad0, r = 0x556f1ad0}}
> vl = {type = 1433014944, u = {s = 0x0, i = 0, b = 0, d = 0, m = 0x0, 
> c = 0x0, f = 0x0, l = 0x0, r = 0x0}}
> vr = {type = 1436412560, u = {s = 0x0, i = 0, b = 0, d = 0, m = 0x0, 
> c = 0x0, f = 0x0, l = 0x0, r = 0x0}}
> vle = 
> vre = 
> m = 
> str = 
> op = 

If "op" weren't optimized, we could see which case is breaking :-)
But since "e" is null, that says op is garbage anyway.

> buf1 = {u = {d = 0, i = 0, l = 0, 
> c = 
> "\000\000\000\000\000\000\000\000\200\032oUUU\000\000\270\022jUUU\000\000\000\000\000\000\000\000\000\000\220\352\235UUU",
>  '\000' , 
> "\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000\060\032oUUU\000\000\320\022jUUU\000\000\000\000\000\000\000\000\000\000\220\352\235UUU",
>  '\000' , 
> "\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000\340\031oUUU\000\000\350\022jUUU\000\000\000\000\000\000\000\000\000\000\220\352\235UUU",
>  '\000' , 
> "\256m\326\367\377\177\000\000\000\000\000\000\000\000\000\000"...}}
> buf2 = {u = {d = 0, i = 0, l = 0, 
> c = 
> "\000\000\000\000\000\000\000\000@\031oUUU\000\000\030\023jUUU\000\000\000\000\000\000\000\000\000\000\025",
>  '\000' , "\a\000\000\000\000\000\000\000 
> \000\000\000\000\000\000\000\002\000\000\000\000\000\000\000\020\300aUUU\000\000\017\000\000\000\000\000\000\000@\000\000\000\000\000\000\000\260\377\377\377\377\377\377\377\000\000\000\000\000\000\000\000\002\000\000\000\060",
>  '\000' , "[\000\000\000w", '\000' , 
> "n\000\000\000|\000\000\000\t\000\000\000\000\000\000\000\017\000\000\000\000\000\000\000\025",
>  '\000' , "\260\377\377\377\377\377\377\377"...}}
> #1  0x77d66418 in FcConfigEvaluate (p=p@entry=0x556f2430, 
> p_pat=p_pat@entry=0x559dea90, kind=kind@entry=FcMatchFont, 
> e=e@entry=0x55681218) at fccfg.c:1003
> m = {xx = 1.4821969375237396e-323, xy = 6.9533490418283141e-310, yx = 
> 1.4821969375237396e-323, yy = 1}
> xx = 
> yy = 
> xy = 
> yx = 
> v = {type = FcTypeMatrix, u = {s = 0x3  at address 0x3>, i = 3, b = 3, d = 1.4821969375237396e-323, m = 0x3, c = 0x3, 
> f = 0x3, l = 0x3, r = 0x3}}
> vl = {type = FcTypeVoid, u = {s = 0x556f24b0 "Noto Color Emoji", 
> i = 1433347248, b = 1433347248, d = 4.6355706221270172e-310, m = 
> 0x556f24b0, c = 0x556f24b0, f = 0x556f24b0,