Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-5034GitHub issuePublicReceived

IPU7 camera HAL requires missing libjsoncpp.so.26 on current Arch

Reported by jamielmccormick · filed Sep 11, 2026Closed upstream on 2026-09-11 by its own reporter jamielmccormick, as not planned. Closed by its own reporter — not by itself evidence of a fix.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

IPU7 camera HAL requires missing libjsoncpp.so.26 on current Archrevision 1 · captured 2026-10-04 12:10 UTC via poll

Summary

The integrated webcam on a Dell XPS 14 (IPU7 / OV08X40) is not usable in Omarchy 4.0.3. The camera kernel modules and sensor bind successfully, but the bundled Intel camera HAL is linked against an older jsoncpp ABI than current Arch provides.

Reproduction

  1. Boot Omarchy 4.0.3 on a Dell XPS 14 with the OV08X40 camera.
  2. Start the camera stack:
   sudo systemctl restart camera-init.service [email protected]
  1. Run gst-inspect-1.0 icamerasrc.

Before installing the cached older jsoncpp package, the output included:

HalAdaptor: load_camera_hal_library, failed to open library:
/usr/lib/libcamhal/plugins/ipu75xa.so,
error: libjsoncpp.so.26: cannot open shared object file: No such file or directory

The resulting relay logs then show:

CameraParserInvoker: getAvailableSensors, Found IPU: IPU7
CameraParserInvoker: parseSensors: No sensors available
gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed

Applications such as Chromium/Google Meet remain stuck at “Camera is starting” and then fail.

Observed system state

  • Omarchy: 4.0.3-1
  • Kernel: 7.2.3-arch1-1-ptl
  • v4l2-relayd: 0.2.0-2.2
  • Current Arch jsoncpp: 1.9.8-1, providing libjsoncpp.so.27
  • Intel HAL: /usr/lib/libcamhal/plugins/ipu75xa.so
  • Loaded modules include intel_ipu7, intel_ipu7_isys, intel_ipu7_psys, ov08x40, and intel_cvs.
  • The sensor is bound at i2c-OVTI08F4:00.
  • /dev/media0 and /dev/video50 exist.

The media graph contains IPU7 CSI/ISYS nodes but no OV08X40 sensor entity when the HAL is attempted.

Temporary workaround

Installing the cached Arch package jsoncpp-1.9.6-3 restores libjsoncpp.so.26; then ldd /usr/lib/libcamhal/plugins/ipu75xa.so resolves successfully. This suggests the camera package/HAL is stale relative to the current Arch jsoncpp ABI.

Expected behavior

The Omarchy IPU7 camera installation should have a compatible HAL and jsoncpp dependency, and a normal omarchy update should not leave icamerasrc unable to load its camera HAL.

Suggested fix

Please rebuild/update the IPU7 camera HAL package against the current Arch jsoncpp ABI, or declare/provide the exact jsoncpp soname required by the shipped HAL. It may also be useful for the install/update path to verify the HAL’s shared-library dependencies.

Related reports: #6000, #7776, and Discussion #7279.

View raw text
## Summary

The integrated webcam on a Dell XPS 14 (IPU7 / OV08X40) is not usable in Omarchy 4.0.3. The camera kernel modules and sensor bind successfully, but the bundled Intel camera HAL is linked against an older jsoncpp ABI than current Arch provides.

## Reproduction

1. Boot Omarchy 4.0.3 on a Dell XPS 14 with the OV08X40 camera.
2. Start the camera stack:
   ```
   sudo systemctl restart camera-init.service [email protected]
   ```
3. Run `gst-inspect-1.0 icamerasrc`.

Before installing the cached older jsoncpp package, the output included:

```
HalAdaptor: load_camera_hal_library, failed to open library:
/usr/lib/libcamhal/plugins/ipu75xa.so,
error: libjsoncpp.so.26: cannot open shared object file: No such file or directory
```

The resulting relay logs then show:

```
CameraParserInvoker: getAvailableSensors, Found IPU: IPU7
CameraParserInvoker: parseSensors: No sensors available
gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed
```

Applications such as Chromium/Google Meet remain stuck at “Camera is starting” and then fail.

## Observed system state

- Omarchy: `4.0.3-1`
- Kernel: `7.2.3-arch1-1-ptl`
- `v4l2-relayd`: `0.2.0-2.2`
- Current Arch `jsoncpp`: `1.9.8-1`, providing `libjsoncpp.so.27`
- Intel HAL: `/usr/lib/libcamhal/plugins/ipu75xa.so`
- Loaded modules include `intel_ipu7`, `intel_ipu7_isys`, `intel_ipu7_psys`, `ov08x40`, and `intel_cvs`.
- The sensor is bound at `i2c-OVTI08F4:00`.
- `/dev/media0` and `/dev/video50` exist.

The media graph contains IPU7 CSI/ISYS nodes but no OV08X40 sensor entity when the HAL is attempted.

## Temporary workaround

Installing the cached Arch package `jsoncpp-1.9.6-3` restores `libjsoncpp.so.26`; then `ldd /usr/lib/libcamhal/plugins/ipu75xa.so` resolves successfully. This suggests the camera package/HAL is stale relative to the current Arch jsoncpp ABI.

## Expected behavior

The Omarchy IPU7 camera installation should have a compatible HAL and jsoncpp dependency, and a normal `omarchy update` should not leave `icamerasrc` unable to load its camera HAL.

## Suggested fix

Please rebuild/update the IPU7 camera HAL package against the current Arch jsoncpp ABI, or declare/provide the exact jsoncpp soname required by the shipped HAL. It may also be useful for the install/update path to verify the HAL’s shared-library dependencies.

Related reports: #6000, #7776, and Discussion #7279.

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.