I can't find Zotero Connector in Chrome
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
This discussion has been closed.
i'd send a screen shot if i could add it in here.
The debug looks exactly right, so I'm kind of at a loss. Did you disable other Chrome extensions or do you not have any?
just tried doing the whole debug thing with the new user.
anything now.
The Debug ID is D1710065479.
this one is the new user i created with no extension added (except docs which it came with.)
http://imgur.com/02FRtcQ
this is the first one i've been dealing with.
http://imgur.com/bnBybHO
here it is... http://imgur.com/9LY0ZiP
i just tried it from Jstor and got the following message 3 consecutive times:
"An error occurred while saving this item. Check Known Translator Issues for more information."
Edit: What's the JSTOR URL?
I read this thread in its entirety and didn't find any indication of a solution to this problem.
My setup:
Linux version 3.11.0-11-generic #17-Ubuntu
KDE SC version 4.11.2
Chromium version 29.0.1547.65 Ubuntu 13.10 (29.0.1547.65-0ubuntu2)
Zotero Standalone version 4.0.11
Zotero Connector version 4.0.8.2
Save as snapshot appears in context menu, but does not do anything when clicked on a webpage, with this message:
(3)(+0041741): HTTP POST {} to http://127.0.0.1:23119/connector/ping
(3)(+0000005): Connector: Method ping failed with status 0
_generated_backgroun_page.html shows this error repeated ad nauseam:
Port: Could not establish connection. Receiving end does not exist. lastError:29
set lastError:29
dispatchOnDisconnect miscellaneous_bindings:259
I would happily fill a bug report (or add info to an existing one), but I didn't find where.
Needless to say, Zotero is useless to me in this state. Any help would be appreciated. Thanks.
I am NOT running zotero or chromium as root.
The Firefox connector DOES work, though.
I'll gladly test whatever you need me to, I really use this feature a lot.
Beyond that Simon will have to look at that.
Linux kubuntu 3.2.0-52-generic-pae #78-Ubuntu
KDE SC 4.8.5
Chromium version 28.0.1500.71 Ubuntu 12.04 (28.0.1500.71-0ubuntu1.12.04.1)
Zotero Standalone version 4.0.11
Zotero Connector version 4.0.8.2
How would I go about figuring out if apparmor is the culprit? do you have a reference to other past apparmor issues, so I can file a bug against the correct Kubuntu package?
Thanks for your help.
https://forums.zotero.org/discussion/9375/
so this is just a guess based on the fact that the Chromium extension doesn't appear to be able to communicate with Zotero
could also be something else, a KDE change or so.
Zotero Standalone communicates with the connectors on port 23119 and best I can tell something is blocking that communication.
Two more things that'd be helpful:
1. what do you get when you paste http://127.0.0.1:23119/connector/ping
into Chromium's URL bar?
2. A debug ID from Chromium that covers loading the amazon wealth of nations page http://www.zotero.org/support/debug_output#zotero_connectors_chrome_and_safari
I'm using a custom library dir here, and firefox works. Also, There is no apparmor profile for chrom(e|ium) (but I don't know if that means anything). In any case, I disabled apparmor just to check, and the problem persists.
1. what do you get when you paste http://127.0.0.1:23119/connector/ping into Chromium's URL bar?
"Endpoint does not support method"
2. Debug ID D1313541543.
Let me know if you think of anything else. Thanks!
btw, is there a proper bug tracker for zotero? should i file a proper bug report, and if so, where?
thanks again for your help.
There is an issue tracker on github, but that's for dev use only.
As a workaround I installed Google Chrome, which works fine. Google Chrome is the non-open-source counterpart to Chromium, which you can download via Google (but not through the Ubuntu repositories).
This is not a fix in any way, of course, but at least it's a useful workaround for people affected by this problem.
The bug was fixed in the latest Ubuntu Chromium update, and the connector now works perfectly.