You are not logged in.
I am using FireFox to write this post, and that is because if I attempt to load Chromium it briefly appears and then immediately shuts itself down, with zero notice.
$ neofetch
..,,;;;::;,.. alexk@ng3
`':ddd;:,. ---------
`'dPPd:,. OS: Devuan GNU/Linux 6 (excalibur) x86_64
`:b$$b`. Model: 90BJ008CUK Lenovo H30-05
'P$$$d` Kernel: 6.12.94+deb13-amd64
.$$$$$` Uptime: 5 hours, 42 mins
;$$$$$P Packages: 3340 (dpkg)
.:P$$$$$$` Shell: bash 5.2.37
.,:b$$$$$$$;' Resolution: 1920x1080
.,:dP$$$$$$$$b:' DE: Xfce 4.20
.,:;db$$$$$$$$$$Pd'` WM: Xfwm4
,db$$$$$$$$$$$$$$b:'` WM Theme: Default
:$$$$$$$$$$$$b:'` Theme: Clearlooks-Phenix-Sapphire [GTK2/3]
`$$$$$bd:''` Icons: oxygen [GTK2/3]
`'''` Terminal: xfce4-terminal
Terminal Font: Monospace 12
CPU: AMD A8-7410 APU with AMD Radeon R5 Graphics (4) @ 2.200GHz
GPU: AMD ATI Radeon R4/R5 Graphics
Memory: 1642MiB / 7362MiB$ which chromium
/usr/bin/chromium
$ /usr/bin/chromium --version
Chromium 150.0.7871.46 built on Debian GNU/Linux 13 (trixie)
$ la /usr/bin/chromium
-rwxr-xr-x 1 root root 5064 Jul 4 09:01 /usr/bin/chromiumAfter the recent Chromium update the first Chromium restart saw it ask me for a keyring password. I pressed 'Cancel' and it simply shutdown, no further action.
After much useless DDG searching I tried to follow some advice to remove the keyring at ~/.local/share/keyrings using rm -v ~/.local/share/keyrings/login.keyring.
The previous step on Chromium restart now saw a much fuller restart, with a Chromium 'New tab' and a "Restore pages" dialog + "Choose password for new keyring" dialog. The entire desktop was frozen with the sole exception of the Chromium dialogs.
Entering my system-user password, then confirming it + pressing the 'Continue' button then shutdown that entire window but released all other windows.
The keyring dir now looked like this (I do not recall the 'default' nor the 'Default_Keyring.keyring' entries being present before):
$ la ~/.local/share/keyrings
total 12
-rw-rw-r-- 1 alexk alexk 15 Jul 5 22:56 default
-rw------- 1 alexk alexk 428 Jul 5 22:56 Default_Keyring.keyring
-rw------- 1 alexk alexk 207 Sep 12 2016 user.keystoreAttempting to launch Chromium briefly shows a flash of Chromium in the panel but nothing else.
Curiously, my earlier efforts placed an extra entry into the keyrings, but not now:
$ la ~/.local/share/keyrings
total 16
-rw-rw-r-- 1 alexk alexk 15 Jul 5 14:54 default
-rw------- 1 alexk alexk 428 Jul 5 16:54 Default_Keyring.keyring
-rw------- 1 alexk alexk 328 Jul 5 16:54 login.keyring
-rw------- 1 alexk alexk 207 Sep 12 2016 user.keystoreI got some useful info + background from a Microsoft forum (sorry about that):
I assume that I will have to wait for yet another Chromium update.
Offline
I'm having problems as well with this version. I have 3 profiles in Chromium, and I can use profile 1, but profiles 2 and 3 just won't load. I can see the screen start to be drawn, but it disappears after a split-second. Not happy about this. (Trying out Floorp . . . seems okay.)
Offline
Don't know what's up, but on the surface my first instinct says this smacks of gnome-keyring issues. Stuff like that is why I un-installed several gnome packages.
My solution: Ditch gnome-keyring. Save passwords in a separate encrypted app. Zero reason to trust gnome with my security in the first place. Srsly, don't trust gnome.
Last edited by greenjeans (Today 02:50:34)
https://sourceforge.net/projects/vuu-do/ Vuu-do GNU/Linux, Devuan-based Openbox systems.
Devuan 6 mate-mini iso, pure Devuan, 100% no-vuu-do, mostly
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
https://devuanusers.com/
Offline
My solution: Ditch gnome-keyring.
In my case that's one of the first things I do after an OS install. So it must be something more than just gnome-keyring?
Offline
Thanks for the warning. I downloaded the 149.x version before doing the upgrade. Chromium-150 appears for a fraction of a second and disappears. No keyrings here. I get a message when I try to start it from command line:
$ chromium
[0706/080813.360978:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64] tag not found
Trace/breakpoint trapIf anyone knows what that means, I'd be interested to hear about it.
Meanwhile...
### Download these (or from your favorite debian mirror)
http://ftp.us.debian.org/debian/pool/main/c/chromium/chromium_149.0.7827.196-1~deb13u1_amd64.deb
http://ftp.us.debian.org/debian/pool/main/c/chromium/chromium-common_149.0.7827.196-1~deb13u1_amd64.deb
http://ftp.us.debian.org/debian/pool/main/c/chromium/chromium-sandbox_149.0.7827.196-1~deb13u1_amd64.deb
### And force-install them
dpkg --force-downgrade -i chromium*.debIt's been reported (multiple times) and there's a suggested patch.
https://bugs.debian.org/cgi-bin/bugrepo … ug=1141488
I expect there will be a new version very soon.
Offline
chromium 150 appears to be working okay on a new installation (that is, I did not previously have 149).
does 'chromium --temp-profile' work?
Offline
Since my last post i've seen other mentions of similar issues on other forums. The same bug fsmithred linked to. Chromium usually updates anyway about once a week so it should be fixed pretty quick.
https://sourceforge.net/projects/vuu-do/ Vuu-do GNU/Linux, Devuan-based Openbox systems.
Devuan 6 mate-mini iso, pure Devuan, 100% no-vuu-do, mostly
Please donate to support Devuan and init freedom! https://devuan.org/os/donate
https://devuanusers.com/
Offline