P.S. All this, and compiling the kernel makes sense for owners of old computers.
Chromium base browsers play YouTube videos at a resolution one notch higher than Firefox.
Therefore, the "fruit analogies" of Risen owners with 32 GB of memory are quite understandable.

aluma wrote:

iridium-2021.06.91-1pclos2021.x86_64.rpm

That's pretty old.

If you really want to use a browser for which Debian support is non-existent then at least use the latest version:

https://dl.iridiumbrowser.de/fedora_37/

But it's still a really bad idea. How do you keep it updated against the steady stream of CVEs?

Have you tried it on the stable branch?
When installing chromium base browsers on a system with a different version of glibc, you will only be able to run it with the "nosandbox" option.
I offer a working solution.

P.S. I can add.
The stable version of my EXEGnu by glibc corresponds to openSUSE_Leap_15.3.
Here is the latest version of iridium for her
https://downloads.iridiumbrowser.de/ope … .3/x86_64/
But I couldn’t get it to work, it still needs other libraries and some newer ones.

The browser is the single biggest potential vulnerability in a desktop system...

Have you probably had many such cases with browsers?
I have had one for 20 years, when the browser "hung" the computer, I had to press the "restart" button.

But seriously, it's better to place the browser cache in tmpfs, the same Firefox today with 13 errors.
https://bugzilla.mozilla.org/buglist.cg … id=6873202

aluma wrote:

iridium-2021.06.91-1pclos2021.x86_64.rpm

That's pretty old.

If you really want to use a browser for which Debian support is non-existent then at least use the latest version:

https://dl.iridiumbrowser.de/fedora_37/

But it's still a really bad idea. How do you keep it updated against the steady stream of CVEs?

This is a conscious choice.

1. The latest version has an "innovation" - a warning line about using Google search, which must be manually closed.
In the previous one, it was in the address bar and disappeared by itself.

2. After some time, when viewing YouTube, the mouse cursor starts to run by itself and the browser freezes.
By the way, Pclos has now completely removed Iridium from the repo.

iridium-2021.06.91-1pclos2021.x86_64.rpm

That's pretty old.

If you really want to use a browser for which Debian support is non-existent then at least use the latest version:

https://dl.iridiumbrowser.de/fedora_37/

But it's still a really bad idea. How do you keep it updated against the steady stream of CVEs?

The ultimate goal of any OS is to run a user program. This can be done in many ways, directly if the program is compiled for this OS or using "crutches", virtual machines. containers or the same Wine. This is the choice of the user, his preferences and capabilities.

A hobby is an irrational and expensive thing, and one should probably not advise everyone to follow their whims.
In fact, I think that the password request is unique to Gnome, I have never had such problems in Trinit.
(There is some gnome-something-xml file)

Moreover, the iridium-2021.06.91-1pclos2021.x86_64.rpm of the PclinuxOs build works great in the Devuan stable branch. I can post this package and the *.deb package converted by alien, it would be nice to have it in a place accessible to everyone.

To run this browser, you don’t need a super-duper computer with a bunch of OS and stray crutches at all.

Marjorie wrote:

can't recall having any keyring issues

Chromium tries to detect the desktop and it will only show that message if it thinks it's running in GNOME. If you're running Xfce I think it will fall back to basic for the --password-store option, which doesn't need the keyring.

FWIW I use Cinnamon (=gnome lite).

can't recall having any keyring issues

Chromium tries to detect the desktop and it will only show that message if it thinks it's running in GNOME. If you're running Xfce I think it will fall back to basic for the --password-store option, which doesn't need the keyring.

EDIT: and contrary to the OP's statement this problem was solved in their linked thread. I presume Altoid just has problems reading.

Hello:

I run Devuan Beowulf on a backported kernel [5.10]:

So ...
Just what #$%&'¿ does Chromium want with a keyring PW?

Any idea  as to what is going on?

Thanks in advance.

A.

I use Chimaera on a 5.15 kernel. Beowulf is a bit old now.

I've got ungoogled-chromium (also 108) installed as a backup for firefox-esr in case it can't render a website (though these days I never seem to need it) and can't recall having any keyring issues.

Is anyone else, who uses the devuan repository chromium on Beowulf, seeing this?

My question was:

Just what #$%&'¿ does Chromium want with a keyring PW?
Any idea  as to what is going on?

You did not answer it.

Yes I did. The answer to that is in the linked thread. But I did presume you were asking for help getting Chromium to start without nagging for a password when in fact all you wanted to do was whine. My mistake.

Hmm ...
Not really.

My question was:

You did not answer it.

Maybe, depends.
I was not looking for quicker.

I asked here on Dev1 because I use Devuan Linux, the issue affects Devuan+Chromium and probably affects quite a few Devuan users.
The solution/explanation (if found) will eventually be posted here and will be available to Devuan users searching for it here.

All that does not come with quicker.

Now, if my doing so results in your getting your knickers in a twist, annoys you or in any way upsets your fragile peace of mind, please do consider disregarding my question: you are under no obligation whatsoever to answer it.

Like I have said in another opportunity: I value your opinions, expertise and the help provided to me more than once.
That has not changed.

But it seems that you insist on acting up and in doing so do yourself a great disservice.
You are in no position to presume to be able to lecture me on learning anything, so please don't.

Best,

A.