VMD-L Mailing List

From: POTTER T.D. (thomas.d.potter_at_durham.ac.uk)
Date: Wed Oct 18 2017 - 05:31:53 CDT

Hi,

I managed to fix the issue, one of the modules I use was loading some
out of date libraries.

Tom

On 17/10/17 20:10, John Stone wrote:
> Hi,
> Are you able to run "glxgears" on the same remote linux cluster?
> If you can't run glxgears, then VMD isn't likely to work either,
> since it needs far more graphics functionality than glxgears does.
> Try glxgears and let me know if it runs or not. Also, what output
> do you get if you run "glxinfo" on that remote linux cluster?
>
> Best regards,
> John Stone
> vmd_at_ks.uiuc.edu
>
> On Tue, Oct 17, 2017 at 02:20:07PM +0100, POTTER T.D. wrote:
>> Hi all,
>>
>> I'm trying to use vmd on a remote linux cluster, which I ssh into
>> from a Ubuntu 14.04 desktop.
>>
>> When I try to load a file, I get the following output:
>>
>> vmd > XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>> XRequest.154: BadMatch (invalid parameter attributes) 0x4c00009
>>
>> The vmd window opens, but I am not able to view any molecules. On
>> closing the window, I get the following output:
>>
>> Info) VMD for LINUXAMD64, version 1.9.1 (February 1, 2012)
>> Info) Exiting normally.
>> XRequest.154: GLXBadContext 0x4c00001
>>
>> When I try to log in from a different computer, I get the same
>> error. However, other users on the cluster are able to use vmd
>> without problems, so there must be an issue somewhere with my
>> settings. Does anyone know what could be causing this issue?
>>
>> Thanks,
>>
>> Tom