Unfortunately, no one can be told what Redcore Linux is. You have to see it for yourself!
You are not logged in.
I spent many frustrating hours trying to install a Linux desktop application built with Chromium/CEF. Distributed as a .deb package.
Succeeded running the package natively, not in a vm/distrobox.
Here is a guide for those would like to install similar packages. I hope this helps !
Cheers Myst!
RUNNING DEBIAN (.deb) DESKTOP APPS ON REDCORE LINUX (GENERIC GUIDE)
This applies to:
• Proprietary Linux apps distributed as .deb
• Electron / Chromium / CEF-based apps
• Trading platforms, chat apps, media apps, etc.
Examples:
• moomoo
• Discord (older builds)
• Slack (legacy)
• Many vendor-only Linux clients
These are NOT Android apps.
They do NOT require Waydroid.
------------------------------------------------
1) WHAT THIS TYPE OF APP IS
------------------------------------------------
• Native Linux binary
• Built for Ubuntu/Debian
• Often bundles outdated libraries (libstdc++, NSS, etc.)
• Often disables Chromium’s internal sandbox
• Expects Debian filesystem layouts (/usr/lib64, etc.)
------------------------------------------------
2) WHY THEY BREAK ON GENTOO / REDCORE
------------------------------------------------
Common issues:
• Hardened kernel features (IBT / SHSTK)
• Bundled, incompatible libstdc++
• Missing /usr/lib64 symlinks
• NSS / GLIBCXX version mismatches
• GPU / EGL incompatibilities
• Locale / region mis-detection via CEF cache
------------------------------------------------
3) THE CORRECT REDCORE STRATEGY
------------------------------------------------
DO:
✓ Extract/install app into /opt/<appname>
✓ Use system libraries instead of bundled ones
✓ Disable GPU acceleration
✓ Force locale explicitly
✓ Use Firejail as the primary sandbox
✓ Run via a wrapper script
DO NOT:
✗ Use Waydroid
✗ Assume Android compatibility
✗ Run binaries directly
✗ Trust bundled libstdc++
✗ Expect Chromium sandbox to work
------------------------------------------------
4) SECURITY MODEL (IMPORTANT)
------------------------------------------------
• Chromium internal sandbox is often disabled → NORMAL
• Firejail becomes the PRIMARY security boundary
• Hardened kernel still applies
• No container required unless you want full isolation
------------------------------------------------
5) WHEN TO USE DISTROBOX INSTEAD
------------------------------------------------
Optional, not mandatory.
Use Distrobox ONLY if:
• You don’t want to touch host libraries
• The app breaks after system upgrades
• You want a frozen Ubuntu runtime
• You run many Debian-only apps
If the app runs natively with Firejail:
→ Distrobox is NOT required.
------------------------------------------------
6) ANDROID APPS ARE DIFFERENT
------------------------------------------------
Android apps:
• Use APK / AAB
• Require Waydroid or Anbox
• Run inside an Android container
• Use Binder, not glibc
Linux .deb apps:
• Use glibc
• Run directly on host
• No Android runtime involved
These are completely different stacks.
Offline