On Mon, Oct 10, 2011 at 2:58 AM, Tsjerk Wassenaar <tsje...@gmail.com> wrote:
> Hey Lina,
>
> It most likely is a consequence of the update. But the error comes
>
Hi Tsjerk,
Right now I downgrade the pymol from 1.4.1-1+b1 to 1.4.1-1. It works.
I was kinda of lazy sometimes, should have carefully checked earlier.
But, which problem cause the version 1.4.1-1+b1 not functional well I still
don't know. (http://packages.debian.org/wheezy/pymol)
Thanks,
lina
> from the settings code, so I assumed that you set some settings at
> startup, which brings a .pymolrc in mind. Not loading that file would
> then solve it, although the problem is probably more fundamental, and
> I would suspect you'd get an error like that when just setting some
> setting in Pymol. If you can give more information regarding the
> modules that were updated, it would be very helpful. Otherwise, I'm
> rather clueless...
>
> Cheers,
>
> Tsjerk
>
> On Sun, Oct 9, 2011 at 7:42 PM, lina <lina.lastn...@gmail.com> wrote:
> > On Oct 10, 2011, at 1:04, Tsjerk Wassenaar <tsje...@gmail.com> wrote:
> >
> > Hi Lina,
> >
> > Can you tell more? What version are you using, what system are you on, do
> > you use a .pymolrc, and what exactly do you do?
> >
> > Version 1.4.
> > Debian amd64
> > I did use .pymolrc.
> > Please kindly notice the problem just recent two days showed up.
> > The .pymolrc has been used for a while.
> > Today I reinstalled the pymol. Still the same.
> > Do you think it's related to the .pymolrc?
> > Right now I'm not in front of computer.
> > Later (now is 1:40 am here, probably 8 or 9 hours later) I can remove the
> > .pymolrc and test.
> > Actually I suspected It might due to the update of some package in my
> box.
> > But I have no clue about how to check further.
> > Thanks.
> >
> > Cheers,
> >
> > Tsjerk
> >
> > On Oct 9, 2011 5:05 PM, "lina" <lina.lastn...@gmail.com> wrote:
> >
> >
> >
> > On Sun, Oct 9, 2011 at 10:50 PM, lina <lina.lastn...@gmail.com> wrote: >
> >
> > Hi, > > I met the followi...
> >
> > Still something abnormal.
> >
> > When I tried to write session, it's terminated and showed:
> > Save: Please wait -- writing session file...
> > Segmentation fault
> >
> >>
> >> Thanks,
> >>
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > All of the data generated in your IT infrastructure is seriously
> valuable.
> > Why? It contains a definitive record of application performance, security
> > threats, fraudulent activity, and more. Splunk takes this data and makes
> > sense of it. IT sense. And common sense.
> > http://p.sf.net/sfu/splunk-d2dcopy2
> > _______________________________________________
> > PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net)
> > Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users
> > Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
> >
>
>
>
> --
> Tsjerk A. Wassenaar, Ph.D.
>
> post-doctoral researcher
> Molecular Dynamics Group
> * Groningen Institute for Biomolecular Research and Biotechnology
> * Zernike Institute for Advanced Materials
> University of Groningen
> The Netherlands
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net)
Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users
Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
