Skip to content

v0.9.6-beta.2 — Linux beta (x64)

Pre-release
Pre-release

Choose a tag to compare

@TeeJS TeeJS released this 11 Sep 01:50
· 38 commits to linux-dev since this release

Bedrock Panel v0.9.6-beta.2 — Linux beta (x64)

Bedrock Panel now runs on Linux with the DK-QUAKE: Software mode, Panel mode on the 1920×480
display, the knob and touchscreen, the tile grids, the editor, dashboards, and every
platform-neutral app. This is a beta for testers. Everything below is verified on Ubuntu 26.04
with KDE Plasma 6.6 on Wayland, PipeWire, and a real DK-QUAKE.

What changed since beta.1

The starter grid. beta.1's Linux pages were a mechanical translation of the Windows ones, so they
inherited tiles naming software no stock Linux desktop ships — Firefox, VS Code, a paint program,
OBS, Discord. Five tiles did nothing when tapped, on the one page a fresh install opens on.

Every shipped tile now names a category resolved against PATH, so it finds whatever your desktop
actually has: Images, Documents, Software, Video, Music, Disks and Info replace the ones that could
not resolve, alongside the Browser, Files, Editor, Calc, Tasks, Terminal, Settings and Screenshot
tiles that already worked.

This is the first-run seed, so upgrading from beta.1 will not change a config you already have.
To pull the pages in: editor → + Add page → Starter pages…. Nothing else differs from beta.1.

Download: bedrock-panel_amd64.deb for Debian and Ubuntu, or bedrock-panel-x86_64.AppImage
for anything else. Windows and macOS builds are unchanged in this beta (v0.9.5 remains current).

There is no native/linux helper tree and no compiler requirement. On Linux the equivalents of the
Windows C# and macOS Swift helpers are reachable from JavaScript, so the features that depend on
them are either already covered or listed below as not yet built.

First launch

The whole walkthrough is in docs/linux.md. In short:

  1. sudo apt install ./bedrock-panel_amd64.deb. Device access is set up for you — the package
    installs the udev rule the console needs, because apt already runs as root. Plug the QUAKE in
    and it is detected.
  2. Running the AppImage or from source instead? There is no installer, so the rule is one
    command: the editor's Settings → Hardware → Device access shows whether it is active and
    prints the exact command for your install, with a Copy button.
  3. Set the panel display to landscape so the desktop sees 1920×480 rather than 480×1920. On KDE
    that is kscreen-doctor output.DP-1.rotation.right, or Display Configuration in System Settings.
    Either orientation is detected, but only landscape lines the pointer up with what you see.
  4. Nothing else. There are no permission prompts to grant on Linux.

Packages are unsigned. Linux has no equivalent gatekeeper, so nothing asks you to allow the app.

What to try

  • Panel mode on the Quake — the panel covers the 1920×480 display. In a Wayland session the app
    restarts itself once at launch to run through XWayland, and logs one line saying so: a native
    Wayland client is not allowed to place a window on a chosen screen, and Panel mode is nothing but
    placement. BEDROCK_LINUX_OZONE=wayland skips the restart, at the cost of Panel mode.
  • Starter pages — a fresh install starts with Linux pages. Because Linux has no single
    calculator, file manager, or terminal, those tiles name the job and the app launches whichever
    program your machine has, checking a candidate list against PATH. A tile naming a real binary
    (dolphin, firefox, obs) is used exactly as typed. An existing config: editor →
    + Add page → Starter pages….
  • A config copied from Windows or a Mac — program names are mapped to their Linux equivalents
    and start <url> becomes xdg-open, so the pages you already built keep working.
  • Secrets — saved passwords and tokens go to KWallet or GNOME Keyring. With no keyring reachable
    the app refuses to save rather than store tokens under Chromium's hardcoded fallback key, which
    would only look encrypted. Existing secrets still decrypt either way.
  • Device Diagnostics — names Linux, and says when a device open was refused for want of the
    udev rule rather than blaming a cable.

Known limits in this beta

  • A GPU process crash was seen during development on Intel graphics with Mesa 26: the GPU
    process segfaulted at startup, Chromium restarted it, and after three attempts fell back to
    software rendering — the app ran normally throughout. It stopped reproducing before this build and
    has not recurred in roughly sixty launches across both display backends, so it is not listed as a
    known defect, only as something to report. The OEM DK-Suite build showed the same crash on the
    same machine, which points at the graphics stack rather than at Bedrock Panel. If you see
    bedrock-panel core dumps in coredumpctl list, please say so in an issue with your Mesa version
    (glxinfo -B | grep Mesa) — that is the missing piece.
  • Reserved Display and follow the focused app are not available. Both need to enumerate and
    move other applications' windows, which Wayland does not allow.
  • Teams window control cannot work for the tiles that focus the Teams window first. Zoom is
    unaffected, because its shortcuts need no focus.
  • Macros, media keys, and global hotkeys are not wired up yet. That is the next milestone.
  • Now playing, system volume, and call detection are not wired up yet either, so the Music page
    is blank, the meeting console's output rail shows a dash, and auto-record does not start on its
    own. Manual recording works.
  • Outlook desktop meeting info is Windows-only; use the Microsoft 365 source, which works
    everywhere.
  • Built-in speech is Windows and macOS only. Point the voice apps at a Wyoming server such as
    faster-whisper or piper; the app already speaks that protocol.
  • The touchscreen wizard does not exist and is not needed: it fixes a Windows-only problem.
  • AppImage needs FUSE 2, which Ubuntu 24.04 and newer no longer ship. Install libfuse2t64 or
    use the .deb.
  • x64 only. No arm64 build yet.

Reporting

Please include ~/.config/bedrock-panel/logs/main.log (every launch appends to it), your
distribution, desktop, and session type (echo $XDG_SESSION_TYPE) with any report.
Issues: https://github.com/TeeJS/bedrock-panel/issues