[email protected] wrote:

>Send Bibdesk-users mailing list submissions to
>       [email protected]
>
>To subscribe or unsubscribe via the World Wide Web, visit
>       https://lists.sourceforge.net/lists/listinfo/bibdesk-users
>or, via email, send a message with subject or body 'help' to
>       [email protected]
>
>You can reach the person managing the list at
>       [email protected]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Bibdesk-users digest..."
>
>Today's Topics:
>
>   1. Re: spinning wheel of death (Adam R. Maxwell)
>   2. Re: spinning wheel of death (Matthias Brennwald)
>   3. Re: spinning wheel of death (Fischlin  Andreas)
>   4. Re: spinning wheel of death (Niels Waller)
>   5. Re: spinning wheel of death (Adam R. Maxwell)
>   6. Re: spinning wheel of death (Niels Waller)
>
>
>On May 2, 2010, at 7:14 PM, Niels Waller wrote:
>
>> Its been a frustrating weekend. Last Friday my computer crashed and was only 
>> brought back to life by the magic of Diskwarrior.  I had an invalid B-tree 
>> something or other.  Luckily, everything was resuscitated EXCEPT my most 
>> important file -- my bibdesk file.  I have 1000 pdf's that I can no longer 
>> access through Bibdesk.  Every time I start Bibdesk I see my refs in the 
>> program (just to taunt me) and then the spinning wheel of death appears (and 
>> never goes away).  Any and all help would be GREATLY appreciated.
>
>Sorry to hear that!  If you can take a sample while it's beachballing (and 
>check the console for output), that might be a clue to what's going on.  Use 
>Activity Monitor and the "Sample Process" button to do this (or the sample 
>command in Terminal, if you prefer), and post the results here.
>
>
>
>
>
>On May 3, 2010, at 4:29 AM, [email protected] wrote:
>
>> Its been a frustrating weekend. Last Friday my computer crashed and was only 
>> brought back to life by the magic of Diskwarrior.  I had an invalid B-tree 
>> something or other.  Luckily, everything was resuscitated EXCEPT my most 
>> important file -- my bibdesk file.  I have 1000 pdf's that I can no longer 
>> access through Bibdesk.  Every time I start Bibdesk I see my refs in the 
>> program (just to taunt me) and then the spinning wheel of death appears (and 
>> never goes away).  Any and all help would be GREATLY appreciated.
>> 
>> Niels
>
>I'd try to open the file using a text editor. If this works, I'd check for 
>obvious errors in the bibtex entries (and fix them accordingly). If there's 
>nothing obvious, I'd split the file into several parts and open these with 
>BibDesk to see where the error is.
>
>Also (this is boring but important, because the next crash WILL happen 
>sometime): backup your files. Regularly. Really.
>
>Good luck
>Matthias
>
>
>I can only repeat what others said before, backup (next time). 
>
>If you go the split file route, don't forget to do it binary search.
>
>Regards,
>Andreas
> 
>
>ETH Zurich
>Prof. Dr. Andreas Fischlin
>Systems Ecology - Institute of Integrative Biology
>CHN E 21.1
>Universitaetstrasse 16
>8092 Zurich
>SWITZERLAND
>
>[email protected]
>www.sysecol.ethz.ch
>
>+41 44 633-6090 phone
>+41 44 633-1136 fax
>+41 79 221-4657 mobile
>
>             Make it as simple as possible, but distrust it!
>________________________________________________________________________
>
>
>
>On 03/May/2010, at 08:27 , Matthias Brennwald wrote:
>
>> On May 3, 2010, at 4:29 AM, [email protected] 
>> wrote:
>> 
>>> Its been a frustrating weekend. Last Friday my computer crashed and was 
>>> only brought back to life by the magic of Diskwarrior.  I had an invalid 
>>> B-tree something or other.  Luckily, everything was resuscitated EXCEPT my 
>>> most important file -- my bibdesk file.  I have 1000 pdf's that I can no 
>>> longer access through Bibdesk.  Every time I start Bibdesk I see my refs in 
>>> the program (just to taunt me) and then the spinning wheel of death appears 
>>> (and never goes away).  Any and all help would be GREATLY appreciated.
>>> 
>>> Niels
>> 
>> I'd try to open the file using a text editor. If this works, I'd check for 
>> obvious errors in the bibtex entries (and fix them accordingly). If there's 
>> nothing obvious, I'd split the file into several parts and open these with 
>> BibDesk to see where the error is.
>> 
>> Also (this is boring but important, because the next crash WILL happen 
>> sometime): backup your files. Regularly. Really.
>> 
>> Good luck
>> Matthias
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Bibdesk-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/bibdesk-users
>
>
>
>
>
>To all the good folks who are coming to my aid. 
>
>I forgot to mention an important detail in my original post.  I have at least 
>30 backups of my BibDesk file (I use time machine) and another half dozen on 
>an office backup hard drive  (the word "backup" is a mantra in my lab).  I get 
>the spinning beach ball even when I open up a fresh EMPTY BibDesk file.  I 
>have tried installing a new copy of BibDesk several times, but the problem 
>remains.  Hopefully this new info will help.  Thanks
>
>Niels
>
>
>On May 3, 2010, at 1:27 AM, Matthias Brennwald wrote:
>
>> On May 3, 2010, at 4:29 AM, [email protected] 
>> wrote:
>> 
>>> Its been a frustrating weekend. Last Friday my computer crashed and was 
>>> only brought back to life by the magic of Diskwarrior.  I had an invalid 
>>> B-tree something or other.  Luckily, everything was resuscitated EXCEPT my 
>>> most important file -- my bibdesk file.  I have 1000 pdf's that I can no 
>>> longer access through Bibdesk.  Every time I start Bibdesk I see my refs in 
>>> the program (just to taunt me) and then the spinning wheel of death appears 
>>> (and never goes away).  Any and all help would be GREATLY appreciated.
>>> 
>>> Niels
>> 
>> I'd try to open the file using a text editor. If this works, I'd check for 
>> obvious errors in the bibtex entries (and fix them accordingly). If there's 
>> nothing obvious, I'd split the file into several parts and open these with 
>> BibDesk to see where the error is.
>> 
>> Also (this is boring but important, because the next crash WILL happen 
>> sometime): backup your files. Regularly. Really.
>> 
>> Good luck
>> Matthias
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Bibdesk-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/bibdesk-users
>
>Niels Waller, Professor
>Director of Quantitative/Psychometric Methods
>Department of Psychology
>N218 Elliott Hall
>University of Minnesota
>75 East River Road
>Minneapolis Minnesota 55455
> 
>Phone: (612) 626-8729
>Email: [email protected]
>Homepage: http://www.psych.umn.edu/faculty/waller/
> 
>
>
>
>
>
>On May 3, 2010, at 6:26 AM, Niels Waller wrote:
>
>> I forgot to mention an important detail in my original post.  I have at 
>> least 30 backups of my BibDesk file (I use time machine) and another half 
>> dozen on an office backup hard drive  (the word "backup" is a mantra in my 
>> lab).  I get the spinning beach ball even when I open up a fresh EMPTY 
>> BibDesk file.  
>
>This is actually good news, since it may mean that your database isn't trashed.
>
>> I have tried installing a new copy of BibDesk several times, but the problem 
>> remains.  Hopefully this new info will help.  Thanks
>
>Please post the sample that I asked for last night, and any relevant console 
>output.  That is the only way to debug this problem remotely.
>
>
>
>
>
>
>
>Herre is a listing from activity monitor.  Thanks for working with me to solve 
>this.
>
>Niels
>
>
>On May 3, 2010, at 8:54 AM, Adam R. Maxwell wrote:
>
>> 
>> On May 3, 2010, at 6:26 AM, Niels Waller wrote:
>> 
>>> I forgot to mention an important detail in my original post.  I have at 
>>> least 30 backups of my BibDesk file (I use time machine) and another half 
>>> dozen on an office backup hard drive  (the word "backup" is a mantra in my 
>>> lab).  I get the spinning beach ball even when I open up a fresh EMPTY 
>>> BibDesk file.  
>> 
>> This is actually good news, since it may mean that your database isn't 
>> trashed.
>> 
>>> I have tried installing a new copy of BibDesk several times, but the 
>>> problem remains.  Hopefully this new info will help.  Thanks
>> 
>> Please post the sample that I asked for last night, and any relevant console 
>> output.  That is the only way to debug this problem remotely.
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Bibdesk-users mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/bibdesk-users
>
>Niels Waller, Professor
>Director of Quantitative/Psychometric Methods
>Department of Psychology
>N218 Elliott Hall
>University of Minnesota
>75 East River Road
>Minneapolis Minnesota 55455
> 
>Phone: (612) 626-8729
>Email: [email protected]
>Homepage: http://www.psych.umn.edu/faculty/waller/
> 
>
>
>------------------------------------------------------------------------------
>
>_______________________________________________
>Bibdesk-users mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/bibdesk-users
------------------------------------------------------------------------------
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users

Reply via email to