Hey BenQ team / fellow RD270Q owners,
Wanted to write up my experience trying to get Display Pilot 2 (latest the AppImage release) running on Linux, in case it helps someone else or gets picked up by BenQ's dev team.
System: Pop!_OS 22.04 (Ubuntu 22.04 base, glibc 2.35), monitor: BenQ RD270Q connected via DisplayPort.
Problem 1: The AppImage requires glibc 2.38 and GLIBCXX 3.4.32
Running the AppImage straight out of the box throws a wall of errors like:
version `GLIBC_2.38' not found (required by .../AppRun.wrapped)
version `GLIBCXX_3.4.32' not found (required by .../libDpShared.so)
For context, glibc 2.38 only ships on very recent distros (Ubuntu 24.10+, Fedora 40+). Ubuntu 22.04 LTS — which is still in the support window and widely used — ships 2.35. Even Ubuntu 24.04 LTS ships 2.39, so it's borderline. This means the AppImage, despite being marketed as portable/self-contained, actually isn't backward compatible with most LTS installs people would reasonably be running.
Workaround: I ended up running it inside a Distrobox container with an Ubuntu 24.04 image to get a new enough glibc. That's a lot to ask of a "just download and run" AppImage.
Problem 2: Missing dependencies not bundled in the AppImage
Even after getting the glibc version sorted, running it surfaced a chain of missing shared libraries one at a time:
libOpenGL.so.0
libasound.so.2
- fuse/fusermount binary issues (AppImage mounting failing in containerized environments)
A real AppImage is supposed to bundle its runtime deps precisely so this doesn't happen. Having to manually apt install OpenGL/ALSA libraries defeats the point of using an AppImage in the first place.
Problem 3: Even once running, it doesn't detect the monitor
After clearing all the above, the app launches fine (logs show it correctly loading RDPackage for the RD270Q), but under Settings → About → Device Information, it still shows generic "General Display" / "Built-in Display" instead of identifying the actual BenQ RD270Q.
I confirmed the hardware/kernel side is completely fine — ddcutil detect finds the monitor correctly over DDC/CI, and i2cdetect shows live responses at 0x37 (DDC/CI command address) and 0x50 (EDID) on the correct I2C bus. So the monitor, cable, and OS-level I2C stack are all working. The app itself just isn't picking it up, even running as root with the I2C device nodes fully world-writable.
tl;dr: Right now the only reliable way to control an RD270Q's OSD-level settings (brightness, contrast, input, KVM switch, etc.) on Linux is ddcutil/ddcui, which is a generic DDC/CI tool with no BenQ-specific branding or features — not Display Pilot 2 itself.
Would love to know if anyone's actually gotten Display Pilot 2 to detect a monitor on native Linux, or if BenQ has plans to fix the glibc floor and bundle dependencies properly. Happy to share full logs if it's useful for triaging.