[Bug Report & Solution] Root Cause of Grayed-Out ADB Debugging on Debian 13 (Trixie): Broken Google Repository
Hello Chrome OS Engineering Team, After extensive troubleshooting regarding the "Enable ADB debugging" toggle remaining grayed out on managed devices, I have isolated the root cause. It is not an Admin Policy issue, nor a user error. The issue is a missing dependency in the Google Package Repository for Debian 13 (Trixie), which prevents the installation of cros-guest-tools. Without cros-guest-tools, the Chrome OS Host cannot verify the container's integrity or establish the necessary bridges, leading the OS to lock developer features (ADB) as a security fallback. Here is the technical breakdown and the required fix. 1. The Environment Host: Chrome OS (Version 131+) Guest: Debian 13 (Trixie) - Current Stable. Repository Config: /etc/apt/sources.list.d/cros.list deb https://storage.googleapis.com/cros-packages/142 trixie main 2. The Error When attempting to install or update the integration tools via sudo apt install cros-guest-tools, the package manager fails with a hard dependency error: The following packages have unmet dependencies: cros-guest-tools : Depends: cros-im which is a virtual package and is not provided by any available package Running sudo apt search cros-im confirms that this package does not exist in the trixie RELEASE of the repository. 3. The Diagnosis The cros-guest-tools meta-package depends on cros-im (Input Method integration). In Bookworm (Debian 12), this dependency is satisfied (likely by cros-im-default or similar). In Trixie (Debian 13), the cros-im package has not been published or linked in the repository index. 4. The Solution (Action Required from Google) The repository maintainers need to push the missing input method packages to the Trixie DIRECTORY immediately. Required Action: Please ensure cros-im-default (or the architecture-specific equivalent) is added to: https://storage.googleapis.com/cros-packages/142/dists/trixie/main/ Once this dependency is resolvable: cros-guest-tools will install correctly. The Host<->Guest handshake will complete. The "Enable ADB Debugging" toggle will unlock in the Chrome OS Settings. Please escalate this to the Cros Packaging team. Best regards, Christophe RouxStability vs. Features: The Unique Philosophy of Chrome OS
Hello, There is a distinct difference in how Google manages Android versus Chrome OS, and as a developer, I think it is important to recognize why the Chrome OS strategy is superior for productivity. The Android Approach: Android is a commercial product first. It focuses on features, consumer appeal, and running on everything. The priority is "It works now." The Chrome OS Approach: Chrome OS started small and humble. It has grown slowly, not by chasing trends, but by building a foundation of trust and robustness. I see this robustness daily in the Crostini environment. Recently, upgrading my VM from Debian 12 (Bookworm) to Debian 13 (Trixie) was a pleasure—a real upgrade requiring no reinstallation. This level of stability is rare in the OS world. It proves that Chrome OS is engineered with a long-term vision of quality. The Risk The current rumors about new operating systems or "Android on PC" threaten to undermine this stability. If Google tries to make Chrome OS behave too much like Android—rushing features at the cost of stability—we lose the "high quality" segment. My Request Chrome OS is currently the best bridge between desktop computing and Android mobile development. I urge Google to maintain this "slow and steady" strategy. We don't need a flashy OS; we need a trustable one. Keep building the high-quality, robust platform that Chrome OS has become.
Beyond the endpoint: The unified Google enterprise stack can simplify your fleet today
We're excited to see the ongoing evolution of your ChromeOS deployments. Our latest enterprise vision isn't just about faster devices or better software; it’s about delivering a truly unified and intelligent Google stack, fit for enterprise, that simplifies management and powers the modern workforce. The key message is clear: Google AI is fundamentally changing the way work gets done, and we’re ensuring that transformation is secure and seamlessly available across every touchpoint. A look at the unified platform Our new vision ties together our core enterprise products to eliminate complexity and deliver unparalleled value: The AI-powered workspace (ChromeOS, Chrome, & Gemini): Gemini is now embedded directly into the Chrome browser and operating system (especially on Chromebook Plus devices), offering employees intelligent assistance right where they work. Crucially, this is delivered and managed through your existing Google Workspace accounts, giving IT the necessary controls over how your data interacts with AI. The application bridge (Cameyo by Google): We understand that a unified OS requires total application compatibility. The general availability of Cameyo by Google closes the final gap. It allows you to deliver every application; legacy or modern, side-by-side, entirely within the Google ecosystem, eliminating the need for expensive, complex third-party VDI environments. The Security & Operations Hub (Chrome Enterprise Premium & SecOps): Comprehensive data protection is non-negotiable. That's why we've baked robust DLP directly into Chrome Enterprise Premium and provided a one-click integration with Google SecOps. This gives you unprecedented visibility and control over web activity and data movement across your entire fleet, including when employees leverage AI. We're dedicated to helping you realize a simpler, more secure, and AI-powered enterprise. Share your strategies, thoughts and questions below! For all the details on the new capabilities and our connected enterprise vision, please read the full announcement: Bringing connected and AI-powered work experiences across our platforms and devicesChrome OS Flex AUE in Google Admin
Hey. The admin console has a fantastic feature where you can see the AUE of your devices pr year. It makes it easier to plan budget for replacing devices going out of support and planning execution. https://admin.google.com/ac/chrome/devices/?sf=2&so=2&tab=dashboard However - you can only see Chrome OS devices since the "Automatic updates until" field in Google Admin is not populated as in the example below. Obviously this information is available somewhere to be displayed, but it is currently not. I would really like to avoid exporting inventory to a spreadsheet, use the certified model list (https://support.google.com/chromeosflex/answer/11513094?hl=en) to populate the empty field in the spreadsheet and keep track of it there. How do others plan inventory replacements? Has anyone else tried to reach out to the Chrome OS team pointing out this flaw?Project Lifeboat: Secure your business continuity with Google
In an evolving cyber landscape, being prepared for disruptions is essential. That's why we're hosting a critical session exclusively for our valued ChromeOS customers to introduce a powerful contingency solution: Project Lifeboat. This webinar will demonstrate how Google's integrated solution, which includes ChromeOS, Chrome Enterprise, Google Workspace, and Google Cloud, can help your organization maintain essential operations during and after a security incident. We'll show you how to ensure critical communication and access remain secure, even if your primary systems are compromised. Join us to learn how ChromeOS provides a robust and resilient foundation for your business continuity strategy. Once you register - we will share the calendar event with meeting link closer to the event.
