traneous padding too:
...
CARD32 length B32;
CARD16 num_encodings B16;
CARD32 padl3 B32;
...
And even without this padding sz_xvQueryEncodingsReply=32 is wrong,
as the fields sum up to 34 and with that padding we're at 36.
Cheers,
Daniel Martin
--
To UNSUBSCRIBE, email to
On 10 June 2013 11:55, Julien Cristau wrote:
> On Mon, Jun 10, 2013 at 11:41:00 +0200, Daniel Martin wrote:
>
>> On 9 June 2013 19:00, Julien Cristau wrote:
>> > The padding is *before* the rate field, so the rate is placed on a 32bit
>> > boundary. This change
"Charl P. Botha" <[EMAIL PROTECTED]> writes:
> In 3.3.6 that was incidental. Your answer lies in the following:
> man xmodmap (this is what you'll use to remap keycodes to metas)
> man xev (this is what you'll use to discover keycodes)
Wasn't the xkb extension supposed to replace the interface t
Tom Joseph <[EMAIL PROTECTED]> writes:
> I had a similar problem. It turned out that not all of my FontPath
> statements in XF86Config were valid. I don't know why one of them
> suddenly became invalid, but deleting the offending line fixed things
> for me.
>
> --Tom Joseph
Blame the latest re
In trying to fix a realease-critical bug for fvwm95, I ran into
something I don't understand about how X deals with XFontSet
structures.
As I understand it, XCreateFontSet(dpy,fontname,&ml,&mc,&ds) is
supposed to allow one to have a generic font name (say "fixed") which
then is used to find the co
Sven LUTHER <[EMAIL PROTECTED]> writes:
> Hello, ...
>
> i am running uptodate potato (from yesterday) and when i boot using a
> linux-2.3.99-pre3 kernel, i got the following message when X is booting :
>
> Apr 4 12:56:46 lambda kernel: shmget: shm filesystem not mounted
>
> what is this, shou
"Charl P. Botha" <[EMAIL PROTECTED]> writes:
> In 3.3.6 that was incidental. Your answer lies in the following:
> man xmodmap (this is what you'll use to remap keycodes to metas)
> man xev (this is what you'll use to discover keycodes)
Wasn't the xkb extension supposed to replace the interface
Tom Joseph <[EMAIL PROTECTED]> writes:
> I had a similar problem. It turned out that not all of my FontPath
> statements in XF86Config were valid. I don't know why one of them
> suddenly became invalid, but deleting the offending line fixed things
> for me.
>
> --Tom Joseph
Blame the latest r
8 matches
Mail list logo
