Hi Valter,
I had this problem long ago with a very similar configuration. It
vanished when Alex Deucher modified some details (like rounding) in the
Radeon mode setting/calculation code.
I don't know about the details, but maybe you can copy the modeline
generated by the proprietary driver and fo
The integration of the code has some deficiencies which try to resolve here
mainly to make reuse of the code easier. Also, the new valuator masks are
now used by acceleartion, making things much more straightforward.
___
xorg@lists.freedesktop.org: X.Or
On 12/09/2010 01:22 AM, Peter Hutterer wrote:
>> What can be done?
>
> commit beea2378f142556471c62290e275935af848e137
> Author: Peter Hutterer
> Date: Mon Dec 6 14:33:43 2010 +1000
>
> xfree86: don't overwrite option list (#32115)
>
> Options set in the configuration file were un
On 11/25/2010 07:42 AM, Joel Feiner wrote:
> On Wed, Nov 24, 2010 at 5:44 PM, Simon Thum wrote:
>
>> On 11/23/2010 06:33 AM, Joel Feiner wrote:
>>> Mouse acceleration seems to have gone away as of a week or so ago. I'm
>> not
>>> sure which component d
On 11/23/2010 06:33 AM, Joel Feiner wrote:
> Mouse acceleration seems to have gone away as of a week or so ago. I'm not
> sure which component did it and I don't recall when it actually changed
> since I use Linux now irregularly and only update once in a while.
Yes, It's a known problem originati
at OK?
-
Simon
On 11/15/10 06:34, Dan Nicholson wrote:
> On Sun, Nov 14, 2010 at 8:19 PM, Peter Hutterer
> wrote:
>> On Sun, Nov 14, 2010 at 02:11:25PM -0800, walt wrote:
>>> On 11/14/2010 09:11 AM, Simon Thum wrote:
>>>> Hi all,
>>>>
>>>&g
On 11/05/10 00:21, Peter Hutterer wrote:
> On Thu, Nov 04, 2010 at 10:35:29PM +1100, Russell Shaw wrote:
>> In XInput2, when i get a XI_HierarchyChanged event after plugging in
>> another mouse, is there a way to get a unique identifier for each device
>> such as a brand and model number?
>
> no,
Am 21.06.2010 01:53, schrieb Peter Hutterer:
> On Sat, Jun 19, 2010 at 07:17:52PM +0200, Harald Dunkel wrote:
>> AngleOffset is a mousedrv(4) parameter, evdev doesn't have anything
>> similar and your device is now handled by evdev. Feel free to port this
>> over.
>
>> I've been hoping to somehow
section.
> man: note where the Area options fit in.
> man: don't call it "synaptics" touchpad driver.
> Support percent values for area.
> Move some defines to where they belong.
> Reshuffle default value initialization.
> Re-u
Am 09.06.2010 00:20, schrieb Jacek Wielemborek:
> Hi,
>
> I recently decided to try and build an app allowing me to easily
> convert my netbook into an e-book reader at any time. The problem is,
> when I try to rotate the screen on the right, making the resolution
> 600x1024, the touchpad behaves
Am 14.05.2010 19:37, schrieb Dan Nicholson:
> On Thu, May 13, 2010 at 11:45 PM, Nikos Chantziaras wrote:
>> 5
>> > type="string">2
>> > type="string">0.15
>> 8
>> true
>>
>>
>> With X.Org server 1.8 and HAL disabled, how to I configure the above?
In case you're referring to the ex
Am 28.04.2010 13:20, schrieb Tobias Wolf:
> On Wed, 2010-04-28 at 11:44 +0200, Simon Thum wrote:
>> This intends to preserve precision. I'd bet any speed gains one may have
>> under another OS is driver magic.
>
> I never used this machine under another OS and am not s
Am 28.04.2010 02:01, schrieb Peter Hutterer:
>
> sysfs files are for knobs exposed by the kernel.
>
>> Simple question, asking for the current way to configure:
>>
>> How do I speed up my terribly slow TrackPoint?
>
> Simon, do we have anything to speed up devices? looks like everything we
> ha
Hi Max,
I've had a small look at your work. I've often had requests to do this
by users who assumed this would work the same way as pointer
acceleration, which unfortunately it doesn't. So I have a small comment
and a suggestion.
The comment first; from your rationale: "The new event would specif
Am 16.03.2010 09:42, schrieb Zhang, Xing Z:
> Hi experts:
> From xlib manual, here are sentences for color:
>
> GrayScale is treated the same way as PseudoColor except that the *primary*
> that drives the
> screen is undefined. Thus, the client should always store the same value for
> r
Peter Hutterer wrote:
> On Mon, Mar 01, 2010 at 12:41:02AM -0700, David Mohr wrote:
>> On Sun, Feb 28, 2010 at 11:37 PM, Peter Hutterer
>> wrote:
>>> On Sun, Feb 28, 2010 at 11:29:12PM -0700, David Mohr wrote:
I'm part of the minory who currently uses a Zaphod style dual monitor
setup wi
Julien Cristau wrote:
> This is also expected at the moment. The enumeration of devices gives
> us /dev/input/event* (which evdev can handle), and
> /dev/input/{mouse,kbd}* (which it doesn't). This results in a couple
> error messages for the latter. It should be possible to tone those down
> so
Hi all,
I just upgraded my X to use udev. It generally went fine, but I noticed
two minor issues:
At first, the device names have quotation marks. As in
xinput list
...
⎜ "ImExPS/2 Logitech Wheel Mouse" id=7[slave pointer
(2)]
I looked up the source, but found nothing obvio
Zhi Li wrote:
> All,
>
> I'm working in a project which study energy saving on PCs. I saw a
> strange thing which was opposite to my intuition: when PC working on
> graphic mode, it would be more energy saving.
>
> When in graphic mode, on my PC, it is 52w; when I switched to terminal
> mode(on l
to hear - that's exactly what it should achieve.
>
> aside from that, looks good to me and I'd be happy to put that one in. We'll
> see if we get positive feedback.
>
Yay! Attached.
Cheers,
Simon
>From 76ea8499aa308ad535f499cc1e6712dd1ea82373 Mon Sep 17 00:00:00
Marco Cavallini wrote:
> Simon Thum ha scritto, Il 27/01/2010 11:47:
>> Marco Cavallini wrote:
>>> Hi,
>>> I'm testing and debugging xinput-calibrator and looks like
>>> CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored
>>> by
Marco Cavallini wrote:
> Hi,
> I'm testing and debugging xinput-calibrator and looks like
> CalibratorEvdev::do_set_prop - XChangeDeviceProperty calls are ignored
> by Xorg.
Properties may reject attempts to change their value (to specific
values). Also, if the properties don't exist before, you ma
ck!
>From 0c30a80cb0e32b89a93c2497ebd7ef97652cf211 Mon Sep 17 00:00:00 2001
From: Simon Thum
Date: Wed, 9 Sep 2009 14:41:08 +0200
Subject: [PATCH] Setup pointer acceleration for synaptics
Setup dix pointer accel from the synaptics driver so synaptics devices
behave like before while benefiting from
Peter Hutterer wrote:
> The ususal 5 week schedule will be maintained for 1.7.5
Hi Peter,
since you intend to push 1.7.5, maybe you can include my first ptr accel
xorg.conf.man changes along with fenando's corrections? I hope this
lessens the chance of ppl wasting time with evdev scaling patches o
Those patches should address the issues. The rename is skipped for now.
Peter Hutterer wrote:
> thanks, that woke me up. I was struggling this morning :)
>
> On Tue, Jan 05, 2010 at 09:13:47PM +0100, Simon Thum wrote:
>> another round of ptr accel patches. I didn't sen
Peter Hutterer wrote:
> thanks, that woke me up. I was struggling this morning :)
always a pleasure.
> I don't think this is necessary. We're nitpicking on the wording here and
> given the number of languages out there there's always going to be some
> ambiguity. with this patch you're breaking us
help output.
It's perfectly possible the man changes are bogus, I just copied around
and I seem not to have broken things.
Cheers,
Simon
>From 6bdb4ab5abef8a2155df23281c4ca1268dc999ae Mon Sep 17 00:00:00 2001
From: Simon Thum
Date: Tue, 5 Jan 2010 11:50:05 +0100
Subject: [PATCH 1/4] dix:
Keith Packard wrote:
> Do we have enough info to start assigning default profiles to different
> kinds of devices yet? Should we stick this in some default xorg.conf.d
> fragments? Or should we stick it in the code instead?
Essentially, there is no fixed relation. I tested the 'wacom' profile
w/my
>From fcc93189b031ee78c6292d18c57e71a5c7e423f4 Mon Sep 17 00:00:00 2001
From: Simon Thum
Date: Fri, 11 Dec 2009 20:55:56 +0100
Subject: [PATCH] dix: add smooth limited pointer acceleration profile
This profile is inspired by the accel code removed from the wacom driver.
It ascends from zero to acce
Gene Heskett wrote:
> On Saturday 19 December 2009, Simon Thum wrote:
>> Gene Heskett wrote:
>>> I would tend to agree. With modern high resolution mice, I have often
>>> wished I could set the gain to a below 1 condition. My mouse now uses
>>> about a 1
Lorenz Ruhmann wrote:
> After alternating between the two schemes several times and repeating
> specific mouse strokes a few dozen times, I'm getting less and less
> convinced that there actually is a difference. Also, considering you say
> my settings are correct (I'm not using adaptive decelerati
Peter Hutterer wrote:
> On Sat, Dec 19, 2009 at 02:25:16PM +0100, Simon Thum wrote:
>> Peter Hutterer wrote:
>>> given the two changes alan already suggested,
>>> Reviewed-by: Peter Hutterer
>>>
>>> please send out the last version of these patches an
Gene Heskett wrote:
> I would tend to agree. With modern high resolution mice, I have often wished
> I could set the gain to a below 1 condition. My mouse now uses about a 1"
> x1.35" area of the pad, to cover a 1680x1250 screen, so its way too fast for
> this user.
I'm not sure I got it. What
Justin Piszcz wrote:
> On Fri, 18 Dec 2009, Lorenz Ruhmann wrote:
>> Is there a way to exactly reproduce this old behavior with the new code?
>> I don't like to rely on a scheme that is kinda considered obsolete.
[..]
> Yes, this is VERY annoying to me as well (all of the new acceleration
> method
Lorenz Ruhmann wrote:
> With the old pointer acceleration code (now lightweight scheme) my mouse
> cursor behaves perfectly with the following command:
>
> xset m 16/100 1
>
> Even for far and fast mouse movement I can accurately hit small objects.
>
> However, I'm not able to reproduce that acc
Hi,
I created another acceleration profile, inspired by the bits removed
from the wacom driver.
I think it's worth adding to the server because it has some qualities no
other profile has.
Cheers,
Simon
>From fcc93189b031ee78c6292d18c57e71a5c7e423f4 Mon Sep 17 00:00:00 2001
From: Si
however, so I left it out.
Cheers,
Simon
>From fd3a7020ac06c4bfcdf1a871f0764a31169bb3c1 Mon Sep 17 00:00:00 2001
From: Simon Thum
Date: Sun, 18 Oct 2009 15:10:56 +0200
Subject: [PATCH] xinput: clarify role of set-ptr-feedback
---
man/xinput.man |9 +++--
1 files changed, 7 insertions(+)
Resending to include philip as xinput maintainer. xset doesn't have a
dedicated maintainer. Alan?
Peter Hutterer wrote:
> On Thu, Dec 10, 2009 at 03:13:30PM -0800, Alan Coopersmith wrote:
>> Peter Hutterer wrote:
>>> On Thu, Dec 10, 2009 at 10:24:20PM +0100, Simon Thu
Ross Vandegrift wrote:
> When I installed xinput, the first thing I did was look at the man
> page. But it's nearly useless - all it really does is list how the
> commands map onto API functions. I don't know the XInput API, so most
> of it doesn't mean anything to me.
I take it the man page is a
Peter Hutterer wrote:
> On Thu, Dec 10, 2009 at 03:13:30PM -0800, Alan Coopersmith wrote:
>> Peter Hutterer wrote:
>>> On Thu, Dec 10, 2009 at 10:24:20PM +0100, Simon Thum wrote:
>>>> +has more detials. For X.org 1.7
>>> ^^^ typo ^^ X.Org X
ey seek this kind of information.
In general, is it reasonable to point to the wiki from a man page? That
one's separate if the answer is no.
Cheers,
Simon
>From 84ceba932e93c0b2467be696c9878c4d9c59312b Mon Sep 17 00:00:00 2001
From: Simon Thum
Date: Sun, 18 Oct 2009 15:10:56 +0200
Subject:
ZelluX wrote:
> Considering such a situation, some applications are running on x window
> systems and one of them, for example, a web browser has the focus. If there
> comes an interrupt, such as a keyboard interrupt, and now kernel takes over
> the control. My question is that what's the running u
Alan Coopersmith wrote:
> misunderstanding. (My employer on the other hand, requires us not to
> automatically label everything as confidential, since that just causes people
> to assume nothing really is, and destroys all value of true confidential
> labels.)
I'm amazed by the sheer amount of co
Magnus Kessler wrote:
> On Friday 06 November 2009, Simon Thum wrote:
>> Rémi Cardona wrote:
>>> from git and completely rebuilt. And with a single command, users can
>>> rebuild all "live" packages.
>> Would you be so kind to explain what exactly you&#x
Yotam Medini wrote:
> + On current Ubuntu, it is not easy to configure. The GSynapyics tool
> warns (and requires(?)) settings in /etc/X11/xorg.conf
> while current configuration happens under /usr/share/hal/fdi/...
I can't say that about ubuntu, but I can place stuff in /etc/hal/fdi/...
so onc
Justin Piszcz wrote:
> Solution for now as I need a working desktop:
>
> 1. Recover OS from backup before upgrade:
> 2. Pin kde* and xorg* so they are not upgraded anymore.
>
> In the future/if someone from xorg can respond-- is there a fix/way to
> make the semantics such that 'xset m 20/5 1' i
Flittigs at PICT wrote:
> Hello all, we are undergrad students trying to install and compile the
> latest X release on a virtual box. We did all installation on /opt/MPX
> prefix.
>
> on doing "sudo /opt/MPX/bin/X -config /../xorg.conf" , the X server starts
> running and screen goes blank. We als
Hi,
I just upgraded to the latest-and-greatest X.org + mesa. I've got this
radeon:
01:00.0 VGA compatible controller: ATI Technologies Inc RV280 [Radeon
9200] (rev 01)
01:00.1 Display controller: ATI Technologies Inc RV280 [Radeon 9200]
(Secondary) (rev 01)
No KMS - though it may be compiled in -
> It's never worked ! I'm using Mandriva One 2009 with KDE 4.2.4, Somehow I had
> the
> impression it was something to do with the X-server because the
> Ctrl-Alt-Bkspace
> was also disabled. I have that fixed thanks to the list.
> I'll poke around some with the settings and see if I find anythin
Maybe different ~/.fonts.config?
Comparing outputs of fc-list may also help.
Giacomo wrote:
> Hi to all.
> I am Giacomo S. from Elettra synchrotron radiation facility, Trieste, Italy.
>
> We use to develop Qt GUIs on a kubuntu system.
>
> The development process is as follows:
>
> 1. develop t
Harald Braumann wrote:
> On Wed, 05 Aug 2009 12:08:54 +0200
> Simon Thum wrote:
>> There is a distinct advantage the server has, namely, it knows more
>> detail. So it could do a better job than a client/wm. But still that's
>> far from perfect, which I guess is wh
Harald Braumann wrote:
> If it's not possible yet, are there plans to implement such
> functionality in the X server? Like sending an event whenever the
> pointer stops?
Well, X is in pretty much the same situation here; it just knows when
the mouse moves, or when it did so last time (plus somethin
Simon Thum wrote:
> eventToRawEvent(), again used solely for Xi2 processing. So by inference
> Xi2 is the only option if you want raw coordinates (which are what evdev
> calibration needs). What am I missing?
Just FTR, I figured that Xi1/valuators access is enough if you can
assume no
Peter Hutterer wrote:
> XI 1 gives you access to the valuators as well, so this should work in
> principle if you register for DeviceButtonPress and friends.
Ok, big sorry if I'm wrong, but to clarify: untranslated valuators are
stored in valuators.data_raw, which is picked up solely by
eventToRawE
Florian Echtler wrote:
> Hello everyone,
>
> I've recently written an input event driver for a touchscreen, and it's
> working out-of-the box with the evdev driver. However, the scaling is a
> bit off, so I'd like to do a four-point calibration and set the "Evdev
> Axis Calibration" property accor
Michel Dänzer wrote:
> On Fri, 2009-07-10 at 08:51 -0700, Sebastian Glita wrote:
>> Xorg: pixman-region.c:372: pixman_region_copy: Assertion
>> `pixman_region_selfcheck (src)' failed.
>
> See http://bugs.freedesktop.org/show_bug.cgi?id=22642 .
Thanks for the pointer! I started rebuilding half my
Peter Hutterer wrote:
> On Sat, Jul 04, 2009 at 02:32:09PM +0200, Simon Thum wrote:
>> Asbjørn Sannes wrote:
>>> But for "Evdev Axis Calibration" I have not found anything that works ..
>>>
>>> Any hints and suggestions are welcome :)
>&g
Asbjørn Sannes wrote:
> But for "Evdev Axis Calibration" I have not found anything that works ..
>
> Any hints and suggestions are welcome :)
One could probably do a patch which adds property manipulation to
config/hal, but it didn't surface yet.
I remember to have heard hal can be configured to
jspran...@awlship.com wrote:
> Trying to build Kdrive and I receiving the following errors:
> kinput.c: In function ‘KdEnableInput’:
> kinput.c:340: warning: passing argument 1 of ‘NoticeEventTime’ from
> incompatible pointer type
> kinput.c: In function ‘KdQueueEvent’:
> kinput.c:1675: warning: p
Peter Hutterer wrote:
> this code hasn't been touched for ages (it's even disabled by default).
> hal.c came after this code, so the use of RemoveDevice is more legacy than
> anything else.
>
> Have you tried DIDR? Does it work fine? If so I'll just amend your patch
> before pushing.
Not really tr
ad of RemoveDevice(). Daniel, is there a specific reason to use RD
and not DIDR?
Cheers,
Simon
>From d2c7f41cc2564b155a285d10f404818410b92e3c Mon Sep 17 00:00:00 2001
From: Simon Thum
Date: Fri, 5 Jun 2009 19:14:48 +0200
Subject: [PATCH] config: adapt to Xi2 changes
---
config/dbus.c |2 +-
Peter Hutterer wrote:
> On Fri, May 29, 2009 at 03:42:02PM +0200, Simon Thum wrote:
>> I wonder if one couldn't just do a Xi1 XOpenDevice() to 'convert'
>> Id->Device* ? Any known reasons?
>
> I'm not sure I understand what you mean, but
> - XOpen
Peter Hutterer wrote:
> The protocol only cares about the device id, so to make XTest XI2 aware, all
> that's needed is some libXtst functions that take an id directly instead of
> the XDevice*. So it's a pure client-side change in the library, feel free to
> send me the patch :)
I wonder if one co
Ooops,
forget hat mail; I didn't switch branches.
Simon Thum wrote:
> Christian Beier wrote:
>> Hi there,
>> with the merge of xi2 coming next week, I wonder what the status of
>> XTest with xi2 is. Right now, XTest still pretty much looks like XI
>> 1.x, with
Christian Beier wrote:
> Hi there,
> with the merge of xi2 coming next week, I wonder what the status of
> XTest with xi2 is. Right now, XTest still pretty much looks like XI
> 1.x, with Device*'s instead of devive ids
> (http://cgit.freedesktop.org/xorg/proto/xextproto/tree/XTest.h).
> Looking at
Evgeny M. Zubok wrote:
> I have S3 Trio64V2 with VBE 1.2 and I want to add the possibility of
> display autodetection via DDC to s3 driver. There is two ways to deal
> with DDC: (i) VESA BIOS Extension and (ii) directly from videochip's DDC
> registers. The later method currently is impossible to i
Damien Mir wrote:
> Hello,
>
> I recently installed Opensuse 11.1 on a HP Pavilion dv8000 ( with XPRESS
> 200M graphics ), shipped with Xorg 7.4
> (--) RADEON(0): Chipset: "ATI Radeon XPRESS 200M 5955 (PCIE)" (ChipID =
> 0x5955)
>
> I am experiencing some kind of slow 2D performance, never seen b
Peter Hutterer wrote:
> relative to the window's origin but in the screen coordinate system.
>
> so if the window is on 100/100, a device on root 101/101 has event 1/1,
> even if the valuator state is e.g. 7202/2381 (valuators are in device
> coordinates).
Thanks for the clarification.
Cheers,
Peter Hutterer wrote:
> On Sat, Apr 18, 2009 at 10:54:31AM +0200, Florian Echtler wrote:
However, the second one (controlled by touchpad) reports values in the
range (1472,1408) to (5472,4448). This is also reported in the Xorg.log
by the synaptics driver. How can I map these to scre
Florian Echtler wrote:
> However, the second one (controlled by touchpad) reports values in the
> range (1472,1408) to (5472,4448). This is also reported in the Xorg.log
> by the synaptics driver. How can I map these to screen coordinates? As
> the pointer still moves in screen coordinates, the map
Harald Dunkel wrote:
> Sorry, but I do want to skip pixels (for gaming only, as written
> before). I understand that somebody overloaded (abused?)
> threshold = 0 to provide a completely different acceleration
> characteristic. I would like to have the "classic" profile with
> a "simple" characteri
Hi,
you may want to read this:
http://www.x.org/wiki/Development/Documentation/PointerAcceleration
It is geared towards development, but also contains a lot of end-user
info as well.
> with a constant acceleration (e.g. for gaming)? Something like
I'm not sure what you mean by 'constant accele
Alan Coopersmith wrote:
> Is there any reason we should have two forks of this? Which one
> do most distros ship?
On gentoo:
[I] x11-apps/luit
[...]
Homepage:http://xorg.freedesktop.org/
Not a proof, though.
___
xorg mailing list
xor
This cannot be deduced from that line. You need to review your math.
>>
>> On Wednesday 08 April 2009 22:52:12 Thomas Dickey wrote:
>>
>>> Behdad's comment doesn't make sense in English.
>>>
>>> (Perhaps someone can help Behdad with that - or else explain to him
>>> what "API-stable" might me
Tuomo Valkonen wrote:
> The only problem with core fonts is the blur-fascist elite
> not bothering to fix UTF-8 fontset support, so there you have
> some problems.
If transporting visual information that would otherwise go lost is
blurring, then I'm probably not from this world. The implementation
Bill Crawford wrote:
> On Saturday 28 March 2009 17:42:54 Simon Thum wrote:
>> Rémi Cardona wrote:
> ...
>>> Can't we work something out with Qt folks?
>> Good idea, but I think the above sounds like adopting a
>> what-breaks-gets-fixed policy is the most rea
Rémi Cardona wrote:
> Le 27/03/2009 19:55, Simon Thum a écrit :
>> Hi,
>>
>> I'm bitten by this issue too and I'm somewhat lost with this. The patch
>> has not yet been applied or commented on xorg, so I just want to make
>> sure it's seen.
>
&
Hi,
I'm bitten by this issue too and I'm somewhat lost with this. The patch
has not yet been applied or commented on xorg, so I just want to make
sure it's seen.
8yrgr4dkp...@dyweni.com wrote:
Just noticed that I created the reverse patch. Here to correct one.
Hey Everyone,
I found a bu
> I did a quick sysprof test while switching desktops, and it looks like
> it's all in memcpy:
>
> miClearToBackground 0.00 77.45
> miPaintWindow 0.00 77.45
> ValidateGC
Jeremy C. Reed wrote:
> On Wed, 18 Mar 2009, Peter Hutterer wrote:
>> I think in 1.4, xf86OSMouseInit was still in the server, so maybe
>> there's some conflicts there.
>
> That sounds like that was it. Maybe the xf86-input-mouse configure should
> check for xorg-server >= 1.4.99.something inste
Bill Crawford wrote:
> included on the command line at link time. Libtool sort of abstracts this,
> but
> to do so it needs to keep track of what those dependencies are, and does so
> by
> storing them in this .la file.
Thanks for the explanation. What baffles me is that AFAICT this
introduces
Dan Nicholson wrote:
> Debian (and Ubuntu by proxy) has a patch that makes libtool only add
> needed libraries (i.e., those added on the command line) to the
> dependency_libs setting in .la files. Unfortunately, I think it still
> has a few corner case bugs that make it not upstream acceptable. I
Halim Issa wrote:
> Would I be correct to assume that the best way to work around this is to
> downgrade while waiting for these issues to stabilize upstream in the next
> few months?
Depends on how whacky you want to go. E.g. on LSF/non-production I'd
give remi's script (see bug) a try. Worked
Halim Issa wrote:
> grep: /usr/lib/libxcb-xlib.la: No such file or directory
> /bin/sed: can't read /usr/lib/libxcb-xlib.la: No such file or directory
> libtool: link: `/usr/lib/libxcb-xlib.la' is not a valid libtool archive
Possibly, this is biting you:
http://bugs.gentoo.org/show_bug.cgi?id=15847
James Cloos wrote:
> The Video Bus input device is a keyboard. Mine is:
...
> So, if one wants to handle those keys via X, evdev needs to read that
> input device.
Thanks! I almost had managed to spend a whole day without learning
something new...
Cheers,
Simon
__
Dan Nicholson wrote:
info.callouts.add = {'hal-acl-tool --add-device'} (string list)
>> ...
>> That an awful lot. on my system, only keyboard and pointer are listed.
>> Try booting an older kernel, upgrading HAL, throw out any home-brew HAL
>> fdi's or go to the HAL list.
>
> No, I think th
Ben Gamari wrote:
> be too difficult to implement. Am I wrong? If not, I could potentially
> take a stab at it.
Oh, I overlooked that one earlier. In the docs to ptr accel I've
described how to detect whether the server is configured to do
predictable pointer accel. The job would be defeating deri
Ben Gamari wrote:
> On 03/11/2009 11:28 AM, Simon Thum wrote:
>> lshal | grep -10 x11_driver
>>
>> might be valuable.
>
> Your wish is my command:
>
>> info.callouts.add = {'hal-acl-tool --add-device'} (string list)
...
That an awful lot. on my sys
Ben Gamari wrote:
> Hey all,
>
> Recently I've been finding that despite Xorg.log reporting several
> devices being added to my server, `xinput list` only reports two:
>
>> $ xinput list
>> "Virtual core pointer"id=0[XPointer]
>> ...
>> unknown class
>> "Virtual core keyboard"id=1
Hello all (on git xorg),
since I had to learn ruby anyway, and hello world was already written:
http://the-shoebox.org/apps/140
This is a prototypish gui for tweaking pointer acceleration, i.e. all
the goodness no other UI knows. It isn't in any way serious, and you'll
need shooes, to world's mo
Peter Hutterer wrote:
> yeah, of course. sorry. what I meant was that the value x is sent as x * (1 <<
> 16). A little test program for random values between 0 and 0x showed an
> average rounding error of 0x08.
I can't judge whether that is good or bad :)
IMO for the protocol, definition is
Dirk wrote:
> I was referring to reading /many/ manuals as a relic of the nineties.
Oh, I got that, I just used it as a starter :)
>
> I'll try this on another machine as soon as it is in debian/unstable (if
> not already)... It would be great it this works and can't be overriden
> by anything.
If
Carl Karsten wrote:
> http://dpaste.com/1931/
> xorg finds and uses the touchscreen - good.
> I need to set min/Max X/Y values - I am lost on how to do that. the #ed out
> parts either have 0 effect or disable it - mouse doesn't move when I touch.
#Option "MinX" "4100"
#Option
Dirk wrote:
> Well I had read the xset manual but it kept re-enabling itself.
I'd say it was re-enabled by something else. Probably your desktop
environment. Yet, to Xorg, a notable difference.
> I didn't know I had to read /many/ manuals to permanently disable mouse
> acceleration in Linux... bu
Peter Hutterer wrote:
> XML is merely a container format. It doesn't solve our actual problem - what
> information to send to the client.
[...]
> We're in pretty unchartered territory, with much of the UI needing to change
> anyway to accommodate for all this. Once the UI changes, the information n
Pedro Izecksohn wrote:
> On 2/24/09, Simon Thum wrote:
>> Pedro Izecksohn wrote:
>>> Where it may be found?
>> Nowhere, AFAIK.
>> You may want to know this: http://bugs.gentoo.org/show_bug.cgi?id=158476
First off, you need to use reply-all. It's an in
Pedro Izecksohn wrote:
> Where it may be found?
Nowhere, AFAIK.
You may want to know this: http://bugs.gentoo.org/show_bug.cgi?id=158476
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Bill Crawford wrote:
> In theory a lot of them shouldn't need to, because they're installed in a
> subdirectory of /usr/include, and you're intended to include
> ...
I guessed that also, but couldn' get it nailed down. Anyway, it looks
more like the OP's script is broken.
___
Simon Thum wrote:
> Pedro Izecksohn wrote:
>> pkg-config --cflags xproto
>>
>> prints a line-feed only and keysymdef.h exists in my system and it is in
>> the right place.
> Same here, on my local system (gentoo + X11 overlay). In my git tree it
> gives a good-lo
Pedro Izecksohn wrote:
> pkg-config --cflags xproto
>
> prints a line-feed only and keysymdef.h exists in my system and it is in
> the right place.
Same here, on my local system (gentoo + X11 overlay). In my git tree it
gives a good-looking -I arg.
Though I never had problems building anything.
1 - 100 of 166 matches
Mail list logo
