Re: xorg Digest, Vol 99, Issue 29
在我的摩托罗拉手机发送
xorg-requ...@lists.x.org编写：
>Send xorg mailing list submissions to
> xorg@lists.x.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.x.org/mailman/listinfo/xorg
>or, via email, send a message with subject or body 'help' to
> xorg-requ...@lists.x.org
>
>You can reach the person managing the list at
> xorg-ow...@lists.x.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of xorg digest..."
>
>
>Today's Topics:
>
> 1. [ANNOUNCE] xorg-server 1.14.3.901 (Matt Dew)
> 2. SIGUSR1 to xinit (k...@hot.ee)
> 3. bug report (Jean-Gael Renard)
> 4. add (Jean-Gael Renard)
> 5. Re: SIGUSR1 to xinit (Alan Coopersmith)
>
>
>--
>
>Message: 1
>Date: Sat, 26 Oct 2013 14:17:50 -0600
>From: Matt Dew
>To: xorg-annou...@lists.freedesktop.org
>Cc: x...@lists.freedesktop.org
>Subject: [ANNOUNCE] xorg-server 1.14.3.901
>Message-ID: <526c236e.8050...@osource.org>
>Content-Type: text/plain; charset=ISO-8859-1
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>All,
> Here's 1.14.4-rc1. Please beat on it.
>
>Major highlight:
> CVE-2013-4396 -
>https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-4396
>
>
>I pulled and cherry-picked these late in the 6-week cycle.
>
>Considering that the CVE-2013-4396 is in here, I'm extending this
>another week. I want to get this out for the security patch, but I
>want a little testing on it. So, if there are no issues between now
>and next Thursday, I will release it then.
>
>
>Alan Coopersmith (2):
> Avoid use-after-free in dix/dixfonts.c: doImageText()
>[CVE-2013-4396]
> Allow disabling XFree86-DGA, DRI, VidModeExtension extensions
>
>Egbert Eich (1):
> DIX/Xi: Pass correct client to CheckDeviceGrabAndHintWindow()
>
>Julien Cristau (3):
> test: include dix-config.h in hashtabletest.c
> xfree86: improve check for posix saved ids
> dix: add missing include for DeleteWindowFromAnySelections
>
>Matt Dew (1):
> Bump version from 1.14.3 to 1.14.3.901.
>
>Peter Hutterer (14):
> test: fix the gcc diagnostics pragma
> dix: check for grab type before checking XI2 mask
> Xi: allow for XIAllowEvent requests larger than XI < 2.2 size
>(#68554)
> dix: only allow button and key events to freeze a sync'd pointer
> include: change grabtypes to start at 1
> dix: don't attempt to deliver an event for a different grabtype
> dix: only deliver for the current grab type
> sync: compress two if statements
> sync: always call BracketValues when recalculating upper/lower
>brackets
> sync: supply the counter from IdleTimeBlockHandler
> dix: provide accessor methods for the last device event time
> sync: if the idle time was reset, force alarms to trigger (#70476)
> sync: always set the brackets (#59644)
> sync: split updating and triggering a counter up
>
>git tag: xorg-server-1.14.3.901
>
>http://xorg.freedesktop.org/archive/individual/xserver/xorg-server-1.14.3.901.tar.bz2
>MD5: 8b59f9964103706f7b1bf4ba8395f91b xorg-server-1.14.3.901.tar.bz2
>SHA1: b253807d4f3110e8297859d7a94a2820e277ef9d
>xorg-server-1.14.3.901.tar.bz2
>SHA256:
>3d8481f60d6ef67bb9b72c1ee375f5a64e69ba32c613c01367b3c2b5c154ab0a
>xorg-server-1.14.3.901.tar.bz2
>
>http://xorg.freedesktop.org/archive/individual/xserver/xorg-server-1.14.3.901.tar.gz
>MD5: af10685c61957b3fd10fd32a7eed0af3 xorg-server-1.14.3.901.tar.gz
>SHA1: a0a9f60f465fdb536e885b293e3cb4f6f93533fe
>xorg-server-1.14.3.901.tar.gz
>SHA256:
>6339d38d314435a8d6d0926aeef939b8e74c8f167890870d7bb585f37bd90cd4
>xorg-server-1.14.3.901.tar.gz
>
>
>
>- --
>Matt DewKey signature: 0xF7C3 BEC3
>Fingerprint: FDB1 9D94 C573 DC29 BCCB 2F9F A6BF 3771 F7C3 BEC3
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v1.4.13 (GNU/Linux)
>Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
>iQEcBAEBAgAGBQJSbCNrAAoJEKa/N3H3w77DnM4H/0ALx+Qft5Nf+H7/c96DONn/
>Fqjf9HUy1TAqsQr1u5deLxDYgl60RBUB0Yq6UA+u1v/XhavRLJBM6Zvvyd+2Dc8n
>rqwNuNfIztPsh+j4L/G+zbsP7odoH875Wj0du/+5OvcwL4G7ImwChPqZo0MG0L0K
>YF4/uhqrkksFjFwQhZhayf7R5mJpP8gillbtDMj3vrvDHHx33yeymW8Ysfu0TYlt
>KxQmoRVrnIYFxHTn1HZQ5i90TpZHVX6Hgar+ra4lSNMp90HTBOpRabTVGO7gbJ4B
>uLgt5FrinDpkgHoY7c75JxDOGNJpobBwczNaCGaXemCkZaZiWUBGQjaUFuEoDto=
>=Y2pb
>-END PGP SIGNATURE-
>
>
>--
>
>Message: 2
>Date: Fri, 25 Oct 2013 18:05:53 +0300
>From: k...@hot.ee
>To: xorg@lists.x.org
>Subject: SIGUSR1 to xinit
>Message-ID: <20131025150553.GA4483@KLF.private>
>Content-Type: text/plain; charset=us-ascii
>
>Hello,
>
>Apparently xserver does not signal the parent if ppid == 1. (Launch from init
>is assumed?)
>
>Excerpt from NotifyParentProcess() in ./os/connection.c:
>if (RunFromSmartParent) {
>if (ParentProcess > 1) {
>kill(ParentProcess, SIGUSR1);
>}
>}
>
>This means startup is slow (a timeout) if xinit hap
Control monitor to be used
Hello, I am sure there has been lot of forums with similar question. I couldn't find answer for what I am trying to do. I have one external monitor connected to laptop using VGA.The setup works fine as an extended monitor. I want to control the monitor application's graphical interface is started. Both the monitors comes up as Screen0 and $DISPLAY=:0.0. Eg: xclock -display :0.1 Error: Can't open display: :0.1 Does anybody know how can I do it please? I am told "devilspie" can be used for the purpose. Although, I am experimenting with ubuntu laptop, the method is eventually to be used for an embedded devices. So I would prefer to avoid any new application, unless that is the only way. I noticed, in Ubuntu (12.04, gnome-classic) any application with graphical interface once started, is displayed in the monitor where mouse pointer resides. I am after the exact method. But not sure how. Thank you in advance for any suggestions. Following is my xrandr output (My laptop does not have a /etc/X11/xorg.conf ) xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 32767 x 32767 LVDS1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.0*+ 59.9 1680x1050 60.0 59.9 1600x1024 60.2 1400x1050 60.0 1280x1024 60.0 1440x900 59.9 1280x960 60.0 1360x768 59.8 60.0 1152x864 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 75.0 60.0 1440x900 59.9 1280x800 59.8 1152x864 75.0 1280x720 60.0 1024x768 75.1 70.1 60.0 832x62474.6 800x60072.2 75.0 60.3 56.2 640x48072.8 75.0 66.7 60.0 720x400 70.1 Thanks, Tony ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Setting keyboard autorepeat rate with xkb?
That's all great info which will work for almost everyone out there. But I have two keyboards and need to set different auto repeat rates for each independently. Currently I'm still using the kbd driver and can certainly switch over to evdev and InputClass. I didn't see a way xset would target a specific keyboard / input device. So I started looking for an xorg.config way, which led me here. Any ideas? ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
Making xset stick on a secondary X session
Hi, I am running a second X server (:1) and then run the vnc client (tigervnc) over it in -fullscreen. I am having huge problems increasing the keyboard repeat rate and reducing the keyboard delay for that X server. To see what I mean, simply run another X server: sudo X :1 & The blank, empty X server will be there Then go back to the "main" xserver, and run: export DISPLAY=:1 xterm At this point, the repeat is average and the delay is long--ish (the default). Now run within that xterm: xset r rate 150 50 The keyboard repeat rate and delay are adjusted. Great! CTRL-D and exit that term. Go back to the "main" X session, and type again: xterm The new repeat/delay settings are gone (?!?!?!), keyboard is slow/delay is long-ish again! Running xset r rate 150 50 from the "main" X server. even with DISPLAY=:1, still won't change the keyboard rate for the second :1 server. This is a bugger, since I need to decide the repeat rate and the delay for that second X server ':1', since I will run the xvnc client in -fullscreen mode -- and I can't find a way of setting that X server :1 so that the repeat/delay are what I need them to be. Help? Merc. ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Re: Making xset stick on a secondary X session
Hi, I tried again. I am starting to doubt that xset works properly! I did: $ export DISPLAY=:1 $ sudo X :1 -noreset & $ xeyes & $ xterm & I can then confirm that xset has no effect on the running X: $ xset r rate 50 150 No difference in the repeat rate. However, if you run the command on the terminal within :1, it will work (as expected). It really looks like xset will only work if run within the server itself... but why? Should I report this as a bug? (it's really easy to reproduce) Bye, Merc. On 14 October 2015 at 08:00, Tony Mobily wrote: > Hi, > > $ export DISPLAY=:1 >>> $ sudo X :1 & >>> $ xterm & >>> >>> At this point, a new terminal is running and it's all dandy. But repeat >>> is SLOW. >>> >>> Then, from the LAUNCHING terminal: >>> >>> $ xset r rate 50 150 >>> >>> Back in the :1 server, the repeat has NOT changed. Input from xterm is >>> still >>> very slow. >>> >> >> My best guess is either DISPLAY isn't set correctly for the xset process >> or >> that since you don't have -noreset in that X command line you're hitting a >> race condition and the xset exits before the more complicated xterm begins >> and thus the server resets between the two. > > > > I tried again. > > $ export DISPLAY=:1 > $ sudo X :1 -noreset & > $ xeyes & > $ xterm & > > I can then confirm that xset has no effect on the running X: > > $ xset r rate 50 150 > > No difference in the repeat rate. > However, if you run the command on the terminal within :1, it will work > (as expected). > > It really looks like xset will only work if run within the server > itself... but why? Should I report this as a bug? (it's really easy to > reproduce) > > Bye, > > Merc. > > > ___ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: %(user_address)s
Where is the documentation for the clipboards?
Hi All, I am not finding anything about the two clipboards over on https://www.x.org/releases/current/doc/libX11/libX11/libX11.html Is "clipboard" the wrong keyword to search for? Also, are there any examples out there in C land on how to read and write to the two clipboards? Many thanks, -T -- - I Fish. Therefore, I am. - ___ 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
