Hello,
I'm not sure what is causing that first problem, but I did make one change
that could be impacting this, and that is that if the AnalysisProfile
repository (so the thing it is complaining about) has a path which is not
writeable/executable by you then it repoints it to your ~/.ccpn/data
directory. It should pop up a Warning message with that mentioned (near
the bottom) if it has done this. It would say something like "generalData
has been changed from ... to ...". But if your project has not moved it
should not cause a problem unless that access check is going horribly
wrong somehow.
On the second issue, the ExtendNmr release API is a superset of the
current Analysis release API, and in particular there is a package for
Haddock in the former that is not in the latter. I thought we have made
the API so that it would ignore the situation that you have come across
(assuming I am understanding what has happened correctly). I think you
can edit the file (so by hand):
/home/vitaliy/sk45m/CCPN/Sk45m/memops/Implementation/Sk45m.xml
and fix this. First back that file up just in case. Then look for the
first line that mentions currentHaddockProject and delete from that to the
last line that mentions it (I think this will be 6 lines total) and save.
But it will be interesting to see if you still have that first problem
then.
Back to the first problem, while you are editing that Sk45m.xml file, look
for a line that has a "generalData" (without the quotes) in it. It
doesn't have to occur (depending on the history of the project) but if it
does then 6 lines down you should see a line that says something like:
<IMPL.PathString>/Users/wab104/.ccpn/data</IMPL.PathString>
If you "ls -l" that path then it should have writeable (w) and executable
(x) permissions for you (assuming it exists). If it does then I'm not
sure how the change I made yesterday would have impacted you.
Wayne
On Wed, 9 Jun 2010, Vitaliy wrote:
> Hello:
>
> I can not open my project which was killed with this output:
> X Error of failed request: BadIDChoice (invalid resource ID chosen for this connection)
> Major opcode of failed request: 148 (RENDER)
> Minor opcode of failed request: 4 (RenderCreatePicture)
> Resource id in failed request: 0x2d19531
> Serial number of failed request: 52759630
> Current serial number in output stream: 52760669
>
> Then I updated CCPN and now I am getting this:
>
> Traceback (most recent call last):
> File "/usr/local/ccpnmr/ccpnmr2.1/python/ccpnmr/analysis/AnalysisGui.py", line 231, in <module>
> main(projectDir, max_size, glDirect)
> File "/usr/local/ccpnmr/ccpnmr2.1/python/ccpnmr/analysis/AnalysisGui.py", line 118, in main
> top.initProject(project)
> File "/usr/local/ccpnmr/ccpnmr2.1/python/ccpnmr/analysis/AnalysisPopup.py", line 1413, in initProject
> Analysis.initProject(self, project)
> File "/usr/local/ccpnmr/ccpnmr2.1/python/ccpnmr/analysis/Analysis.py", line 284, in initProject
> Util.defaultColors(project)
> File "ccpnmr/ccpnmr2.1/python/ccpnmr/analysis/core/Util.py", line 1150, in defaultColors
> File "ccpnmr/ccpnmr2.1/python/ccpnmr/api/AnalysisProfile.py", line 1678, in getColorSchemes
> File "ccpnmr/ccpnmr2.1/python/memops/api/Implementation.py", line 5068, in load
> memops.general.Implementation.ApiError: No active repository found for TopObject <ccpnmr.AnalysisProfile.AnalysisProfile ['B3']>
>>>>
>
> Interestingly, I can open it with unpatched CCPN version which I have under extendNmr package. So, I saved the project with this unpatched version and re-opened it with the stand alone updated version. Now it gives me this message and the project has been opened:
>
> Error loading file for: <memops.Implementation.MemopsRoot id:607153104>
> Reading: <open file '/home/vitaliy/sk45m/CCPN/Sk45m/memops/Implementation/Sk45m.xml', mode 'r' at 0x2340deb8>
> Last xml tag read: IMPL.MemopsRoot.currentHaddockProject
> Parser state was: reading
> Current object was: <memops.Implementation.MemopsRoot id:607153104>
>
> First loading attempt failed - compatibility problem?.
> Re-trying, skipping cached TopObjects:
>>>>
>
> I am not sure if the project is still OK or something may have been damaged and it is not visible immediately.
> I wonder if you could please look into this and give any advices.
>
> Thank you,
> Vitaliy
>
