Skip to content

OMUS v1.0.4 — Every mouse. One system.

Choose a tag to compare

View all tags
@github-actions github-actions released this 20 Sep 07:58
· 11 commits to main since this release
v1.0.4
912bdcc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

OMUS v1.0.4 — Reliable runtime recovery and safe fast proof

Reliability

  • OMUS now restores enabled runtime features automatically after reboot/login,
    service restart, process failure, delayed tray availability, desktop-shell
    restart, temporary D-Bus loss, and device reconnect.
  • The purple OMUS battery tray recovers automatically when the graphical
    environment becomes ready. A real cold-boot acceptance test required no
    manual intervention.

DPI correctness

  • Fixed startup and reconnect synchronization when saved software state differed
    from the mouse's actual native DPI.
  • Hardware now determines current DPI while configuration determines the
    available DPI choices. Notifications reflect confirmed hardware state, and
    startup reconciliation does not produce a false DPI-change notification.

Performance

  • On the tested Logitech G305/Fedora environment, observed startup improved from
    about 6,170 ms to 2,428 ms and USB DPI-management recovery from about 16,042 ms
    to 5,074 ms. Corrected reconnect acceptance measured about 86.9 ms for
    remapping and 5,001 ms for DPI management.
  • Normal DPI cycling remained about 20 ms and two HID requests. Warm proof from
    a current known owner measured a 73.474 microsecond median and added zero HID
    requests. These observations are specific to the tested system and are not
    guarantees for every mouse or host.

Discovery and safety

  • Capability proof is now explicit and capability-specific: UNKNOWN,
    READ_PROVEN, WRITE_SEMANTICS_KNOWN, WRITE_BOUNDED, WRITE_VERIFIED, and
    PERSISTENCE_PROVEN.
  • Known protocol implementations reuse established immutable knowledge instead
    of treating known hardware as a blank slate. Write permission still depends
    on concrete identity, bounds, packet isolation, routing, confirmation, failure,
    compatibility, and runtime-policy evidence.
  • Persistent writes, unresolved shared-packet writes, generic HID writes,
    ambiguous targets, unsupported report-rate ownership, and insufficiently
    proven storage operations remain blocked.

Primary artifacts are omus-1.0.4-1.fc44.noarch.rpm,
omus_1.0.4_all.deb, OMUS-1.0.4-x86_64.AppImage,
omus-1.0.4-py3-none-any.whl, and omus-1.0.4.tar.gz.

VirusTotal analysis

VirusTotal scanned the five primary distributable artifacts. Results are a point-in-time signal, not a certification of safety.

Artifact SHA-256 Result at scan time Analysis
OMUS-1.0.4-x86_64.AppImage 0318a1faf36a9a6f413edbda3ce6ead1c999ef8e44830541080173a5056190f6 0 detections at scan time VirusTotal analysis
omus-1.0.4-1.fc44.noarch.rpm fc6b8b72f3fcf3a2c565886af29bebfa93dfc3e1612311da799e71f766513682 0 detections at scan time VirusTotal analysis
omus-1.0.4-py3-none-any.whl cc6377f1f46d4f2e1917c1ad181de39e21cd4877e529ccf8f9e0b7a0e0fc7281 0 detections at scan time VirusTotal analysis
omus-1.0.4.tar.gz ec7d2ef65c9b5840b3969c2dbb8ae0a00b7e23e536ba2ad3e5402e985789185f 0 detections at scan time VirusTotal analysis
omus_1.0.4_all.deb 3486e88af2125d2699621948ca8ab4d5f94aaa594dbe8742726d11f46bae6f9d 0 detections at scan time VirusTotal analysis
Assets 10
Loading