2009/8/3 Marc Lehmann <[email protected]>:
> On Sun, Aug 02, 2009 at 09:59:02AM +0100, Thomas Adam
> <[email protected]> wrote:
>> - $self->grab ($self->{data}{event}{time}, 1)
>> + $self->grab ($self->{data}{event}{time})
>> and $self->allow_events_async;
>>
>> # should definitely not fail
>> - $self->grab ($self->{data}{event}{time}, 1)
>> + $self->grab ($self->{data}{event}{time})
>> and $self->allow_events_async;
>
> Could somebody investigate whether the grab in the latter case fails, e.g.:
>
> $self->grab ($self->{data}{event}{time}, 1)
> and die "grab successful\n";
>
> and see if that dies (the die should cause an ungrab btw....).
I know it breaks XAllowEvents() -- I was hoping this wouldn't be a
problem. Yes, we die() here in the above, yes it ungrabs, but it
litters my screen with popup windows now, unsurprisingly. (I had
already tested this.)
> Maybe for some reason the event time ($self->{data}{event}{time}) is 0?
Nope -- very much greater than zero. :)
Marc, ten to one this is going to be a Debian/Ubuntu issue *yet*
again (I see this annoyance crop up with other open source projects
I'm involved with -- c.f. your own FAQ entry on this :P). urxvt is
most likely linked against libxcb (my copy here is -- even though I
built from CVS of course) whose APIs are in an extreme state of flux
of course.
I will look through their Changelogs to see what happened -- they've
clearly messed something up.
Sorry for the noise.
-- Thomas Adam
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
