I am using 3 containers. I have been aware that multi-container support is going away.

I have started receiving the following message upon starting up any linux container.

> NOTICE: multi-container support is going away

> Recently it has become necessary to deprecate some features of crostini,including:

> * UI-based installation of .deb packages. Installation via aptitude is the default path, but there are also visual package managers which may be used.

> * UI-based Debian release upgrade. Please refer to release notes for the release in question for upgrade instructions.

> * Multi-container support.

> info

> * For the most up-to-date news, please visit

> * https://developers.google.com/chromeos/app-development/develop/news

> (this message will be repeated 2 more times).

My preparations:

• I have moved my files and applications from my secondary containers into my penguin container

My questions

1. is there anything else I should be doing to prepare? (I have no ability to remove the abandoned containers through the settings, because container management was removed from settings)
2. will my penguin container remain intact?
3. when will this change occur?

I use the DuckDuckGo Search & Tracker Protection extension with the brave and chrome browser (don't judge, I use different browsers for different purposes)

If i VISIT https://browserleaks.com/chrome I see

> Detected 1 of 5000 Extensions

> ✔DuckDuckGo Search & Tracker Protection

This occurs whenever the extension is enabled, even if the extension has not been granted access to https://browserleaks.com/

I believe it means there are web-accessible resources within the extension that the website uses to detect the ddg extension.

Is it possible to redo the extension to remove web-accessible resources?

I'm thinking of dipping my toes into self hosting just out of curiosity, and maybe a learning experience (I would still keep local copies of encrypted vault exports for backup purposes, and take precautions to prevent circular lockout).

Bitwarden Lite I think used to be called Unified when it was in beta. It is no longer in beta, and described here:

• https://bitwarden.com/help/install-and-deploy-lite/

Let's talk about computing resources:

> * Bitwarden lite requires: > * RAM: At least 200 MB > * Storage: At least 1GB > * Docker Engine: Version 26+

That's not very demanding specs for a server. I have google cloud always-free compute engine (E2 I think) with 1GB ram and 250gb storage. I currently access it via tailscale for a few small projects. Thinking about getting an oracle always-free arm vps as well since it comes with an option for more ram.

Let's talk about complexity to install. I see one extra requirement for bitwarden lite:

> * "Because Bitwarden lite databases are not provided by or collocated with the application container, database maintenance, including updates, maintenance, and backups, must be fully managed by you."

... that doesn't seem too challenging to install sqlite3 and adjust environmental variables to point to it. Are there other challenges setting up bitwarden lite that don't apply to vaultwarden?

What are your thoughts about pros and cons of these two self-hosted options or any compelling reasons to prefer one solution over the other (vaultwarden vs bitwarden lite)?

Android 17 blocks non-accessibility apps from the AccessibilityService API | anonhaven.com

> Google added an accessibility API lockdown in Android 17 Beta 2. When Advanced Protection Mode (AAPM) is active, the system prevents any app not classified as an accessibility tool from receiving AccessibilityService access. ...

> ... Apps must declare isAccessibilityTool=true in their service metadata to pass the check. Screen readers, voice control systems, and switch-based input tools qualify. Automation apps, custom launchers, notification customizers, password managers, and antivirus software do not [qualify].

Bitwarden uses accessibility services to support the quick action tiles.

autofill from android app | Bitwarden.com

> Quick-action tiles use the Android accessibility service to make autofill actions available from your notifications pull-down's settings menu.

I'm not sure when this change might come into effect. The article mentions Android 17 Beta 2, so I think (?) it might come to standard android when we get Android 17 which is supposed to be in June or July.

It seems like this might affect certain users if they have android's advance device protection active and they use bitwarden quicktiles.

I tried to log into the chrome extension using my yubikey.

First attempt failed in some way (I'm not sure if I got an error message, but I assumed I had typed my pin wrong and tried again).

Second attempt succeeded, except I get this error message warning me about ADDITIONAL data loss (which means I already have data loss?!?)

It includes 12 sets of hex strings (each wrapping to 2 lines like the one shown).

I have no idea what particular data may have been lost in my vault. I don't see anything obvious. Neither do I know how I can associate these hex numbers with my entries (does anyone know that?).

Trying to decide whether the next action is going back to my last backup or not.

I will be contacting support, but also posting here for any suggestions.

I have Debian 12. After running sudo apt update, uname -r tells me that I have kernel 6.6.99 which apparently is not yet patched for copy-fail and therefore vulnerable to local privilege escalation under certain conditions.

I'm trying to figure out what would be the steps to rectify the situation. I see some discussion here:

Debian Linux Patched Copy Fail (CVE-2026-31431) Vulnerability - OSTechNix

It seems to require more technical knowledge than I have.

Can anyone provide suggestions to update the kernel or make the system safe until the update arrives?

Two things I noted:

1. Is there any way to eliminate trust in ancient X11 from this app?
2. Is it still requiring an outdated version of org.gnome.Platform? When I perform flatpak update, I get the error message:

• Info: (pinned) runtime org.gnome.Platform branch 48 is end-of-life, with reason: The GNOME 48 runtime is no longer supported as of March 24, 2026. Please ask your application developer to migrate to a supported platform.
  • I think this error originates from OnlyOffice but I'm not positive. The only other flatpak I have installed is flatseal

EDIT - The following item appears related to X11 on the flatpak

• flatpak: Can't run on Wayland · Issue #1453 · ONLYOFFICE/DesktopEditors