[SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

alexkemp · 2026-07-05 22:22:58

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/chromium

After 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.keystore

Attempting 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.keystore

I got some useful info + background from a Microsoft forum (sorry about that):

Chrome 150 Patch for CVE-2026-13933: Passwords Policy Fix After Renderer Compromise

I assume that I will have to wait for yet another Chromium update.

Ron · 2026-07-06 00:35:24

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.)

greenjeans · 2026-07-06 02:47:40

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 (2026-07-06 02:50:34)

Ron · 2026-07-06 08:17:55

greenjeans wrote:

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?

fsmithred · 2026-07-06 12:24:46

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 trap

If 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*.deb

It'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.

rbit · 2026-07-06 12:50:31

chromium 150 appears to be working okay on a new installation (that is, I did not previously have 149).
does 'chromium --temp-profile' work?

greenjeans · 2026-07-06 15:00:58

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.

Ron · 2026-07-07 21:58:19

Here we are 2 days beyond a major breakage and still no fix. I don't think it's unreasonable to have expected a fix by now. Floorp is looking really good right now.

fsmithred · 2026-07-07 22:26:00

Read the last post in the bug thread I linked. The fix has been merged. Package soon.

Ron · 2026-07-07 23:16:12

fsmithred wrote:

Read the last post in the bug thread I linked. The fix has been merged. Package soon.

Yeah, I should have wrote "still no release" instead of "still no fix." Still seems way too long for the fix to arrive. I don't see how such a major breakage like this slipped through the cracks to begin with. But crap happens, I guess.

stargate-sg1-cheyenne-mtn · 2026-07-08 16:32:46

pulled this snippet out of OP OP OT(original-poster_original-post_original-topic)referenced url:
https://windowsforum.com/threads/chrome-150-patch-for-cve-2026-13933-passwords-policy-fix-after-renderer-compromise.433930/

The Bigger Chrome 150 Story Is Attack Surface Sprawl
Chrome 150’s 433 security fixes are striking not only because of the count, but because of their spread. The release notes cover graphics layers, device APIs, extensions, remote access, browser UI, rendering libraries, and platform-specific components. A browser is now closer to a miniature operating system than a document viewer.
That sprawl changes how defenders should think. There is no single “browser vulnerability” category anymore. There are GPU bugs, WebUSB bugs, extension bugs, password bugs, AI-surface bugs, media bugs, and policy bugs, each with different exploitability and enterprise impact.
CVE-2026-13933 sits in the policy category, and policy bugs are easy to underappreciate. Memory corruption sounds dramatic. Policy enforcement sounds bureaucratic. But many of the most consequential security failures are cases where code does exactly what it was written to do — just for an actor that should never have been allowed to ask.
That is why the phrase policy enforcement deserves attention. It is the security model made executable. When it fails, the browser’s internal contract between trusted and untrusted components begins to fray.

regardless of which OS and/or _browser_ one is using, the whole commentary is worth reading when the time is available for such.

greenjeans · 2026-07-08 18:53:33

Already fixed in Brave last night.

Ron · 2026-07-08 19:01:25

Update to Chromium finally arrived.

alexkemp · 2026-07-08 21:17:50

Ron wrote:

Update to Chromium finally arrived.

Indeed it has, and it works. This post is written under Chromium (hurrah!):

About Chromium
Version 150.0.7871.100 (Official Build) built on Debian GNU/Linux 13 (trixie) (64-bit)

$ ~/.local/sbin/update
Hit:1 http://deb.devuan.org/merged excalibur InRelease
Get:2 http://deb.devuan.org/merged excalibur-updates InRelease [37.6 kB]
Get:3 http://deb.devuan.org/merged excalibur-security InRelease [37.9 kB]
Get:4 http://deb.devuan.org/merged excalibur-security/main amd64 Packages [228 kB]
Fetched 304 kB in 1s (261 kB/s)   
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
Summary:                        
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 4
Upgrading:                      
  chromium  chromium-common  chromium-l10n  chromium-sandbox

Summary:
  Upgrading: 4, Installing: 0, Removing: 0, Not Upgrading: 0
  Download size: 123 MB
  Space needed: 0 B / 57.3 GB available

Continue? [Y/n] Y
Get:1 http://deb.devuan.org/merged excalibur-security/main amd64 chromium-l10n all 150.0.7871.100-1~deb13u1 [8,891 kB]
Get:2 http://deb.devuan.org/merged excalibur-security/main amd64 chromium amd64 150.0.7871.100-1~deb13u1 [87.2 MB]
Get:3 http://deb.devuan.org/merged excalibur-security/main amd64 chromium-common amd64 150.0.7871.100-1~deb13u1 [26.6 MB]
Get:4 http://deb.devuan.org/merged excalibur-security/main amd64 chromium-sandbox amd64 150.0.7871.100-1~deb13u1 [131 kB]
Fetched 123 MB in 11s (10.9 MB/s)                                              
Reading changelogs... Done
(Reading database ... 265613 files and directories currently installed.)
Preparing to unpack .../chromium-l10n_150.0.7871.100-1~deb13u1_all.deb ...
Unpacking chromium-l10n (150.0.7871.100-1~deb13u1) over (150.0.7871.46-1~deb13u1
) ...
Preparing to unpack .../chromium_150.0.7871.100-1~deb13u1_amd64.deb ...
Unpacking chromium (150.0.7871.100-1~deb13u1) over (150.0.7871.46-1~deb13u1) ...
Preparing to unpack .../chromium-common_150.0.7871.100-1~deb13u1_amd64.deb ...
Unpacking chromium-common (150.0.7871.100-1~deb13u1) over (150.0.7871.46-1~deb13
u1) ...
Preparing to unpack .../chromium-sandbox_150.0.7871.100-1~deb13u1_amd64.deb ...
Unpacking chromium-sandbox (150.0.7871.100-1~deb13u1) over (150.0.7871.46-1~deb1
3u1) ...
Setting up chromium-sandbox (150.0.7871.100-1~deb13u1) ...
Setting up chromium-common (150.0.7871.100-1~deb13u1) ...
Setting up chromium (150.0.7871.100-1~deb13u1) ...
Setting up chromium-l10n (150.0.7871.100-1~deb13u1) ...
Processing triggers for desktop-file-utils (0.28-1) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for mailcap (3.74) ...
$ la /usr/bin/chromium
-rwxr-xr-x 1 root root 5064 Jul  7 18:47 /usr/bin/chromium

The officially official Devuan Forum!

#1 2026-07-05 22:22:58

[SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#2 2026-07-06 00:35:24

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#3 2026-07-06 02:47:40

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#4 2026-07-06 08:17:55

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#5 2026-07-06 12:24:46

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#6 2026-07-06 12:50:31

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#7 2026-07-06 15:00:58

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#8 2026-07-07 21:58:19

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#9 2026-07-07 22:26:00

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#10 2026-07-07 23:16:12

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#11 2026-07-08 16:32:46

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#12 2026-07-08 18:53:33

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#13 2026-07-08 19:01:25

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

#14 2026-07-08 21:17:50

Re: [SOLVED] Chromium 150.0.7871.46 Will Not Load After Password Update

Board footer