From: Nicolas B. <nbi...@gm...> - 2010-08-17 23:09:32
|
Thanx for your answer. It's certainly not obvious what the problem is, but here are two small > ideas: > Indeed... > 1) Sometimes problems of this kind stem from a need to update the > graphics drivers. I'm inclined to think that's not your problem, > because you crash just trying to import visual, before creating any > objects. > My driver is up to date: xf86-video-intel 2.12.0-1 > 2) I see that the visual machinery is in > /usr/lib/python2.6/site-packages. I don't know anything about > Arch-Linux, but on Ubuntu there was a recent change involving > dist-packages as opposed to site-packages. Is it conceivable that your > builds have put the newly compiled files somewhere not in > /usr/lib/python2.6/site-packages, but there is something in > /usr/lib/python2.6/site-packages that is corrupted? > VPython is installed in /usr/lib/python2.6/site-packages/visual/. The package is built by Arch devs with: > pythondir=`python -c "from distutils import sysconfig; print > sysconfig.get_python_lib()"` > unset PYTHONPATH > ./configure --prefix=/usr \ > --with-example-dir=$pythondir/visual/demos > Curious that VPython works on one of you machines but not on two others.... > I just though about it too and the only difference between these machines is that the failing one have integrated intel card, while the one which is working has an nvidia. 3D is working fine on the integrated card: I run KDE/kwin with composition on without any problem. I can even play some games on these machines... |