public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: kdo@cosmos.phy.tufts.edu Subject: Re: AIGLX Date: Sat, 05 Mar 2011 18:05:00 -0000 [thread overview] Message-ID: <4D727B84.4020005@dronecode.org.uk> (raw) In-Reply-To: <E1PlPEP-0003Q0-Sx@cosmos.phy.tufts.edu> On 04/02/2011 17:14, Ken Olum wrote: > From: Jon TURNEY <jon.turney@dronecode.org.uk> > Date: Mon, 24 Jan 2011 18:38:36 +0000 > > > Once I say -wgl, direct rendering no longer works. That is, if I > > don't set LIBGL_ALWAYS_INDIRECT, then I get a long (infinite?) > > sequence of errors like this: > > > > X Error: BadMatch (invalid parameter attributes) 8 > > Major opcode: 73 (X_GetImage) > > Resource id: 0xa0039a > > I can't reproduce this problem. Can you give me a few more details on the > host which is running paraview: unix version, version of libGL and version of > paraview? > > Mandriva 2010.2 on x86_64 with kernel 2.6.33.7-server-2mnb > libGL is from lib64mesagl1-devel-7.8.1-6mdv2010.1 > Paraview is version 3.8.1 for x86 Thanks for the info. I tried to reproduce this problem using the x86 version of the above (I don't have any hardware capable of running x64 VMs at the moment), with no success, so either it's specific to x64 in some way, or there's something else I need to do. > I don't have a clear picture of when this bug occurs and when it doesn't. > I just deleted my paraview configuration file .config/ParaView/ParaView3.8.1.ini > to start with a clean environment, and now when I type paraview it > gives me a large but finite number of these warnings and then starts > up. > > When I create objects (e.g., try Sources->Arrow) it displays them > without further errors, but extremely slowly. You can watch the > individual polygons appear on the screen. > > Do you get that error with other OpenGL applications (e.g. glxinfo) or just > paraview? > > glxinfo does not give these errors. I haven't tried any other OpenGL > application. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2011-03-05 18:05 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-19 18:53 AIGLX Ken Olum 2011-01-19 21:11 ` AIGLX Jon TURNEY 2011-01-21 17:52 ` AIGLX Ken Olum 2011-01-24 18:38 ` AIGLX Jon TURNEY 2011-02-04 17:14 ` AIGLX Ken Olum 2011-03-05 18:05 ` Jon TURNEY [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4D727B84.4020005@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=kdo@cosmos.phy.tufts.edu \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).