Potential Chrome/ChomeOS Bug

[cdc109]

Steps To Reproduce

When I restart my Chromebook to apply a Chrome OS update and log back into my Bitwarden vault, the vault will not autofill user id or passwords on any website I have a registered account with corresponding credentials in Bitwarden.

If I use my extension manager to toggle the Bitwarden browser extension off, and then back on it behaves correctly.

Chome OS Version 128.0.6613.133 (Official Build) (64-bit)
Chromebook Asus C425T

Expected Result

After rebooting my chromebook, I expect that when I log into Bitwarden it will then fill user ids and passwords on websites where I have corresponding userid and password stored in Bitwarden.

Actual Result

The Bitwarden browser extension seems slower than usual and will not prompt me to auto fill credentials on login pages.

Screenshots or Videos

No response

Additional Context

No response

Operating System

Linux

Operating System Version

Chome OS Version 128.0.6613.133 (Official Build) (64-bit)

Web Browser

Chrome

Browser Version

Version: 128.0.6613.133

Build Version

Version: 2024.9.0

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[JABirchall]

Duplicate of #10814 #10815

[cagonzalezcs]

@cdc109 Thank you for this bug report. This appears to be a duplicate of the problem described in #10814 , please see this comment for details surrounding the problem.

As this is a duplicate, I'm closing this thread for now to focus discussion within the Github issue mentioned above. Please feel free to continue discussion there.

[cdc109]

Understood. Thank you for letting me know. Chris Sent with [Proton Mail](https://proton.me/mail/home) secure email.

…

On Wednesday, September 18th, 2024 at 4:32 PM, Cesar Gonzalez ***@***.***> wrote: ***@***.***(https://github.com/cdc109) Thank you for this bug report. This appears to be a duplicate of the problem described in [#10814](#10814) , [please see this comment for details surrounding the problem](#10814 (comment)). As this is a duplicate, I'm closing this thread for now to focus discussion within the Github issue mentioned above. Please feel free to continue discussion there. — Reply to this email directly, [view it on GitHub](#11080 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/BLKUUQO54YIQFDLZNQ3WCNTZXHPM5AVCNFSM6AAAAABOJN22D2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJZGM2TCNJVHE). You are receiving this because you were mentioned.Message ID: ***@***.***>