Re: [gtk-vnc-devel] PATCH: Fix crash in OpenGL scaling code
- From: "Daniel P. Berrange" <berrange redhat com>
- To: Rob Stoddard <rstoddard telanetix com>
- Cc: gtk-vnc-devel List <gtk-vnc-devel lists sourceforge net>
- Subject: Re: [gtk-vnc-devel] PATCH: Fix crash in OpenGL scaling code
- Date: Tue, 11 Mar 2008 20:02:21 +0000
On Fri, Mar 07, 2008 at 08:18:58AM -0800, Rob Stoddard wrote:
> Yes, it would fix that problem.
>
> I ran into another problem which this widget brings to light, a problem
> with gtkglext which has to do with colormaps. It happens rarely, but a
> quick and dirty fix for the problem is to set the environment variable
> (either before calling the program, or in the program with a putenv()
> call) GDK_GL_NO+STANDARD_COLORMAP=1. The problem is a BadColor error
> that causes X to stop working with any gtkglext program until it is
> restarted. Like I said before, this is not a problem with gtk-vnc, it's
> a problem with gtkglext. The first time I have run into it was with
> this widget, however, so there is something that this widget does to
> trigger this issue. What it might be, I have no idea.
I've hit this now too. I've not figured out just what's going wrong but
basically there's a property on the root window specifying a default
colormap which is getting set to a bogus value, for unknown reasons.
You dont need to re-start X though - just run
xprop -remove RGB_DEFAULT_MAP -root
It hit me when I tried to connect to a regular VNC server running at
16bpp. That may have just been co-incidence though - need to investigate
it more.
Dan.
--
|: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]