On Tue, 2003-04-29 at 17:07, Barry Warsaw wrote:
> On Tue, 2003-04-29 at 16:43, Owen Taylor wrote:
>
> > > I did that but unfortunately, Ximian pointed the finger at Xinerama and
> > > closed the issue. :(
> >
> > If Red Carpet hangs with Xinerama and not without Xinerama, then I'd
> > strongly guess it's an X or Xlib bug of some sort.
> >
> > Not that Red Carpet might not be buggy, but it would be hard to be
> > buggy with that symptom.
> >
> > But it's the kind of X bug that we're going to trouble tracking down,
> > unfortunately.
>
> I suppose it could also be a Gtk bug, right? I don't normally use any
> of those fancy desktops (Gnome or KDE) so I probably wouldn't notice it
> much. But once I get Xinerama and dual-heads working again, I'll see if
> I can keep an eye out for which applications have trouble.
It *could* be a GTK+ bug, but my instinct says not.
How firmly I'm convinced of that depends on whether it's a gtk1 or
gtk2 based copy of Red Carpet ...
gtk1 - GTK+ doesn't know anything about Xinerama
gtk2 - GTK+ knows about Xinerama, but it doesn't affect normal
operation at all, and it's only a little bit of code.
Red Carpet is an awful example though because it's (last I knew)
it's statically linked against Ximian's own copies of the GTK+
libraries. If the problem was seen with an we ship, that would
much easier to try to do something with.
Regards,
Owen
_______________________________________________
xfree86-list mailing list
xfree86-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/xfree86-list
IRC: #xfree86 on irc.redhat.com
