Re: error ent = 1073741820, Fatal server error: failed to create root window

2013-04-01 Thread Richard PALO

Le 28/03/13 08:19, Alan Coopersmith a écrit :

You may or may not have better luck with a X server from this decade instead
of trying to run one from 4 years ago - you'd certainly find more people willing
to investigate and help on a current server such as 1.14 than on 1.6.

Well, after spending the weekend upgrading xorg-server to 1.13.3 and as 
well as a couple of components that were not latest and greatest, I am 
able to run with dri disabled (not really up to a Mesa upgrade just 
yet.. seems to be a nightmare in pkgsrc for the moment).


I am tempted to believe that it was a fouled patch for _X_EXPORT in 
xproto that, perhaps together with mesa, caused my problems due to lack 
of globals using gcc4.7.2 on solaris...


I'll test again on the old stuff with this _now known_ fix.

Thanks anyway for your patience and push to upgrade.

It was quite an experience.

___
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


Re: Setting keyboard autorepeat rate with xkb?

2013-04-01 Thread Tony Bones
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

Re: Setting keyboard autorepeat rate with xkb?

2013-04-01 Thread Alan Coopersmith
On 04/ 1/13 01:05 PM, Tony Bones wrote:
> 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.

The xinput command provides per-device settings, but I don't see auto
repeat rates in the properties the kbd driver exposes.   I don't have
an evdev machine booted at the moment to check if it has an auto-repeat
rate property.

-- 
-Alan Coopersmith-  alan.coopersm...@oracle.com
 Oracle Solaris Engineering - http://blogs.oracle.com/alanc
___
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


Re: Setting keyboard autorepeat rate with xkb?

2013-04-01 Thread Peter Hutterer
On Mon, Apr 01, 2013 at 01:27:49PM -0700, Alan Coopersmith wrote:
> On 04/ 1/13 01:05 PM, Tony Bones wrote:
> > 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.
> 
> The xinput command provides per-device settings, but I don't see auto
> repeat rates in the properties the kbd driver exposes.   I don't have
> an evdev machine booted at the moment to check if it has an auto-repeat
> rate property.

it doesn't. autorepeat is handled by XKB and xinput doesn't expose xkb
settings. You really need something like xkbctrl which, on a quick glance,
supports a device ID:

ftp://ftp.freebsd.org/pub/FreeBSD/ports/distfiles/xkbctrl/xkbctrl.c

Cheers,
   Peter
___
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


[ANNOUNCE] xf86-input-synaptics 1.7.0

2013-04-01 Thread Peter Hutterer
synaptics 1.7.0, the generic driver for touchpads is now available.
This release has seen a bunch of purges in the hope that it will make the
code more maintainable. Most of the features dropped are expected to have
few or no users, or hardware that hasn't been around for ages.

Most other fixes have found their way into the 1.6 branch already.

Chase Douglas (4):
  Ignore pre-existing touches
  Reset open slots array on device disable
  Add MODEL_UNIBODY_MACBOOK touchpad model for bcm5974 devices
  Turn down the default sensitivity for unibody MacBook touchpads

Chun Yang (1):
  Fix coasting for negative ScrollDelta

Daniel Stone (1):
  Free mtdev device as well as closing it

Peter Hutterer (53):
  Indent consistently
  tools: undo indentation in synclient's parameter list
  whitespace fix
  Bump to 1.6.99
  Bury shm - or what was left of it
  Drop trackstick emulation mode
  Purge fast-taps option
  Purge edge motion
  Purge scrollbuttons (repeat)
  Drop circular pad support
  Update various Red Hat copyrights
  Require xserver 1.12 and inputproto 2.2
  Move synaptics.h leftovers to synapticsstr.h, drop synaptics.h
  Format Makefile.am, drop @DRIVER_NAME@.c usage
  Rename force_empty parameter to set_slot_empty
  Don't check for soft buttons if a button is already down
  Fix coasting speed trigger
  tools: coasting speed is not capped at 20, cap it at 255
  Avoid out-of-bounds access by running num_active_touches < 0 (#49439)
  Remove defunct HAVE_MULTITOUCH compiler warning
  Reset hw->x/y to INT_MIN and skip HandleState until we have x/y events
  Don't allow for scroll distances of 0 (#49965)
  Remove absolute mode
  Fix indentation mishap
  Remove @DRIVER_NAME@ from Makefile.am
  DeviceOn and friends return a status code, not a bool
  Remove an unused define for 1/sqrt(2)
  Remove typedefs from all enums
  tools: un-typedef TouchpadState
  Un-typedef model_lookup_t
  check for HAVE_CONFIG_H before including config.h
  Fix indentation for the synaptics protocol ops
  ps2comm: use ErrorF from PS2DBG directly
  Move properties header to where it's needed
  Remove leftover HAVE_SMOOTH_SCROLL typedef
  eventcomm: simplify conditions
  eventcomm: proto_data is not null, don't check
  Decorate the accel log messages with (accel)
  Use LogMessageVerbSigSafe on ABI 18
  Reset num_active_touches on DeviceOff (#52496)
  test: drop xf86CheckStrOption from fake symbols
  Recognise the soft button area property before clickpad is enabled
  Allow dead areas to update the button state
  conf: add example for AreaBottomEdge on clickpad buttons
  Replace numerical values with an enum for the TouchpadOff prop
  eventcomm: print axis resolution to the log
  tools: drop -s listing in synclient's help output. SHM is gone.
  synclient: remove 'm' and 'h' from getopt and man page
  synclient: support -? for usage
  syndaemon: list -? in help/man page
  synclient: drop XF86Config-4 from man page
  synclient: use a parameter that actually exists in the man page example
  synaptics 1.7.0

Samuel Thibault (1):
  Enable ps2comm and alpscomm build on GNU/Hurd

git tag: xf86-input-synaptics-1.7.0

http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.7.0.tar.bz2
MD5:  5e4f232a18a1741e4c34895d28238f8d  xf86-input-synaptics-1.7.0.tar.bz2
SHA1: 404b649f76b97787d0409299215afef1de8d23d7  
xf86-input-synaptics-1.7.0.tar.bz2
SHA256: d6f1ad0b0653dddbe2e2db7e2f06c1860e491045e87a6577b63568d65e5d0f0e  
xf86-input-synaptics-1.7.0.tar.bz2

http://xorg.freedesktop.org/archive/individual/driver/xf86-input-synaptics-1.7.0.tar.gz
MD5:  641f2aac0cb2588875cc2ec16caeebfc  xf86-input-synaptics-1.7.0.tar.gz
SHA1: 4db04614117119cc584faa756f7d2e0a45f3a96b  
xf86-input-synaptics-1.7.0.tar.gz
SHA256: 7031939a8e60b9a93fe1c205a20673e10d9dc089028b730d6bb5ffbbac36884c  
xf86-input-synaptics-1.7.0.tar.gz



pgpIwAoz2IAFd.pgp
Description: PGP signature
___
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

Subject=Re: Multiple Headless X Servers Attached to Graphics Cards

2013-04-01 Thread Jonathan Herriott
I specifically forgot to mention that when running multiple processes
against the same Display, for example, Display=:0 there are no issues.  It
is specifically when running two, supposedly, independent X Servers.
___
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