Julien Cristau writes:
>
> We can't call CopyArea in that case because the image has depth 1, which
> might not match the target drawable, so we might overrun the shm
> segment. Commit 11817a881cb93a89788105d1e575a468f2a8d27c apparently
> fixed a similar bug for XYPixmap, but missed the bitmap ca
I'm including here an updated version of the bug demonstration program. It
now reliably segfaults every X server I can find. (That's not a lot of them
since I haven't looked outside Debian stable.)
It does the same basic operations as the previous test program in its
bug-triggering mode, but allow
Julien Cristau writes:
>
> On Sun, Oct 30, 2011 at 20:02:43 -0500, pac...@kosh.dhis.org wrote:
>
> > Disable "dri"
> > Disable "dri2"
>
> Any particular reason you're doing this?
Because I've read the security document[1]. There's a lot of scary stuff in
there.
[1] http://dri.sourcefor
Julien Cristau writes:
>
> On Tue, Jun 7, 2011 at 23:56:08 -0500, Alan Curry wrote:
>
> > Xorg X server configuration file status:
> >
> > -rw--- 1 root root 3981 Feb 8 22:05 /etc/X11/xorg.conf
> >
> > Contents of /etc/X11/xorg.conf:
> > ---
Cyril Brulebois writes:
>
> thanks for the test case, even though I can't reproduce it. A full
> backtrace might be nice:
> http://pkg-xorg.alioth.debian.org/howto/use-gdb.html
Here's what I got from that.
(gdb) bt full
#0 0x0fb028bc in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/lin
Harald Dunkel writes:
>
> Is this a special xterm feature? "whois sensors.de" works much better
> with -k8. Would you suggest to make -k8 the default?
In a perfect world, it would be unnecessary since you wouldn't have
anything written on your terminal that wasn't in the proper charset.
In the r
Don Armstrong writes:
>
> See the attached png which shows the tiny menu in xterm. I'll dig up
> some more useful debugging info.
That looks familiar. Once, while experimenting with X resources, I added
something like this:
XTerm*Geometry: 80x30
which made the VT100 window 80x30 characters (int
Thomas Dickey writes:
> > That file is all ascii, so probably not what you wanted to attach.
>
> ascii here, too.
That must be some kind of mail system bug, closer to your end than the
submitter. Viewing on http://bugs.debian.org/584801 I can see that the
original message included this base64-enc
8 matches
Mail list logo
