From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 27332] Problem with libopencascade - salome-platform
Date: Wed, 17 Nov 2010 14:55:35 -0800 (PST) [thread overview]
Message-ID: <20101117225535.528CC13000D@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-27332-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=27332
--- Comment #2 from Paulo César Pereira de Andrade <pcpa@mandriva.com.br> 2010-11-17 14:55:34 PST ---
Just tested with a build of salome version 5.1.4.
Unlike when running on a computer with an intel card (bug #27333),
it now works without setting LIBGL_ALWAYS_INDIRECT, and this way
becomes fast/responsive in the opencascade viewer; vtk viewer
is very slow on both test systems (i586/i965 and x86_64/r300), and
should be a software issue as it was not so slower with salome
5.1.3. But still fills the console with these warnings:
Mesa: User error: GL_INVALID_ENUM in glIsEnabled(0xb72)
Mesa: User error: GL_INVALID_ENUM in glEnable(0xb72)
Mesa: 1 similar GL_INVALID_ENUM errors
Software version is:
$ rpm -q x11-server-xorg x11-driver-video-ati mesa lib64drm2
x11-server-xorg-1.9.2-1mdv2011.0
x11-driver-video-ati-6.13.99-0.20101029.1mdv2011.0
mesa-7.9-1mdv2011.0
lib64drm2-2.4.22-1mdv2011.0
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2010-11-17 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 19:22 [Bug 27332] New: Problem with libopencascade - salome-platform bugzilla-daemon
2010-05-06 19:48 ` [Bug 27332] " bugzilla-daemon
2010-11-17 22:55 ` bugzilla-daemon [this message]
2019-11-19 8:12 ` bugzilla-daemon
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=20101117225535.528CC13000D@annarchy.freedesktop.org \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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: link
Be 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