Hugo Vanwoerkom schrieb:
I run such a 2-seater under Debian Sid. 2
cards/monitors/keyboards/mice/servers. But the recent xorg (1:7.3+10) gives an
error message:
Hello,
perhaps an update would help as the current xorg for sid is 1:7.3+17[1].
Furthermore I am running a multi seat environment
On Tue, Sep 30, 2008 at 01:56:12AM +0300, Daniel Stone wrote:
> Can you not just ship a null cursor theme or something if your apps
> insist on setting a cursor?
hmm, starting just Xserver and xterm makes it unusable, no cursor and the xterm
cannot be focused.
--
Lukáš Hejtmánek
I tried to get Xgl running with compiz.
[EMAIL PROTECTED]:~$ Xgl :1 -ac &
[1] 22647
[EMAIL PROTECTED]:~$ Could not init font path element
/usr/share/fonts/X11/TTF/, removing from list!
Could not init font path element /usr/share/fonts/X11/OTF, removing from list!
Could not init font path element /
Olivier Guerrier wrote:
> Daniel Stone wrote:
>> Can you not just ship a null cursor theme or something if your apps
>> insist on setting a cursor?
>
> We considered that, but it is unreliable (how about hard coded cursor
> for exemple), need in-depth testing/validating, and as a consequence eat
>
> Hmm, that seems a little odd. Seems like there are three camps here:
>* People writing display drivers (let's call them 'the minority')
> want a stipple and cursor. -> -retro
>* People starting regular desktop environments want the default
> behaviour. (Though I have slight d
Hi lists,
In libX11 1.1.2 (and newer), XNextEvent() sometimes segfault by null
exception.
This problem look like come from _XReadEvents()/_XSend() behavior.
The problem is not reproduce in 1.1.1 and old.
Compiz and IIIMF fall under this problem, but these are typically
example, I think that many
mmh,
i am not an expenrt on xorg internal but why not add
if (!XPending()) return; to XNextEvent(); ?
that would translate old stile loop into the new form
and leave other programs with 2 Pending() calls, what
should be harmless. in the long run the if would eliminate
the if XPending() from all th
2008/9/29 Peter Hutterer <[EMAIL PROTECTED]>:
> Søren:
>
> On Mon, Sep 29, 2008 at 01:29:35PM +0200, Søren Hauberg wrote:
>> > Sorry, I wanted to suggest that in reply but missed it. Anyway, be aware
>> > that as your patch is now, you're also triggering on absolute axes you
>> > can't
>> > handle
Hi walter,
> i am not an expenrt on xorg internal but why not add
> if (!XPending()) return; to XNextEvent(); ?
It is very smart. But it is not backward-compatible(maybe).
XNextEvent() difiniton is
| int XNextEvent(Display *display, XEvent *event_return);
and, typicial classical loop is below.
On Sep 29, 08 13:53:08 -0300, André Tupinambá wrote:
> What is the pixman version that you are using? This bug looks like a
> this one (https://bugs.freedesktop.org/show_bug.cgi?id=17477) and it
> is already fixed in pixman 0.12.0.
F*ck. You're absolutely, perfectly, right.
Sorry for the fuzz. I
On Sun, 2008-09-28 at 18:46 +0200, Bernie Innocenti wrote:
> Tomeu Vizoso wrote:
>
> > On Sun, Sep 28, 2008 at 12:46 PM, Riccardo Lucchese
> > <[EMAIL PROTECTED]> wrote:
> >> On Sun, 2008-09-28 at 12:43 +0200, Riccardo Lucchese wrote:
> >>> * build 703, xorg driver = amd, redraws = 200
> >>> - pi
Hi all,
What was the conclusion about the weave pattern? I don't care what
the default is, but is it possible to get the root weave background as
a compile time / run time option? Or has the weave background gone
for good?
Thanks!
John Tapsell
__
On Tue, Sep 30, 2008 at 12:25:01PM +0100, John Tapsell wrote:
> What was the conclusion about the weave pattern? I don't care what
> the default is, but is it possible to get the root weave background as
> a compile time / run time option? Or has the weave background gone
> for good?
It neve
On Tue, Sep 30, 2008 at 12:25:01 +0100, John Tapsell wrote:
> Hi all,
>
> What was the conclusion about the weave pattern? I don't care what
> the default is, but is it possible to get the root weave background as
> a compile time / run time option? Or has the weave background gone
> for go
The following command solves the problem.
[EMAIL PROTECTED]:~$ Xgl :1 -ac -accel glx:fbo &
"-accel glx:fbo" or "-accel glx:pbuffer" enables the accelerated glx.
On Tue, Sep 30, 2008 at 5:13 PM, KwangYul Seo <[EMAIL PROTECTED]> wrote:
> I tried to get Xgl running with compiz.
>
> [EMAIL PROTECT
2008/9/30 Julien Cristau <[EMAIL PROTECTED]>:
> On Tue, Sep 30, 2008 at 12:25:01 +0100, John Tapsell wrote:
>
>> Hi all,
>>
>> What was the conclusion about the weave pattern? I don't care what
>> the default is, but is it possible to get the root weave background as
>> a compile time / run time
2008/9/29 Peter Hutterer <[EMAIL PROTECTED]>:
> evdev already has the code for device properties in e.g. draglock.c. Best to
> just check it but maybe wait a day or so, I have changes in the pipe that
> restructure the use of DP in evdev. The API is the same, but the handler
> registration is a bit
On Tue, Sep 30, 2008 at 02:15:45PM +0200, Søren Hauberg wrote:
> 2008/9/29 Peter Hutterer <[EMAIL PROTECTED]>:
> > evdev already has the code for device properties in e.g. draglock.c. Best to
> > just check it but maybe wait a day or so, I have changes in the pipe that
> > restructure the use of DP
On Tue, Sep 30, 2008 at 11:53:44AM +0200, Søren Hauberg wrote:
> Okay, so I'm attaching my latest patch. This should handle everything
> except setting/getting calibration parameters. I'll look into this
> after lunch today. I'd love some feedback on the patch, as I think
> this is the best structu
2008/9/30 Peter Hutterer <[EMAIL PROTECTED]>:
> On Tue, Sep 30, 2008 at 11:53:44AM +0200, Søren Hauberg wrote:
>> Okay, so I'm attaching my latest patch. This should handle everything
>> except setting/getting calibration parameters. I'll look into this
>> after lunch today. I'd love some feedback
On Tue, Sep 30, 2008 at 03:14:17PM +0200, Søren Hauberg wrote:
> My impression is that the ones in EvdevRec means something different.
> The ones in the 'touchscreen' struct are the calibration parameters.
> 'min_x' is the smallest x value that the hardware actually sends, and
> similar for the oth
On 2008.09.28 15:02:40 +0800, Ma, Ling wrote:
> Hi ,
>
> If the ViewSonic display (EDID vendor "VSC", prod id 19227) is changed to low
> than "1280x1024" ( 800x600, 640x480,
>
> 1024x768), there are 2 black borders on the top and bottom of the screen,
> while
> resolution with "1280x1024" works
Hi all,
I have a device without a keyboard, but I still send keyboard events
to X. Specifically I use synergy.
But just running Xorg, the keyboard events don't seem to be passed
through by synergy to X.
If I try adding a keyboard like:
Section "InputDevice"
Identifier "Keyboard0"
2008/9/30 Peter Hutterer <[EMAIL PROTECTED]>:
> On Tue, Sep 30, 2008 at 03:14:17PM +0200, Søren Hauberg wrote:
>> My impression is that the ones in EvdevRec means something different.
>> The ones in the 'touchscreen' struct are the calibration parameters.
>> 'min_x' is the smallest x value that the
Okay, here's my latest attempt at a patch. I've renamed "flip_[x|y]"
to "invert_[x|y]" and moved them into "EvdevRec", I've removed
"swap_xy", and I've moved the reading of parameters to PreInit.
I hope that's what you wanted. If not let me know. I'm hoping to have
access to the touch screen for a
Juliusz Chroboczek <[EMAIL PROTECTED]> writes:
> Note that this is on core 2, which has magnificent SSE performance.
> I haven't tried it, but I'm willing to bet that on Pentium-M and
> Pentium 4, the results are similar for SSE and MMX.
Actually they are not, but that's because gcc 4 generates m
I have a new Dell Inspiron computer with built-in Intel 82G33/G31 video.
The Intel driver apparently doesn't recognize this specific chipset and
defaults to using vesa, which doesn't support my monitor's native
resolution of 1680x1050.
Is there any work being done to support this 82G33 chip
Hi All,
I don't quite know where to publish this, so I figured this list
would be a start. Attached is a program for calibrating a touch
screen. It computes the following parameters:
'flip_x'
a boolean parameter that determines if the x-coordinate should
be flipped.
'flip_y'
Daniel Stone wrote:
> On Mon, Sep 29, 2008 at 11:08:04PM +0200, Olivier Guerrier wrote:
>
>
> * People running consumer/embedded systems who can't trust their
> apps not to try to change the cursors want to silently drop all
> cursor rendering. -> patch required if deemed useful
On Tue, Sep 30, 2008 at 05:28:52PM +0100, Barry Scott wrote:
> Daniel Stone wrote:
>> On Mon, Sep 29, 2008 at 11:08:04PM +0200, Olivier Guerrier wrote:
>>
>>
>> * People running consumer/embedded systems who can't trust their
>> apps not to try to change the cursors want to silently dr
On 14:16 Tue 30 Sep , Peter Hutterer wrote:
> Just to get a general opinion: with each driver having their own properties,
> it's a good idea to let the driver install a .h file listing all property
> names. see synaptics-properties.h, evdev-properties.h and probably more to
> come.
>
> Anyone
On Tue, Sep 30, 2008 at 14:16:03 +0930, Peter Hutterer wrote:
> Anyone opposed to a follow-up patch to install the .pc file?
> If not, xorg-.pc or just.pc?
>
xorg- sounds better to me.
Cheers,
Julien
___
xorg mailing list
xorg@lists.freedesktop.org
htt
Michel Dänzer wrote:
> On Sun, 2008-09-28 at 18:46 +0200, Bernie Innocenti wrote:
>> Tomeu Vizoso wrote:
>>
>>> On Sun, Sep 28, 2008 at 12:46 PM, Riccardo Lucchese
>>> <[EMAIL PROTECTED]> wrote:
On Sun, 2008-09-28 at 12:43 +0200, Riccardo Lucchese wrote:
> * build 703, xorg driver = amd,
Where are the sources for Xnest to be found? I've been browsing
http://cgit.freedesktop.org/, especially under the xorg/xserver
repository, but I'm not having any luck finding Xnest.
Thanks in advance.
___
xorg mailing list
xorg@lists.freedesktop.org
ht
hw/xnest in xorg/xserver
On Sep 30, 2008, at 13:47, tsuraan wrote:
Where are the sources for Xnest to be found? I've been browsing
http://cgit.freedesktop.org/, especially under the xorg/xserver
repository, but I'm not having any luck finding Xnest.
Thanks in advance.
tsuraan wrote:
> Where are the sources for Xnest to be found? I've been browsing
> http://cgit.freedesktop.org/, especially under the xorg/xserver
> repository, but I'm not having any luck finding Xnest.
hw/xnest inside xorg/server, i.e.:
http://cgit.freedesktop.org/xorg/xserver/tree/hw/xnest
--
On Mon, September 29, 2008 3:07 am, Thomas Ilnseher wrote:
>
> Am Freitag, den 26.09.2008, 13:42 -0700 schrieb Yan Seiner:
>> I am trying to get Xephyr running with compiz. The following was
>> generated with xserver 1.5.0 and xephyr 1.5.0. I've had the same
>> results
>> with 1.5.1.
>
> Why not
On 30/09/2008, Jeremy Huddleston <[EMAIL PROTECTED]> wrote:
> hw/xnest in xorg/xserver
Thanks!
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
The autumn is here, world finances are tits up - but there is one
thing you can be sure of. xkeyboard-config release 1.4.
So, it is here.
As usual, some bugs are fixed (31), new layouts/models/options,
updated translations
(thanks to TP). Most significant change: added ruleset 'evdev'. It is
used
Peter Hutterer wrote:
> On Tue, Sep 30, 2008 at 11:53:44AM +0200, Søren Hauberg wrote:
>> Okay, so I'm attaching my latest patch. This should handle everything
>> except setting/getting calibration parameters. I'll look into this
>> after lunch today. I'd love some feedback on the patch, as I think
On Tue, 2008-09-30 at 17:28 +0100, Barry Scott wrote:
> For example mozilla (mozembed). The -nocursor patch avoids the need to
> modify
> any app code at all to remove the unwanted cursors.
Have you tried the XFixes HideCursor request yet? That disables the
cursor on a specific screen.
--
[EMA
On Tue, Sep 30, 2008 at 10:54:51AM -0700, Donnie Berkholz wrote:
> > Anyone opposed to a follow-up patch to install the .pc file?
> > If not, xorg-.pc or just.pc?
>
> If this is going in every driver, would it make sense as part of
> xorg-macros? Also I'm wondering whether the sdk dir should be
On Tue, Sep 30, 2008 at 6:06 PM, Peter Hutterer
<[EMAIL PROTECTED]> wrote:
> On Tue, Sep 30, 2008 at 10:54:51AM -0700, Donnie Berkholz wrote:
>> > Anyone opposed to a follow-up patch to install the .pc file?
>> > If not, xorg-.pc or just.pc?
>>
>> If this is going in every driver, would it make sen
On Tue, Sep 30, 2008 at 08:04:50PM -0700, Dan Nicholson wrote:
> Total nitpicking, but it's not necessary to add xorg-evdev.pc.in to
> EXTRA_DIST since you added it to AC_OUTPUT in configure.ac. automake
> takes into account files necessary for autoconf and adds them to
> DIST_COMMON.
Nitpicking i
Greetings all;
In my quest to build a box that will run google sketchup, I finally
threw money at it.
New ASUS mobo, quad core AMD Phenom, 4GB. From lspci -v
03:00.0 VGA compatible controller: ATI Technologies Inc Unknown device 94c3
(prog-if 00 [VGA controller])
Subsystem: Diamond Mul
On Tue, Sep 30, 2008 at 11:17 PM, Gene Heskett <[EMAIL PROTECTED]> wrote:
> Greetings all;
>
> In my quest to build a box that will run google sketchup, I finally
> threw money at it.
[snip]
> From Xorg.0.log, I learn that this Diamond 2400HD-Pro is an R600
> chipset, and that support is very thin
On Tue, Sep 30, 2008 at 04:56:57PM +0200, Søren Hauberg wrote:
> Okay, here's my latest attempt at a patch. I've renamed "flip_[x|y]"
> to "invert_[x|y]" and moved them into "EvdevRec", I've removed
> "swap_xy", and I've moved the reading of parameters to PreInit.
>
> I hope that's what you wanted
2008/10/1 Peter Hutterer <[EMAIL PROTECTED]>:
> Ok, I took your patches, split them up and fiddled with them a bit.
Great, Thanks! I'm hoping to get an hour or so with the touch screen
on friday. Then I'll test, to make sure things are working. Also, I
hope to borrow a different touch screen from
On Wed, Oct 01, 2008 at 12:21:06AM +0200, Simon Thum wrote:
> typedef struct _AbsoluteClassRec {
> /* Calibration. */
> int min_x;
> int max_x;
> int min_y;
> int max_y;
> int flip_x;
> int flip_y;
> int r
49 matches
Mail list logo
