Yes Det, those seem to be the issues I was having but not anymore since I downgraded from testing.
I am able to use google-chrome-stable and login no problem. However, something strange has happened. Even though pacman thinks google-chrome-unstable is not installed, it nevertheless runs fine as long as I don't try to log in. Even the .desktop file still exists and works.
What are all the files I would have to manually remove in order to fully uninstall google-chrome-unstable.
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 .. 21 22 23 24 25 26 27 28 29 30 31 .. 91 Next › Last »
colinkeenan commented on 2014-04-04 04:26 (UTC)
Det commented on 2014-04-04 04:25 (UTC)
So, for reference:
- The fixing commit ([testing]/linux 3.14-3): https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=2c69d1905dc88e27181b36d523c9fa17a0d564c4
- LKML thread: http://www.gossamer-threads.com/lists/linux/kernel/1887224
- Another one: http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg617266.html
colinkeenan commented on 2014-04-04 03:42 (UTC)
I use Xfce and don't use gnome keyring, so no seahorse. However, basically everything I tried to re-install was having issues so with a lot of trouble (at one point boot was failing) I finally downgraded from testing.
I downgraded the kernel and everything else down so that nothing was from testing. I re-installed google-chrome-unstable and (unlike before) didn't get any errors during the install.
After all that though, google-chrome-unstable was still crashing with segfault. So, I did:
rm -r .config/google-chrome-unstable
rm -r .cache/google-chrome-unstable
It didn't crash until about half a minute after I logged in. So, I removed those folders again and tried logging in under a different account. Still crashed half a minute later. Now I'm using google-chrome-unstable no problem as long as I don't log in.
I will try installing google-chrome-stable and see if I can log in.
<deleted-account> commented on 2014-04-04 02:05 (UTC)
@colinkeenan I'm not sure about the segfault but that Gtk-message could be because of seahorse (if you are running gnome). Could you check if it's working or run chrome with "--password-store=basic"? Ignore this if you don't care.
About the kernel: Reinstall the old kernel, test Chrome and update again. If Chrome fails after that then maybe it is really in the kernel (The devs are trying to trim it down, they may have disabled something chrome needed)
colinkeenan commented on 2014-04-04 01:17 (UTC)
I downgraded to *6 from April 1, and am having the same issue.
It started after I tried a system upgrade that tried to upgrade testing/linux 3.14-2 2 -> 3
but failed due to the file not having the required signature.
Seems like my issue is not being caused by *14 though. I'll work on it and probably end up posting for help in the forums.
colinkeenan commented on 2014-04-04 00:57 (UTC)
Having trouble with *.14
colin ~$ google-chrome-unstable
[3229:3229:0403/193416:ERROR:component_loader.cc(138)] Failed to parse extension manifest.
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[3229:3229:0403/193416:ERROR:desktop_window_tree_host_x11.cc(1266)] Not implemented reached in void views::DesktopWindowTreeHostX11::MapWindow(ui::WindowShowState)
Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files
[72,2513151744:00:34:16.968253] Native Client module will be loaded at base address 0x0000367700000000
[3229:3345:0403/193416:ERROR:get_updates_processor.cc(214)] PostClientToServerMessage() failed during GetUpdates
Segmentation fault (core dumped)
<deleted-account> commented on 2014-04-03 17:35 (UTC)
Hmm, just tried to upgrade for x86_64 and failed to verify the md5sum (the file I received had a sum of 88cc0fa5a83acaef7f66a44bf6ae3b1d)
Update: Version bumped to *.14
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.