Package Details: chrome-gnome-shell-git 10.1.r65.ge609ff2-1

Git Clone URL: https://aur.archlinux.org/chrome-gnome-shell-git.git (read-only, click to copy)
Package Base: chrome-gnome-shell-git
Description: Native browser connector for integration with extensions.gnome.org
Upstream URL: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome
Keywords: Chrome Chromium Firefox Opera Vivaldi
Licenses: GPL
Conflicts: chrome-gnome-shell, gs-chrome-connector
Provides: chrome-gnome-shell
Replaces: gs-chrome-connector
Submitter: winsock
Maintainer: rafaelff
Last Packager: rafaelff
Votes: 230
Popularity: 1.04
First Submitted: 2016-02-27 22:54 (UTC)
Last Updated: 2022-01-25 17:31 (UTC)

Pinned Comments

rafaelff commented on 2016-08-15 21:57 (UTC) (edited on 2022-07-04 01:03 (UTC) by rafaelff)

This package provides only the native host messaging connector that integrates with GNOME Shell and the corresponding extensions repository https://extensions.gnome.org

You also need to install the extension for your web browser. Find below URL for the extension/add-on for the supported browsers:

Opera is not supported. See Installation for more info.

Latest Comments

rafaelff commented on 2022-07-04 01:07 (UTC)

There was a change in the project name and the build system which is causing a build failure for this package. Consider using chrome-gnome-shell if you need this working ASAP. I filed a few issues in the upstream project and I'm working on the new PKGBUILD already.

rafaelff commented on 2022-01-10 18:49 (UTC)

@gaelic: This package does not directly depend on libffi7. Several of its dependencies depend on libffi (which provides libffi.so.8), but this could if you have one or more dependencies installed from unofficial repositories. pacman -Qi libffi7 should tell which package depends on it, so you can act if you want.

gaelic commented on 2021-11-09 09:14 (UTC)

to make this work i had to manually install libffi7.

SamLukeYes commented on 2021-05-08 09:21 (UTC)

chrome-gnome-shell was removed from the official repo just now, and became an orphaned package on AUR :(

rafaelff commented on 2018-04-10 11:48 (UTC)

'chrome-gnome-shell' is now part of the official repositories. Consider using it instead of this AUR package. ;-)

sandstorm commented on 2018-02-17 07:24 (UTC)

If you run into certificate problems, add env GIT_SSL_NO_VERIFY=true to the execution, e.g. env GIT_SSL_NO_VERIFY=true yaourt -S chrome-gnome-shell-git

The problem is due to a missing root certificate, be aware of the security implications and see https://stackoverflow.com/a/4454754/3303838 for more details.

rafaelff commented on 2017-11-15 14:48 (UTC) (edited on 2017-11-15 14:48 (UTC) by rafaelff)

@jatone: In your case, adding "-DPYTHON_EXECUTABLE=/usr/bin/python" to cmake should problem solve this. Can you please test it and let me know?

jatone commented on 2017-11-15 13:57 (UTC)

this application incorrectly sets the executable python to be used in the chrome-gnome-shell script installed to /usr/bin/chrome-gnome-shell, and on my system resulting in extensions.gnome.org claiming 'an unexpected error occurred' on my system its picking up my user's local miniconda python version and not the system version. cat /usr/bin/chrome-gnome-shell | head #!/home/user/miniconda3/bin/python by changing it to #!/usr/bin/python the package begins to work again.

rafaelff commented on 2017-10-25 15:52 (UTC)

@brittyazel: Were those missing packages not covered by the array of dependencies of this package? If possible please try to list the packages you had to install or what was the error message, so I can check any possible missing package in the dependency list.

brittyazel commented on 2017-10-25 15:43 (UTC)

@rafaeiff I figured it out. I had a couple missing python packages that were causing the error. Running chrome from the command line let me see the errors quickly. I wasn't aware that chrome-gnome-shell used python, thus why I didn't think to look there before.

rafaelff commented on 2017-10-10 12:37 (UTC)

@brittyazel: I don't know what could be the cause or how to debug. Can you please file a bug report in the upstream requesting for support? (https://bugzilla.gnome.org/enter_bug.cgi?product=chrome-gnome-shell)

brittyazel commented on 2017-10-09 16:36 (UTC)

@rafaelff I have yes. Unless there's something I'm missing, I'm at a loss

rafaelff commented on 2017-10-07 00:51 (UTC) (edited on 2017-10-07 00:52 (UTC) by rafaelff)

brittyazel: have you tried rebuilding this package after having GNOME 3.26 installed? Rebuilding worked just fine for me.

brittyazel commented on 2017-10-06 16:29 (UTC)

Updating to 3.26 today, this seems to be broken. extensions.gnome.org says "Native host has exited." whenever I go to the page.

rafaelff commented on 2017-05-13 12:51 (UTC)

@michaudg: some more information on this issue would be nice for trying to solve. Anyway, please remember to set dependencies (in PKGBUILD) to Python2 as well, or you could have some missing deps in there.

gu1ll0me commented on 2017-05-10 23:40 (UTC) (edited on 2017-05-10 23:42 (UTC) by gu1ll0me)

@ybon I had the "Unexpected error occurred" message too. I finally solved it by using Python 2 instead of Python 3. I modified the first line of /usr/bin/chrome-gnome-shell to #!/usr/bin/python2 and the Gnome Extensions page finally appeared. The project documentation says Python 2.7 or Python 3.x. I don't know why it only works with Python 2.7 for me.

rafaelff commented on 2017-05-10 10:00 (UTC)

@ybon: I see. Can you please try adding a '-DPYTHON_EXECUTABLE=/usr/bin/python' to cmake in the PKGBUILD and let me know if the newly built package doesn't present this issue? I'll apply if it works.

ybon commented on 2017-05-10 09:51 (UTC)

I had the "Unexpected error occurred" message when browsing the extensions.gnome.org website. After digging a bit, I've seen that /usr/bin/chrome-gnome-shell was referencing python from one of my venvs instead of system python, not sure why (maybe because I ran the install while the venv was active?). Anyway, I changed the python in the file (first line must look like #!/usr/bin/python), and now everything works. FYI.

rafaelff commented on 2017-04-26 19:32 (UTC)

@franziskus: Why do you say that? It is built against Python3, so I would expect it to depend on python-request.

franziskus commented on 2017-04-26 16:12 (UTC)

This package needs python2-requests as a dependency (not python-requests).

rafaelff commented on 2017-04-19 17:40 (UTC)

@easymodo: how did you manage to have a Windows-formatted /usr/bin/chrome-gnome-shell ?

easymodo commented on 2017-04-19 17:22 (UTC)

If you are getting "Native host exited" on gnome webpage, run this: dos2unix /usr/bin/chrome-gnome-shell

rafaelff commented on 2017-04-15 10:34 (UTC)

@PSCHC: You need the 'make' package. Please ensure the 'base-devel' package group is installed, because AUR packages will assume you that is true. See: https://wiki.archlinux.org/index.php/Arch_User_Repository#Getting_started

PSCHC commented on 2017-04-15 09:12 (UTC)

"CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool. -- Configuring incomplete, errors occurred!" Can someone help? ._.

rafaelff commented on 2017-03-19 16:19 (UTC)

@brittyazel: Please make sure you have GNOME Shell installed and running. It won't work if you running something else, like Metacity or Unity.

brittyazel commented on 2017-03-15 07:45 (UTC)

Weird, on one of my computers this works great, and extensions.gnome.org works perfectly, but on another I get a message saying "no_gnome_shell"

rafaelff commented on 2017-01-27 09:18 (UTC)

@ferrvittorio: cmake is still in community repository, so it is probably in your system. Please review your /etc/pacman.conf for custom configs.

ferrvittorio commented on 2017-01-27 08:05 (UTC)

Hi, seems as I cannot find cmake in repo, somebody has same problem?

rafaelff commented on 2016-12-27 06:38 (UTC)

PKGBUILD updated. Thanks. @Awesome_Donkey: please do not flag out-of-date a package when its version is not out-of-date, and do not use it to report issue. Maintainer already is always notified of new comments.

mdemierre commented on 2016-12-26 22:39 (UTC)

The build fails for me. The following changes fixed the problem: - Add 'jq' to dependencies - Add -DCMAKE_INSTALL_LIBDIR='/usr/lib' in build() Here is an updated PKGBUILD: https://gist.github.com/mdemierre/b2cddd2b262207fb5ab14778d01cce7d

rafaelff commented on 2016-09-27 00:20 (UTC)

@Mr_ResistOr: You can only use pacman to install local packages or from official repositories. Since chrome-gnome-shell-git is in AUR Unsupported, you will need to "Download Snapshot" and build locally with makepkg, or to use AUR helpers (yaourt, pacaur etc) to install packages directly from AUR. E.g., see: https://wiki.archlinux.org/index.php/Arch_User_Repository

Mr_Resist0r commented on 2016-09-26 16:59 (UTC)

I'm a total noob and have just stared using arch. For some reason when I try to install this I get "Target not found". I'm using "chrome-gnome-shell-git" with "sudo pacman -S" because that's how I installed all the other packages. Any help?

rafaelff commented on 2016-09-13 10:08 (UTC) (edited on 2016-09-16 10:05 (UTC) by rafaelff)

@aseemraj: This package package currently provides only the native connector, while the extension can be installed from Chrome Web Store. Have you tried to rebuild this package, in order to obtain the version 7 ? EDIT: Oh, you tried to rebuild, sorry. Please try also closing the web browser and starting it again, and let me know.

aseemraj commented on 2016-09-13 08:37 (UTC)

I have the chrome extension installed. When I try to install a gnome extension, I get this message on the top: "You are using different versions of GNOME Shell integration extension (version 7) and native host connector (version 6.2)" Any idea how can I update? yaourt -S chrome-gnome-shell-git doesn't seem to help and the extensions that I install don't appear in the tweak tool. Thanks!

rafaelff commented on 2016-08-15 21:57 (UTC) (edited on 2022-07-04 01:03 (UTC) by rafaelff)

This package provides only the native host messaging connector that integrates with GNOME Shell and the corresponding extensions repository https://extensions.gnome.org

You also need to install the extension for your web browser. Find below URL for the extension/add-on for the supported browsers:

Opera is not supported. See Installation for more info.

horosgrisa commented on 2016-08-15 21:40 (UTC)

You can add integration for opera?

rafaelff commented on 2016-08-09 07:29 (UTC) (edited on 2016-08-09 08:57 (UTC) by rafaelff)

No problem, winsock! Thanks for your support! Package adopted!

winsock commented on 2016-08-08 15:02 (UTC)

I want to apologize for the lack of updates, got caught up with work. I disowned the package if you want to take it over @rafaelff.

rafaelff commented on 2016-08-08 11:35 (UTC)

@caseyjp1: was your message a reply for me or the package maintainer? For the record, this is a VCS package, which means it will install the latest version available of the software in the repository. Therefore, users of this package will receive the latest native host connector when installing, even though the pkgver is set to 5.1_xxxxx

caseyjp1 commented on 2016-08-07 22:58 (UTC)

You are using different versions of GNOME Shell integration extension (version 6.2) and native host connector (version 6). Some features may not work or work wrong. The plugin from gnome is showing up to date. host connector is out of date. fyi.

rafaelff commented on 2016-07-07 13:54 (UTC) (edited on 2016-07-07 13:55 (UTC) by rafaelff)

Maxiride: There is no compatibility problem. You just have to install this package plus the Gnome Shell Integration extension in Chrome Web Store. More information on https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

Maxiride commented on 2016-07-07 13:25 (UTC)

Is there a way to install it into chromium instead?

rafaelff commented on 2016-06-11 08:04 (UTC) (edited on 2016-06-11 08:14 (UTC) by rafaelff)

Maintainer, your PKGBUILD has a pkgver() function that is incorrectly using $pkgver (variable) to define itself. This is causing the pkgver to be kept as 5.1. In order to get the real current version number, please replace the use of $pkgver as first parameter of pkgver()'s printf with something like 'git describe --long' or a string regexp in the PROJECT_VERSION from file 'CMakeLists.txt' For more information, see: -> https://www.archlinux.org/pacman/PKGBUILD.5.html#_options_and_directives -> https://wiki.archlinux.org/index.php/VCS_package_guidelines @sakel: In matter of fact, you are getting the latest code with the incorrect version number in the package, as explained in the above paragraph.

winsock commented on 2016-05-20 15:47 (UTC)

@sakel I just re-installed this package and it pulls the latest code just fine from the master branch(version 6 as of writing)

sakel commented on 2016-05-20 10:44 (UTC)

I think it pulls the latest version 5 (or 5.1) and j1simon's comment refer to the fact that the new current version is 6. This also raises a warning when visiting extensions.gnome and an error from the chrome plugin.

winsock commented on 2016-05-18 15:49 (UTC)

@j1simon Did you do a rebuild of this package? This always pulls and builds the latest commit in the master branch. AFAIK, This is how git AUR packages are expected to work.

j1simon commented on 2016-05-18 08:52 (UTC)

https://git.gnome.org/browse/chrome-gnome-shell/tag/?h=v6

winsock commented on 2016-03-16 04:42 (UTC) (edited on 2016-03-16 04:50 (UTC) by winsock)

I'm unflagging this as out of date for now, since this builds straight from the git repo this is actually building the latest version (currently 5.2) not 5.1. Since there was no file I could extract the current version number at the time I just hardcoded the version number. The only thing out of date is the package name, I'll update the version in the PKGBUILD and see about extracting the current version from the CMakeLists.txt to auto update the version on package build.

somepaulo commented on 2016-02-26 18:03 (UTC)

@winsock Thanks! Loop is gone now. All works fine.

winsock commented on 2016-02-26 05:50 (UTC)

@somepaulo Okay I see why it is doing this, however installing a different version is the expected behavior in cvs PKGBUILDs, the version number will always update to match the latest commit number and commit revision. I have updated the PKGBUILD to include the commit number in the version string to fix this issue.

somepaulo commented on 2016-02-26 05:10 (UTC)

@winsock I use quite a few -git packages, and none of them do this. gs-chrome-connector-git currently declares one version - 5.c2b35ef-1, but installs a different version number - 5.bc10252-1, which is obviously considered older and thus triggers an update, since AUR lists a newer version. Can you change your PKGBUILD to declare version 5.bc10252-1?

winsock commented on 2016-02-25 06:25 (UTC) (edited on 2016-02-25 06:25 (UTC) by winsock)

@somepaulo, AFAIK no CVS based AUR package will know when to actually update. It will always recompile if running a full system upgrade with a AUR tool. I could make a non -git package. However, I do not want to commit that far into the Arch community at this point in my life. I would have to then track of releases myself, and currently I do have the time that would be required to keep a non CVS package up to date. That was the long way of saying any package with -svn, -git, -cvs, -hg, etc. will do the same thing AFAIK.

somepaulo commented on 2016-02-24 22:51 (UTC)

Version 5.c2b35ef-1 pulls and installs version 5.bc10252-1, which creates an update loop. GIT repo lists v5.1 as latest.

yuryrodrigues commented on 2016-02-23 17:17 (UTC)

I'm using the browser Vivaldi (derived from Chromium) and Antergos distribution (derived from Arch), and the extension works perfectly! Thank you!

winsock commented on 2016-02-12 05:47 (UTC)

Note: This just installs the native connector for the chrome extension. You also need the chrome extension from the Chrome Web Store: https://goo.gl/JHCUS9