Subject: Re: [nmr_sparky] Cannot see the spectrum in Sparky
From: Mandar T. Naik
Date: Sep 2, 2015

Previous: 1019 Next: 1021


Hi,
Happened to me on Monday after yum update. Seems CentOS 6.7 is out and as many as 400+ packages were updated. I am sorry but I did not make note of yum history. I suspect the X server gets updated and cause this problem. I fooled around trying to roll-over but that did not work.
Then I decided to upgrade to CentOS 7. Please do not try the in-place upgrade! It broke my system. I finally made a DVD install. Sparky runs in CentOS 7 but many old software wont. No 32-bit support in CentOS 7. May be there is a work around but I decided to downgrade to original CentOS 6.5. It seems things are back to normal although the newly installed NMRFAM Sparky comes with a blue background. Never ran it before and have only seen brown or gray colors for old sparky.
People on CentOS and related Linux may want to hold on with update till this issue is nailed. 
Best regards
-mandar

On 9/2/2015 2:36 PM, Woonghee Lee woonghee791113@... [nmr_sparky] wrote:
 

Hi,

You may be using Scientific Linux 6 that is built on RHEL 6.
I am trying to figure out what is going on, but it is more likely faulty
X11 libraries shipped out with RHEL, and in that case, it will not be a
easy fix. I will report if I can find a way to fix this problem.

Woonghee

On Wed, 2015-09-02 at 11:47 -0700, e.ab@... [nmr_sparky]
wrote:

Hi,

I seem to have the same problem with sparky.
On my machine sparky stopped displaying the spectra, just like in the
attachment earlier
in this thread.The contour panel on the right still works as well as
the trace (vS)
l
It was working fine before the weekend and Im not aware of having
changed
anything to the system or in userspace. Im not doing automatic
updates.

Its an old version of sparky 3.110 that has worked fine for a long
time. .
If I try the new NMRFAM sparky the result is the same.

Im on scientific linux.
uname -a
Linux pppp2 2.6.32-504.1.3.el6.x86_64 #1 SMP Tue Nov 11 14:19:04 CST
2014 x86_64 x86_64 x86_64 GNU/Linux


Does any one have a clue what could be wrong?

many thanks,
Eiso