Re: XLookupString return inconsistent

2016-09-29 Thread martin f krafft
also sprach wetts...@gmail.com [2016-09-12 18:01 +0200]: > > And moments after clicking send, I realized this is really just hardcoding > > US keyboard layout & ASCII encoding - Shift-2 is '@' and Ctrl-@ is '\0'. > > Oh, yes. And Ctrl+3-7 get mapped to 0x1b-0x1f, the control codes beyond > Ctrl-

some potential security issue for edid-decode

2016-09-29 Thread shirish शिरीष
Hi all, First of all thank you all for the wonderful work you are during in X.org and its components. I have been using x.org and it components forever. Please make sure to CC me in case anybody replies as I have turned off general replies from the list as I'm already info. overloaded. I have be

Re: some potential security issue for edid-decode

2016-09-29 Thread Alan Coopersmith
In general, we'd prefer reports of security issues go to our security list (which I've cc'ed) instead of our general discussion list, but in this case, unless I'm missing something, in our code, these are just plain bugs, as there's no trust or privilege boundary someone can exploit here. If some

Re: XLookupString return inconsistent

2016-09-29 Thread wettstae
> Long story short: do you see any chance in making this bit of > legacy (nostalgia?) code configurable, or remove it altogether? I do not know, but I do not see the benefit of doing that. It certainly would not fix your problem, which I still think is hardware. Andreas __

Re: XLookupString return inconsistent

2016-09-29 Thread martin f krafft
also sprach wetts...@gmail.com [2016-09-29 21:00 +0200]: > I do not know, but I do not see the benefit of doing that. It > certainly would not fix your problem, which I still think is > hardware. I think you are right. I just noticed that this only happens with my USB keyboards, not with the Thi

Re: some potential security issue for edid-decode

2016-09-29 Thread Seth Arnold
On Thu, Sep 29, 2016 at 09:14:52AM -0700, Alan Coopersmith wrote: > On 09/29/16 07:48 AM, shirish शिरीष wrote: > >Flawfinder version 1.31, (C) 2001-2014 David A. Wheeler. > >Number of rules (primarily dangerous function names) in C/C++ ruleset: 169 > >./JSON/i-nex-edid.c:137: [2] (buffer) char: >

Re: xrandr: cannot find output 0x95

2016-09-29 Thread Thomas Lübking
On Tue, Sep 27, 2016 at 11:00:13PM -0400, John Lewis wrote: xrandr --output DisplayPort-3 --off ... DisplayPort-3 disconnected No idea why arandr wants to configure a disconnected output, but this is most likely the cause. Seems an arandr bug. Cheers, Thomas __

Re: xrandr: cannot find output 0x95

2016-09-29 Thread John Lewis
When I run xrandr --output 0x95 --off DVI-0 turns off. john@thunderguard:~/.screenlayout$ xrandr --output 0x95 --off john@thunderguard:~/.screenlayout$ xrandr --current Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DisplayPort-3 disconnected HDMI-3 connected 1920x1080+0+