It is not a Ubuntu problem. I have the same issue on my laptop, and
it's because it has Intel onboard graphics chip. With NVIDIA cards (at
least on all the desktops I've seen), coot runs fine when you enable
compiz (of course, I do use proprietary nvidia drivers).
On Tue, 2009-05-12 at 14:34
Hello ,
The jaunty 32 bit build seems to fail ( with subversion revision 2002 as
well)
It seems like based on what Ed Pozharsky wrote in ..its a problem with guile
in Ubuntu jaunty (9.04) ..
On my 32 bit , 9.04 installation , the build-it-gtk2-simple script chugs
along fine and then declares the
I have the following guile-like stuff installed, if it is of any help:
diablo-% which dpkg-list
dpkg-list () {
dpkg --list \...@\*
}
diablo-% dpkg-list guile | grep ii
ii guile-1.6-libs
1.6.8-6.3ubuntu1 Main Guile libraries
ii
Didn't help.
It must have something to do with my configuration. I have no problems
on other machines running Hardy.
Which executable actually requires this library? I put ldd $coot_real
into the xxx/bin/coot script, and it does list many libraries in xxx/lib
properly. However, the one in
I'm running this in undergraduate teaching labs containing cheap Dell
boxes or iMacs, both of which are only a couple of years old. Off-hand
I don't know what graphics cards the former have, but the latter
should have nVidia cards. Maybe it's the drivers?
--
Dr J. Shaun Lott
AgResearch
Hi,
I like the fit protein script - at low resolution, initial rounds of
fitting and refinement often result in my leucines/isoleucines having
fairly implausible rotamers, and fit protein is a great way of quickly
fixing up the worst of these.
However, it doesn't seem to deal so well