Hi!
I’m using chrome-dev with Gnome 3, and it can’t remember that I clicked on the button to set it as the default browser.
Do you know how to fix it? Thanks!
Search Criteria
Package Details: google-chrome-dev 133.0.6847.2-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/google-chrome-dev.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome-dev |
Description: | The popular web browser by Google (Dev Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Provides: | google-chrome |
Submitter: | None |
Maintainer: | gromit |
Last Packager: | gromit |
Votes: | 654 |
Popularity: | 1.47 |
First Submitted: | 2009-06-05 21:02 (UTC) |
Last Updated: | 2024-11-21 19:42 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet5 (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (40)
- bitwarden-chromium (requires google-chrome) (optional)
- captive-browser-git (requires google-chrome) (optional)
- chrome-extension-bitwarden-git (requires google-chrome) (optional)
- chrome-extension-ocrs-git (requires google-chrome)
- chromedriver (requires google-chrome) (optional)
- chromium-extension-adnauseam (requires google-chrome) (optional)
- chromium-extension-autoscroll (requires google-chrome) (optional)
- chromium-extension-plasma-integration (requires google-chrome) (optional)
- chromium-extension-runet-censorship-bypass (requires google-chrome) (optional)
- chromium-material-icons-for-github-bin (requires google-chrome) (optional)
- chromium-vencord (requires google-chrome) (optional)
- chromium-vencord-bin (requires google-chrome) (optional)
- chromium-vencord-git (requires google-chrome) (optional)
- dedao-dl-bin (requires google-chrome) (optional)
- endpoint-verification-chrome (requires google-chrome)
- endpoint-verification-minimal (requires google-chrome)
- ff2mpv-go-git (requires google-chrome) (optional)
- ff2mpv-rust (requires google-chrome) (optional)
- hub-kids (requires google-chrome) (optional)
- hub-young (requires google-chrome) (optional)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 91 Next › Last »
Raymondcal commented on 2014-05-12 20:31 (UTC)
Det commented on 2014-05-11 17:55 (UTC)
It's an NPAPI plugin. Aura Chrome for Linux v35+ only supports Pepper: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
SZoPer commented on 2014-05-11 16:54 (UTC)
Anyone else having problem with Java Plugin? (java version "1.8.0_05")
I've already tried creating symlinks to /opt/java/jre/lib/amd64/libnpjp2.so in both /opt/google/chrome/plugins and /opt/google/chrome, but to no avail. I've got this issue for months.
augenleet commented on 2014-05-07 17:55 (UTC)
Alright, thanks. :)
Det commented on 2014-05-07 17:09 (UTC)
Means a new one up.
augenleet commented on 2014-05-07 16:59 (UTC)
Getting this error:
==> Validating source files with md5sums...
google-chrome-unstable_36.0.1964.2_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build google-chrome-dev.
colinkeenan commented on 2014-04-25 18:28 (UTC)
OK - Got google-talkplugin to work by re-installing it.
<deleted-account> commented on 2014-04-25 18:27 (UTC)
Well, I have these two files listed as Google Talk:
/opt/google/chrome-unstable/pepper/libppgoogletalk.so
/opt/google/chrome-unstable/pepper/libppo1d.so
They are just symlinks:
wxrwxrwx 1 root root 52 Mar 28 09:28 libppgoogletalk.so -> ../../../../opt/google/talkplugin/libppgoogletalk.so
lrwxrwxrwx 1 root root 45 Mar 28 09:28 libppo1d.so -> ../../../../opt/google/talkplugin/libppo1d.so
And both files are from the google-talkplugin package:
/opt/google/talkplugin/libppgoogletalk.so pertence a google-talkplugin 5.2.4.0-3
/opt/google/talkplugin/libppo1d.so pertence a google-talkplugin 5.2.4.0-3
Also, the pepper folder they are in seems to also be part of google-talkplugin:
/opt/google/chrome-unstable/pepper pertence a google-talkplugin 5.2.4.0-3
I'm also having a problem where Chrome doesn't seem to get the information that it is the default browser and clicking to change it doesn't work.
colinkeenan commented on 2014-04-25 18:04 (UTC)
Google Talk doesn't show up in chrome://plugins. I have the AUR package installed. CharlesAtum, do you have Google Talk installed and does it show up in chrome://plugins?
Also, the "unstable" branding is missing when setting google-chrome-unstable as the default web browser from the google chrome settings page. The previous version did that correctly, but for this one to work I had to cp google-chrome-unstable.desktop google-chrome.desktop in ~/.local/share/xfce4/helpers/.
Also, in case anyone using Xfce doesn't know, you can get Xfce Preferred Applications to recognize google chrome as default by editing the desktop file in ~/.local/share/xfce4/helpers/ and copying the stuff Xfce added to the end of the file, beginning with TargetEnvironment=Unity and put it at the end of the [Desktop Entry] section.
<deleted-account> commented on 2014-04-25 16:10 (UTC)
This one is still Aura, they just don't say it because there's no more need to differentiate anymore. Also, not sure why Google Talk doesn't work for you: AFAIK, the AUR package also installs PPAPI versions.
Pinned Comments
gromit commented on 2023-07-19 17:01 (UTC) (edited on 2023-07-19 17:02 (UTC) by gromit)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Dev updates" tag in Release blog for this.
You can also run this command to obtain the version string for the latest chrome version:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.