[5.0 Beta] Library won't load

This discussion was created from comments split from: Zotero 5.0 Beta.
  • edited January 12, 2017
    Hello. I updated to the latest beta version just now from the previous beta version. Now when I first start Zotero, the library doesn't load and both the left and middle column are just blank. I have to close the window (instead of to quit Zotero completely) and open it again to make it behave normally. I tried to use a new profile by renaming the original folders. It will work for two times of starting and quitting and then trigger the same problem.

    This is on macOS 10.12.2. I already used the builtin error report to send the information and the ID is 1778427185. Before the update there were no problem.

    I also tried the new Firefox connector. It doesn't seem to work. It shows the Z icon for every webpage and when I click it I always get the popup message introducing the connector and new standalone version. Nothing gets saved to Zotero. In the add-on preference page, it shows that Zotero is available.

    Thanks for the work!
  • edited January 12, 2017
    @jiaqi_hu: Can you confirm that the first problem still happens when Better BibTeX ZotFile is disabled? (I'm also a little confused — what window are you closing to make it behave normally? When you close the Zotero window, it quits, no?) If it still happens, are you able to generate a Debug ID for Zotero startup using the "Enable after restart" option?

    For the second problem, can you provide a Report ID from Firefox (if there are errors logged after closing the popup)? As soon as you click the "Got it" button, the popup should go away and the icon in the toolbar should change to the normal save icon.
  • edited January 12, 2017
    @dstillman I don't have Better BibTeX. When this happens, Command+W only closes that blank window but doesn't quit zotero. When I can click on the icon on the dock to open it again it will be good and in this case Command+W will also quit zotero. I've submitted the new debug output D502646200 after checking the "enable after restart" option and restarting zotero.

    For the firefox connector problem, I started a new firefox profile, installed the connector, enabled the Logging at startup, restarted Firefox, opened an APS page, clicked the Z icon and "got it" for two times, and submitted the report. It didn't return an ID though. I'll paste the output here.

    (3)(+0000000): Setting debug.store to false
    (3)(+0000007): HTTP POST {} to http://127.0.0.1:23119/connector/getTranslators
    (3)(+0000043): Setting firstSaveToServer to true
    (3)(+0000001): Connector: Method getTranslators succeeded
    (3)(+0000029): Translators: Saved updated translator list (362935 characters)
    (3)(+0000009): Setting connector.repo.lastCheck.localTime to 1484209759898
    (3)(+0000000): Repo: Check succeeded
    (3)(+0000000): Repo: Next check in 86402000
    (3)(+0000621): Connector_Browser: URL changed for tab
    (3)(+0000119): HTTP POST null to http://127.0.0.1:23119/connector/getClientHostnames
    (3)(+0000035): Connector: Method getClientHostnames succeeded
    (3)(+0000078): Connector_Browser: URL changed for tab
    (3)(+0001329): Translators: Looking for translators for http://start.firefoxchina.cn/
    (3)(+0000019): HTTP POST {"translatorID":"e7e01cac-1e37-4da6-b078-a0e8343b0e98"} to http://127.0.0.1:23119/connector/getTranslatorCode
    (3)(+0000681): Connector: Method getTranslatorCode succeeded
    (3)(+0000001): HTTP POST {"translatorID":"05d07af9-105a-4572-99f6-a8e231c0daef"} to http://127.0.0.1:23119/connector/getTranslatorCode
    (3)(+0000025): Connector: Method getTranslatorCode succeeded
    (3)(+0000001): HTTP POST {"translatorID":"951c027d-74ac-47d4-a107-9c3069ab7b48"} to http://127.0.0.1:23119/connector/getTranslatorCode
    (3)(+0000004): Connector: Method getTranslatorCode succeeded
    (3)(+0000001): HTTP POST {"translatorID":"c159dcfe-8a53-4301-a499-30f6549c340d"} to http://127.0.0.1:23119/connector/getTranslatorCode
    (3)(+0000005): Connector: Method getTranslatorCode succeeded
    (3)(+0000001): 2 translators found. Injecting into [rootUrl, url]: http://start.firefoxchina.cn/ , http://start.firefoxchina.cn/
    (3)(+0000195): Message `Translators.getWebTranslatorsForLocation` has no callback arg. It should use the returned promise
    (3)(+0000003): Translators: Looking for translators for http://start.firefoxchina.cn/
    (4)(+0000025): Translate: Binding sandbox to http://start.firefoxchina.cn/
    (4)(+0000013): Translate: Parsing code for unAPI (e7e01cac-1e37-4da6-b078-a0e8343b0e98, 2015-06-04 03:25:27)
    (4)(+0000004): Translate: Parsing code for COinS (05d07af9-105a-4572-99f6-a8e231c0daef, 2015-06-04 03:25:10)
    (4)(+0000003): Translate: Parsing code for Embedded Metadata (951c027d-74ac-47d4-a107-9c3069ab7b48, 2016-11-07 14:35:00)
    (3)(+0000006): Translate: Embedded Metadata: found 1 meta tags.
    (4)(+0000002): Translate: Parsing code for DOI (c159dcfe-8a53-4301-a499-30f6549c340d, 2016-11-06 18:45:00)
    (3)(+0000003): Translate: All translator detect calls and RPC calls complete:
    (3)(+0000002): No suitable translators found
    (5)(+0000003): Translate: Running handler 0 for translators
    (5)(+0000002): Translate: Running handler 1 for translators
    (3)(+0002177): Connector_Browser: URL changed for tab
    (3)(+0000006): Connector_Browser: URL changed for tab
    (3)(+0001301): Connector_Browser: URL changed for tab
    (3)(+0000026): Connector_Browser: URL changed for tab
    (3)(+0002654): Connector_Browser: URL changed for tab
    (3)(+0000100): Connector_Browser: URL changed for tab
    (3)(+0002189): Translators: Looking for translators for http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.95.190403
    (3)(+0000020): HTTP POST {"translatorID":"2c310a37-a4dd-48d2-82c9-bd29c53c1c76"} to http://127.0.0.1:23119/connector/getTranslatorCode
    (3)(+0003622): Connector: Method getTranslatorCode succeeded
    (3)(+0000002): 2 translators found. Injecting into [rootUrl, url]: http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.95.190403 , http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.95.190403
    (3)(+0000145): Message `Translators.getWebTranslatorsForLocation` has no callback arg. It should use the returned promise
    (3)(+0000000): Translators: Looking for translators for http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.95.190403
    (4)(+0000013): Translate: Binding sandbox to http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.95.190403
    (4)(+0000009): Translate: Parsing code for APS (2c310a37-a4dd-48d2-82c9-bd29c53c1c76, 2016-09-03 11:53:29)
    (4)(+0000003): Translate: Parsing code for unAPI (e7e01cac-1e37-4da6-b078-a0e8343b0e98, 2015-06-04 03:25:27)
    (4)(+0000002): Translate: Parsing code for COinS (05d07af9-105a-4572-99f6-a8e231c0daef, 2015-06-04 03:25:10)
    (4)(+0000004): Translate: Parsing code for Embedded Metadata (951c027d-74ac-47d4-a107-9c3069ab7b48, 2016-11-07 14:35:00)
    (3)(+0000004): Translate: Embedded Metadata: found 44 meta tags.
    (3)(+0000005): Translate: Creating translate instance of type import in sandbox
    (3)(+0000002): Message `Translators.get` has no callback arg. It should use the returned promise
    (3)(+0000002): HTTP POST {"translatorID":"5e3ad958-ac79-463d-812b-a86a9235c28f"} to http://127.0.0.1:23119/connector/getTranslatorCode
    (3)(+0000008): Connector: Method getTranslatorCode succeeded
    (4)(+0000010): Translate: Binding sandbox to http://journals.aps.org/prl/abstract/10.1103/PhysRevLett.95.190403
    (4)(+0000001): Translate: Parsing code for RDF (5e3ad958-ac79-463d-812b-a86a9235c28f, 2016-06-22 21:09:00)
    (3)(+0000003): Translate: Initializing RDF data store
    (4)(+0000006): Translate: Parsing code for DOI (c159dcfe-8a53-4301-a499-30f6549c340d, 2016-11-06 18:45:00)
    (3)(+0000002): Translate: All translator detect calls and RPC calls complete:
    (3)(+0000003): COinS: 310
    (3)(+0000002): Embedded Metadata: 320
    (3)(+0000002): DOI: 400
    (5)(+0000006): Translate: Running handler 0 for translators
    (5)(+0000008): Translate: Running handler 1 for translators
    (3)(+0000430): Message `Connector_Browser.injectScripts` has no callback arg. It should use the returned promise
    (3)(+0007299): Connector_Browser: URL changed for tab
    (3)(+0000297): HTTP POST {} to http://127.0.0.1:23119/connector/ping
    (3)(+0000006): Message `Prefs.getAsync` has no callback arg. It should use the returned promise
    (3)(+0000003): Message `Prefs.getAsync` has no callback arg. It should use the returned promise
    (3)(+0000006): Message `Prefs.getAsync` has no callback arg. It should use the returned promise
    (3)(+0000004): Message `Prefs.getAsync` has no callback arg. It should use the returned promise
    (3)(+0000017): Connector: Method ping succeeded
  • edited January 12, 2017
    @dstillman For the immediate restart after disabling ZotFile, the problem doesn't occur. Quit and start, it's back. It shows the same pattern when I enable ZotFile again.

    Sorry I forgot to mention, for the connector issue, I have Firefox 52.0a2 developer version.
  • edited January 12, 2017
    Sorry, I meant ZotFile, as you figured out, but doesn't sound like that's related. Still good to leave that disabled while we're debugging this.

    Could you take a screenshot of Zotero with the blank window, upload it somewhere (Dropbox, imgur.com), and post a link here?
    Sorry I forgot to mention, for the connector issue, I have Firefox 52.0a2 developer version.
    We haven't tested with Firefox 52.0a, so that may very well be broken. We'll take a look. It should work in 50.1.0.
  • debug report without any add-on: D1652395747
    screenshot: http://imgur.com/a/c1wrG
  • edited January 12, 2017
    Can you, with Zotero closed, try moving moving prefs.js from your Zotero profile directory to your desktop and see if that makes a difference? If that doesn't work, you can move the file back to restore your Zotero settings, and if it does we can figure out what preference is causing this.
  • Move prefs.js out: good for the first run and the second run, then fails again. Same as starting with a new profile.
    Move prefs.js back: good for the first run, then fails again.

    Could it be that something happens automatically for the first run or second and changed some preference that would cause this problem?
  • Would you mind emailing a "bad" prefs.js to support@zotero.org with a link to this thread?
  • Already did. I also noticed that zotero installs a Microsoft Word plugin as it starts for the first time without a prefs.js or in a clean profile. I tried to disable both the Word integration and Libreoffice integration under Tools menu - Add-ons. This seems to workaround the problem. Now zotero can start and show the library successfully every time. I hope this helps.
  • OK, this should be fixed in the latest build, 109. It actually wasn't related to the word processor plugins — it just happened on the second restart after a change to the running code or profile, so you would get two runs that seemed to be working. Thanks for your help tracking this down.
  • Thanks! I can confirm that it is now fixed here after updating to the latest version.
Sign In or Register to comment.