Zotero won't start-Report ID 1676879777

thofer
the error just noticed today. last used ~7days ago.

Tried restarting firefox several times.
  • dstillman
    We'll have to fix this, but disable auto-sync in the Sync pane of the Zotero prefs, restart Firefox, and try again. Once you sync (possibly with an error message) you can likely re-enable auto-sync.
  • thofer
    no luck yet
    auto-sync off, restarted
    middle (citation) window blank except for "An error has occurred. Please restart Firefox - You can report..."
    restarted several times
    sync arrow green - "last sync 3 seconds ago"
  • dstillman
    Another Report ID?
  • thofer
    Well this one is from home (previous @work)
    Report ID: 1070231370

    appears to be similar error types (something about RFC 5746 ) but slightly different symptom- it keeps presenting 13 citation conflicts and errors out after they are reconciled. may or may not be related.

    will supply another work error when there.
  • dstillman
    The RFC error is irrelevant to Zotero.

    http://www.zotero.org/support/kb/repeated_conflicts

    This likely isn't related to the above, but try a Full Sync from the Sync->Reset pane of the Zotero prefs on your home computer.
  • thofer
    ok @ work again:
    autosync is off
    at start up middle window still shows "An error has occurred..."
    report id: 464206533
  • dstillman
    edited August 24, 2010
    There's no Zotero error in there. Can you provide a Debug ID from Firefox start-up through opening the page, using the "Enable after restart" option?
  • thofer
    hmm-144 lines. it does a lot of stuff.
    at least the error does seem to be there (in the debug log that is).

    The Debug ID is D1948691038.
  • dstillman
    Just to be sure this isn't something we've already fixed, can you check if this still happens with the latest 2.0 Branch XPI? (Unlike the trunk API, the branch XPI should be safe to use, but you should make a backup of your Zotero data directory first anyway.)
  • dstillman
    Also, try disabling all your other Firefox extensions.
  • thofer
    Ok,
    loaded the Branch XPI -- same error
    disabled all addons (only 4 or 5) except zotero & zotero winword integration->same error
    ran debug log after doing the above
    The Debug ID is D1239681675.

    parenthetically I have been getting a javascript error at startup of firefox for several months. But if I say stop script it seems to have worked ok up to the filing of this report. I mention it for completeness.
    "A script on this page may be busy, or it may have stopped responding. You can stop the script now, or you can continue to see if the script will complete.
    Script: chrome://zotero/content/xpcom/translate.js:255"
  • dstillman
    edited August 25, 2010
    You should never click Stop Script. Are you clicking Stop Script? If so, that's why you're getting an error.

    http://www.zotero.org/support/kb/unresponsive_script_warning
  • thofer
    restarted ff between each step obviously.
  • thofer
    yes,
    it just keeps giving the script error if I don't and I can't do anything.
  • dstillman
    No, it won't. Read the linked page, and don't click Stop Script.
  • thofer
    happy to(read the linked page) but I think the link is missing.

    btw I just tried again and if I click "continue" ff freezes and then presents the error again - over and over. The only way I have found to have the browser work at all is to click "stop script"

    also I will note again that I have been doing this ("stop script") for months and while a bit annoying, everything else worked up until recently.
  • dstillman
    Missing? Scroll up?
  • thofer
    also I get the same javascript error mentioned above both at home on a Mac and at work on a PC.
  • thofer
    oh, sorry.
  • thofer
    OK I'll try the about:config approach but at this point I am in this category:

    "If you receive the message repeatedly, report it in the Zotero Forums, and be sure to include the file and line number from the message in your post. "
  • dstillman
    edited August 25, 2010
    You're not, really, because you have yet to actually let it complete. We're familiar with that warning on that line, and it occurs primarily on slow Windows computers, particularly after restarts. Once the operation that's causing it completes without interruption, there's a good chance you won't see it again, at least until the next Zotero update.
  • dstillman
    And, actually, in your case, it may be exacerbated by this being a network drive? (Just guessing based on this being drive letter O:.)
  • thofer
    You are correct on all counts.

    I set the delay to 120 and apart from a delay of 1.3 minutes it then all worked. Why I got by for a while w.o. worse symptoms I don't know but it doesn't really matter.

    yes it is a network drive (although not at home where I was having the same problem)

    I'm glad I mentioned it.
    Thanks for your patience.
  • dstillman
    Great. How about on another Firefox restart? Is there still a delay? And how about after a computer restart?
  • thofer
    it is definitely faster getting into zotero after restart (both ff and pc)

    while the startup is still slow overall, it is back to the point where it may all be related to the overhead of running off a network drive which I am willing to accept given other advantages.
    thanks again

This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.