On Tue, 2008-09-23 at 03:20 +, Jason Spiro wrote:
> Tiago Vignatti c3sl.ufpr.br> wrote:
> >
> > The "DontZap" option in xorg.conf isn't enough for you? `man 5 xorg.conf`
>
> It would work fine for me. But it's not good enough for most users, since
> most
> Xorg users don't know how to edit
Adam Jackson wrote:
> 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 s
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]
>* Or require Control+K+X pressed si
On Mon, Sep 22, 2008 at 08:08:37PM +0200, Lukas Hejtmanek wrote:
> the current git head of the Xserver segfaults on any keystroke. Trace is
> attached:
Can I have a log please?
Cheers,
Peter
___
xorg mailing list
xorg@lists.freedesktop.org
http://list
On Tue, Sep 23, 2008 at 10:34 AM, Russell Whitaker <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 23 Sep 2008, 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 pres
On Tue, 23 Sep 2008, 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]
* Or require Contr
-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". :(
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
Peter Hutterer who-t.net> wrote:
>
> driver kbd: hardcodes Ctrl + Alt + Backspace. (IMHO that's a bug anyway)
> driver evdev: the XKB map decides what happens.
>
> In the latter case, all you have to do is change the xkb map. If you can
> convice svu to add it to xkeyboard-config, you only need
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jason Spiro wrote:
> Corbin Simpson 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
Corbin Simpson 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 make it go fast
Igor Mozolevsky 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, when
2008/9/23 Jason Spiro <[EMAIL PROTECTED]>:
> Igor Mozolevsky 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 shou
Jason Spiro escreveu:
> Tiago Vignatti c3sl.ufpr.br> wrote:
>> The "DontZap" option in xorg.conf isn't enough for you? `man 5 xorg.conf`
>
> It would work fine for me. But it's not good enough for most users, since
> most
> Xorg users don't know how to edit their xorg.conf files.
>
> You could
-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 Control-Alt
Tiago Vignatti c3sl.ufpr.br> wrote:
>
> The "DontZap" option in xorg.conf isn't enough for you? `man 5 xorg.conf`
It would work fine for me. But it's not good enough for most users, since most
Xorg users don't know how to edit their xorg.conf files.
You could argue that distros could disable za
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
Igor Mozolevsky 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.
I
2008/9/23 Jason Spiro <[EMAIL PROTECTED]>:
>
> 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
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 thi
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 t
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 cras
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 Op
On Mon, 2008-09-22 at 14:03 -0400, Owen Taylor wrote:
> Well, at least I understand now why you called it 'remap' :-) Patches
> attached.
Thanks. I edited your spec changes a bit but applied the code changes
verbatim.
--
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed
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 System: FreeBSD 7.1-PRERELEASE i386
Current Operating System: FreeBSD scroll.ashke.com 7.
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 0x7f02
On Mon, 2008-09-22 at 10:14 -0700, Keith Packard wrote:
> On Mon, 2008-09-22 at 11:05 -0400, Adam Jackson wrote:
> > On Fri, 2008-09-19 at 17:27 -0400, Owen Taylor wrote:
> > > I found that
> > >
> > >XFixesChangeSaveSet (..., SaveSetRoot, SaveSetUnmap);
> > >
> > > isn't working as expected
On Mon, 2008-09-22 at 11:05 -0400, Adam Jackson wrote:
> 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 repar
On Fri, 2008-09-19 at 13:50 -0400, Adam Jackson wrote:
> On Fri, 2008-09-19 at 17:54 +0100, David Gerard wrote:
> > http://www.linux.com/feature/148339
> >
> > SGI used their "or later" privilege to upgrade to the X11 licence. w00t!
>
> I've updated the server source in git to reflect FreeB 2.0.
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? Wher
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.
> G1
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 MapRequ
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 roo
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
I find xephyr?
Thanks,
-
On Mon, 2008-09-22 at 18:08 +0930, Peter Hutterer wrote:
> 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 a
On Mon, 2008-09-22 at 08:56 +0200, Søren Hauberg wrote:
> Hi,
> I've making some changes tu the usbtouchscreen module to handle
> calibration stuff (see another thread on this list). This module
> currently emits BTN_TOUCH whenever the user touches the screen (I
> haven't changed this). When I'm
>> Even if you do not want to do stretch, I believe that the X Render
>> extension would require first copying the YUV data to a drawable and
>> then doing a drawable->drawable block transfer operation to do the
>> YUV transformation. In comparison, XvPutImage is a single call
>> takes an XImage,
Peter Hutterer wrote:
> Without the handler disallowing that, a client could potentially delete
> properties that are "owned" by the server or a driver.
Ooops, I thought you were keeping the fromClient bit internally. Now it
makes much more sense :)
Cheers,
Simon
___
On Mon, Sep 22, 2008 at 11:30:59AM +0200, Simon Thum wrote:
>> -DeviceSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop)
>> +DeviceSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop,
>> + BOOL delete)
>> {
>> if (property == XIGetKnownProp
On Mon, Sep 22, 2008 at 11:27:29 +0200, Tomasz Chmielewski wrote:
[...]
> I looked a bit in X.org wiki, and it seems to me that Radeons with
> chipsets R400 should be sufficient for me. Unfortunately it's hard for
> me to find which chipset does a given Radeon card have (i.e. HD2400Pro -
> doe
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 == XIGetKnownProp
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
chi
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 ++-
include/
From: Peter Hutterer <[EMAIL PROTECTED]>
If a property handler now bails out, return the error code to the caller. This
allows to be slightly more specific with the errors.
---
Xi/xiproperty.c| 63 +--
dix/devices.c |7 ++---
include/
From: Peter Hutterer <[EMAIL PROTECTED]>
This removes all the meta-information about device properties (pending,
fromClient, range, valid_values, immutable).
---
Xi/extinit.c | 58 +--
Xi/xiproperty.c| 282
Xi/xiproperty.h
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 status
--- 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 putti
On Sun, 2008-09-21 at 13:58 +0200, Soeren Sandmann wrote:
> Adam Richter <[EMAIL PROTECTED]> writes:
>
> > Even if you do not want to do stretch, I believe that the X Render
> > extension would require first copying the YUV data to a drawable and
> > then doing a drawable->drawable block transfer
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
50 matches
Mail list logo
