Re: xrandr: cannot find output 0x95

2016-09-30 Thread Thomas Lübking
On Thu, Sep 29, 2016 at 10:48:03PM -0400, John Lewis wrote: When I run xrandr --output 0x95 --off DVI-0 turns off. What happens if you twist DVI and HDMI in the combined call? Cheers, Thomas ___ xorg@lists.x.org: X.Org support Archives: http://lists.

[ANNOUNCE] xf86-input-libinput 0.20.0

2016-09-30 Thread Peter Hutterer
Most important fix is the use of input_lock() instead of the old SIGIO stuff to handle the input thread in server 1.19. This version now supports tablet pads and exposes properties for changing the tap button mapping and the rotation. Eric Engestrom (1): man: fix a couple typos Keith Packa

[ANNOUNCE] xf86-input-libinput 0.20.0

2016-09-30 Thread Peter Hutterer
[This time with signature] Most important fix is the use of input_lock() instead of the old SIGIO stuff to handle the input thread in server 1.19. This version now supports tablet pads and exposes properties for changing the tap button mapping and the rotation. Eric Engestrom (1): man: fix

help

2016-09-30 Thread David Aldrich
Best regards David ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s

Re: help

2016-09-30 Thread Floris
Op Fri, 30 Sep 2016 09:16:53 +0200 schreef David Aldrich : Best regards David I love to help, but what is your problem? ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: https://lists.x.org/mailman

proper release of edid-decode with versioning, proper changelog etc.

2016-09-30 Thread shirish शिरीष
Hi all, Please CC me if somebody answers, thank you. I filed a bug to update edid-decode in debian. See https://bugs.debian.org/839152 The answer I was given by the maintainer is as follows - I'm not sure putting git-generated ChangeLog is in any way beneficial to the users. I think it's better

Bug (?) in compose

2016-09-30 Thread Clock Source
Good day! Please get me a tips, where I must catch bug. Not all compose combinations work. For example: : "ß" ssharp # LATIN SMALL LETTER SHARP S - work, xev output: KeyPress event, serial 39, synthetic NO, window 0x501, root 0x262, subw 0x0, time 2509703, (375,

Re: Bug (?) in compose

2016-09-30 Thread Ilya Anfimov
On Fri, Sep 30, 2016 at 04:25:20PM +0300, Clock Source wrote: > Good day! > > Please get me a tips, where I must catch bug. Not all compose > combinations work. For example: Why do you think that something does not work? > >: "??" ssharp # LATIN SMALL LETTER > SHARP

Re: Bug (?) in compose

2016-09-30 Thread Clock Source
On Fri, 30 Sep 2016 17:18:31 +0300 Ilya Anfimov wrote: > On Fri, Sep 30, 2016 at 04:25:20PM +0300, Clock Source wrote: > > Good day! > > > > Please get me a tips, where I must catch bug. Not all compose > > combinations work. For example: > > Why do you think that something does not work?

Re: Bug (?) in compose

2016-09-30 Thread Ilya Anfimov
On Fri, Sep 30, 2016 at 05:58:56PM +0300, Clock Source wrote: > > > On Fri, 30 Sep 2016 17:18:31 +0300 > Ilya Anfimov wrote: > > > On Fri, Sep 30, 2016 at 04:25:20PM +0300, Clock Source wrote: > > > Good day! > > > > > > Please get me a tips, where I must catch bug. Not all compose > > > combi

Re: Bug (?) in compose

2016-09-30 Thread Clock Source
On Fri, 30 Sep 2016 18:24:15 +0300 Ilya Anfimov wrote: > And how do you try to print that characters? > > (I could also note, that xev output is exactly that > is expected when typing that composed sequences) I print Compose + symbols in X-applications, such as leafpad/browser/mail client/l

Re: Bug (?) in compose

2016-09-30 Thread Clock Source
On Fri, 30 Sep 2016 18:24:15 +0300 Ilya Anfimov wrote: > And how do you try to print that characters? > > (I could also note, that xev output is exactly that > is expected when typing that composed sequences) I print Compose + symbols in X-applications, such as leafpad/browser/mail client/l

Re: Bug (?) in compose

2016-09-30 Thread Alan Coopersmith
On 09/30/16 08:32 AM, Clock Source wrote: On Fri, 30 Sep 2016 18:24:15 +0300 Ilya Anfimov wrote: And how do you try to print that characters? (I could also note, that xev output is exactly that is expected when typing that composed sequences) I print Compose + symbols in X-applications,

Re: Bug (?) in compose

2016-09-30 Thread Clock Source
On Fri, 30 Sep 2016 08:33:53 -0700 Alan Coopersmith wrote: > Note that some toolkits such as GTK use their own input handling and > their own Compose key tables, not the Xlib ones. In that case compose key, specified in XkbOptions will work, but got other tables, right? Hmm... looks like my ca

Re: XLookupString return inconsistent

2016-09-30 Thread wettstae
> So there's no way to work around this? I can think of three: - You have two Shift keys and most likely two Mod4 keys. This gives you three more possibilities to enter the same combination. If any of this combinations works and is sufficiently convenient to type, that would be the easies

Re: proper release of edid-decode with versioning, proper changelog etc.

2016-09-30 Thread Tormod Volden
On Fri, Sep 30, 2016 at 3:37 PM, shirish शिरीष wrote: > Hi all, > > Please CC me if somebody answers, thank you. > > I filed a bug to update edid-decode in debian. See > https://bugs.debian.org/839152 > > The answer I was given by the maintainer is as follows - > > I'm not sure putting git-generate

Re: xrandr: cannot find output 0x95

2016-09-30 Thread John Lewis
On 09/30/2016 02:53 PM, Thomas Lübking wrote: > On Fri, Sep 30, 2016 at 07:29:47AM -0400, John Lewis wrote: >> I don't understand what you mean, I will try this. >> >> john@thunderguard:~/.screenlayout$ cat twoscreens1.sh >> #!/bin/sh >> xrandr --output DVI-0 --mode 1920x1080 --pos 1936x0 --rotate

Re: xrandr: cannot find output 0x95

2016-09-30 Thread John Lewis
On 09/30/2016 07:20 PM, John Lewis wrote: > On 09/30/2016 02:53 PM, Thomas Lübking wrote: >> On Fri, Sep 30, 2016 at 07:29:47AM -0400, John Lewis wrote: >>> I don't understand what you mean, I will try this. >>> >>> john@thunderguard:~/.screenlayout$ cat twoscreens1.sh >>> #!/bin/sh >>> xrandr --ou

Re: proper release of edid-decode with versioning, proper changelog etc.

2016-09-30 Thread Christopher Barry
On Fri, 30 Sep 2016 23:14:03 +0200 Tormod Volden wrote: >On Fri, Sep 30, 2016 at 3:37 PM, shirish शिरीष wrote: >> Hi all, >> >> Please CC me if somebody answers, thank you. >> >> I filed a bug to update edid-decode in debian. See >> https://bugs.debian.org/839152 >> >> The answer I was given by t

Re: xrandr: cannot find output 0x95

2016-09-30 Thread John Lewis
On 10/01/2016 02:14 AM, Thomas Lübking wrote: > On Fri, Sep 30, 2016 at 07:20:37PM -0400, John Lewis wrote: > >> john@thunderguard:~$ xrandr --output DVI-0 --mode 1920x1080 --pos 1936x0 >> --rotate normal >> xrandr: cannot find mode 1920x1080 > > Ok, like before. > >> john@thunderguard:~$ xrandr --

Re: xrandr: cannot find output 0x95

2016-09-30 Thread John Lewis
On 10/01/2016 02:45 AM, Thomas Lübking wrote: > On Sat, Oct 01, 2016 at 02:21:29AM -0400, John Lewis wrote: > >>> And does this provide it or do you get (other?) errors? >>> xrandr --output HDMI-3 --auto --rotate normal --output DVI-0 --auto >>> --rotate normal --right-of HDMI-3 >>> >>> Cheers, >>>