On Sun, 2008-09-21 at 08:27 -0700, Corbin Simpson wrote:
Michel Dänzer wrote:
On Sun, 2008-09-21 at 13:35 +0200, Soeren Sonnenburg wrote:
[...]
(**) RADEON(0): Option GARTSize 64
(**) RADEON(0): Option FBTexPercent 0
Try without these two options.
For the former, values
On Fri, Sep 19, 2008 at 01:29:58PM +0200, Søren Hauberg wrote:
I do have a follow-up question (you can't get rid of me that easy :-)
). I have modified the 'usbtouchscreen' kernel module such that it can
use calibration parameters. With this in place, my touchscreen works
in X with the 'evdev'
Søren Hauberg wrote:
I'm sorry but I don't quite understand (I don't know that much about
either X, nor the kernel). But you think it would be better to solve
this in X, right? Via a special driver for touch screens? And then I
can use these 'device properties' to set the calibration
2008/9/22 Peter Hutterer [EMAIL PROTECTED]:
On Fri, Sep 19, 2008 at 01:29:58PM +0200, Søren Hauberg wrote:
I do have a follow-up question (you can't get rid of me that easy :-)
). I have modified the 'usbtouchscreen' kernel module such that it can
use calibration parameters. With this in
On Tue, Sep 16, 2008 at 11:58:56AM +0200, Sascha Hlusiak wrote:
BTW: With MPX, having two key devices attached to the first master device
works fine, regarding the keymap. When creating a second master and attaching
a keyboard to that, key presses seem to use the keymap of the first master
--- On Mon, 9/22/08, Michel Dänzer [EMAIL PROTECTED] wrote:
On Sun, 2008-09-21 at 13:58 +0200, Soeren Sandmann wrote:
As other people pointed out, XRender does allow
arbitrary 3x3
transformations of source images, but you are right
that the XRender
protocol would require putting the
Here's the (hopefully) final patches to device properties in the server.
As mentioned in [1], Configure/Query property functionality and requests have
been culled.
Patch 1 removes these requests. An updated inputproto is required as well of
course.
Patch 2 allows property handlers to return
From: Peter Hutterer [EMAIL PROTECTED]
Add delete parameter to SetProperty handler, handlers can refuse to delete a
property by returning something other than Success.
---
Xi/xiproperty.c| 20 ++--
dix/devices.c |6 +-
include/exevents.h |3 ++-
Hi Peter,
its good news you're done with that. A thing though:
-DeviceSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop)
+DeviceSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop,
+ BOOL delete)
{
if (property ==
As I'm tired of constant fighting with nvidia (and nvidia obsoleted my
current graphics card, GeForce FX 5200), I'm looking for a graphics card
which has open drivers and is well supported.
If it matters, I use 32 bit Linux.
I looked a bit in X.org wiki, and it seems to me that Radeons with
On Fri, 2008-09-19 at 16:55 -0700, Keith Packard wrote:
On Fri, 2008-09-19 at 13:52 -0400, Adam Jackson wrote:
You don't ask for the stipple though. It's the default.
My point was that if you want to avoid the vintage X appearance, you'd
likely start the X server with a black root window
On Fri, 2008-09-19 at 17:27 -0400, Owen Taylor wrote:
I found that
XFixesChangeSaveSet (..., SaveSetRoot, SaveSetUnmap);
isn't working as expected ... when the client terminates, the save-set
window will be reparented to the root window, but the window manager
will get a MapRequest
On Mon, Sep 22, 2008 at 12:15:33PM +0930, Peter Hutterer wrote:
According to Section 12.4 of the XKB Protocol Spec, if a key only has a single
group but the keyboard has multiple groups defined, the core description of
the key is a duplication of the single group across all symbols. i.e.
G1L1
Yan Seiner wrote:
I am new to building X. I'd like to take a shot at building Xephyr from git.
I've been through the instructions on
http://www.x.org/wiki/Development/git but xserver doesn't appear to have
xephyr.
Is there a list somewhere of what module contains which part? Where do
Hello,
the current git head of the Xserver segfaults on any keystroke. Trace is
attached:
(I have the core file and all the binaries, if interested)
Core was generated by `/usr/local/X11R7.5/bin/Xorg :1.0'.
Program terminated with signal 11, Segmentation fault.
[New process 28180]
#0
On Mon, 22 Sep 2008 14:09:45 -0400
Adam K Kirchhoff [EMAIL PROTECTED] wrote:
I'm trying to get that combination working on my i915 laptop, but I'm
running into a problem... Namely, Xorg is crashing:
X.Org X Server 1.5.0
Release Date:
X Protocol Version 11, Revision 0
Build Operating
On Mon, 22 Sep 2008 18:02:25 -0400
Adam K Kirchhoff [EMAIL PROTECTED] wrote:
On Mon, 22 Sep 2008 14:09:45 -0400
Adam K Kirchhoff [EMAIL PROTECTED] wrote:
I'm trying to get that combination working on my i915 laptop, but
I'm running into a problem... Namely, Xorg is crashing:
Hi,
On Mon, Sep 22, 2008 at 10:56:03AM -0400, Adam Jackson wrote:
Right then. -br is now the default. -retro gives you the old school
root window and cursor behavior.
I don't understand why you don't leave the default as it was. Sureley
the only situation where it is inconvenient to have to
Problem: Many[1] users have killed X by accident.[2]
Solution idea: Make it harder to kill X by accident. E.g. you could
change the key sequence users must press.
* Maybe require Control+Alt+Backspace then Control-Alt-Y.[3]
* Or require Control+K+X pressed simultaneously.
What do you
Igor Mozolevsky igor at hybrid-lab.co.uk writes:
CTRL+ALT+BACKSPACE is just the way to do it
OK. That's one no vote, duly noted. Thank you for your vote.
I will now respond to the rest of your comments.
just because users
incompetently press the combination, doesn't mean it's a bad one.
Jason Spiro escreveu:
Problem: Many[1] users have killed X by accident.[2]
Solution idea: Make it harder to kill X by accident. E.g. you could
change the key sequence users must press.
* Maybe require Control+Alt+Backspace then Control-Alt-Y.[3]
* Or require Control+K+X pressed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Spiro wrote:
Problem: Many[1] users have killed X by accident.[2]
Solution idea: Make it harder to kill X by accident. E.g. you could
change the key sequence users must press.
* Maybe require Control+Alt+Backspace then
2008/9/23 Jason Spiro [EMAIL PROTECTED]:
Igor Mozolevsky igor at hybrid-lab.co.uk writes:
just because users
incompetently press the combination, doesn't mean it's a bad one.
I respectfully disagree. Accidental zaps often cause data loss. Data loss is
always unacceptable and Xorg should
Igor Mozolevsky igor at hybrid-lab.co.uk wrote:
...
Unfortunately, there's no cure for human
stupidity
There's no cure, but there are workarounds.
Doesn't CTRL+ALT+DELETE reboot the machine unconditionally?
Not usually. It used to reboot unconditionally way back. But, fifteen years
ago,
Corbin Simpson mostawesomedude at gmail.com writes:
...
Seriously, no.
Your vote has been duly noted.
Zap once, learn forever. No different than anything else,
really;
I still believe that Xorg should make it harder to make the mistake of an
accidental zap.
ever heard of press Alt+F4 to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Spiro wrote:
Corbin Simpson mostawesomedude at gmail.com writes:
...
Seriously, no.
Your vote has been duly noted.
Zap once, learn forever. No different than anything else,
really;
I still believe that Xorg should make it harder to
On Tue, Sep 23, 2008 at 02:41:16AM +, Jason Spiro wrote:
Problem: Many[1] users have killed X by accident.[2]
Solution idea: Make it harder to kill X by accident. E.g. you could
change the key sequence users must press.
* Maybe require Control+Alt+Backspace then Control-Alt-Y.[3]
On Tue, Sep 23, 2008 at 04:39:49AM +, Jason Spiro wrote:
Thanks for the info. 1. So I guess when using evdev, a way to implement my
Ctrl+Alt+Bksp then Ctrl+Alt+Y idea would be this?: Ctrl+Alt+Bksp should latch
some new modifier called ctrl_alt_bksp_was_pressed, and Ctrl+Alt+Y should zap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Spiro wrote:
Plus, due to the psychological effect called groupthink, people who would
have
said yes are now less likely to admit it to the entire list, since IIRC
three
have already said no and only one (me) has said yes. :(
Ctrl+K+X
29 matches
Mail list logo
