[SOLVED] chromium ver 75.0.3770.142 failing to start on Slack 14.2
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
chromium ver 75.0.3770.142 failing to start on Slack 14.2
I had been away for a period of time, and ran slackpkg update, install-new, upgrade-all.
I use slackpkgplus, chromium got updated to chromium-75.0.3770.142-x86_64-1alien.txz. Pepperflash was also updated to chromium-pepperflash-plugin-32.0.0.223-x86_64-1alien.
When I start chromium from a command prompt, I get this message:
Quote:
Gkr-Message: secret service operation failed: Failed to execute program org.freedesktop.secrets: No such file or directory
I at a loss to find a fix. I have tried an older version on chromium, version : chromium-74.0.3729.169-x86_64-1alien.txz; however that fails with a different message.
This version works fine on current.
Is anyone else experiencing this type of failure? What am I missing?
gnome-keyring is installed. I had it disabled, I had re-named /usr/bin/gnome-keyring-daemon to /usr/bin/gnome-keyring-daemon.bak. I found the keyring to be a pita. Up until this last update to chromium, that worked like a charm. Now it appears I have to either live with the keyring being a pita, or disable it, and not use chromium.
Is there a way to have the keyring disabled, and use chromium?
If you use my chromium package, then open /etc/chromium/00-default.conf in an editor and add the line:
Code:
CHROMIUM_FLAGS="--password-store=basic"
That will instruct Chromium to forget about Gnome-keyring or Kwallet and instead use its own built-in password manager which stores the passwords you save un-encrypted in ~/.config/chromium/Default/Login\ Data
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.