Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Bluetooth modules not loading on 3.2
Reported by mburns75 · filed Nov 21, 2025Closed upstream on 2025-11-22 by its own reporter mburns75. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
System details
HP Dev 1 | Omarchy 3.2
What's wrong?
Attempts at launching bluetui result in " Error: internal error: D-Bus error org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed"
Prior to upgrading to Omarchy 3.2, I had successfully used and paired devices via the Bluetooth GTK. However, after upgrading, dmesg reports no bluetooth devices.
~ ❯ sudo dmesg | grep -i -e bluetooth -e blue -e hci
[sudo] password for dvader:
[ 1.020577] xhci_hcd 0000:03:00.3: xHCI Host Controller
[ 1.020584] xhci_hcd 0000:03:00.3: new USB bus registered, assigned bus number 1
[ 1.020690] xhci_hcd 0000:03:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
[ 1.020992] xhci_hcd 0000:03:00.3: xHCI Host Controller
[ 1.020996] xhci_hcd 0000:03:00.3: new USB bus registered, assigned bus number 2
[ 1.020999] xhci_hcd 0000:03:00.3: Host supports USB 3.1 Enhanced SuperSpeed
[ 1.021048] usb usb1: Product: xHCI Host Controller
[ 1.021050] usb usb1: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd
[ 1.021477] usb usb2: Product: xHCI Host Controller
[ 1.021479] usb usb2: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd
[ 1.022250] xhci_hcd 0000:03:00.4: xHCI Host Controller
[ 1.022254] xhci_hcd 0000:03:00.4: new USB bus registered, assigned bus number 3
[ 1.022349] xhci_hcd 0000:03:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010
[ 1.022632] xhci_hcd 0000:03:00.4: xHCI Host Controller
[ 1.022635] xhci_hcd 0000:03:00.4: new USB bus registered, assigned bus number 4
[ 1.022637] xhci_hcd 0000:03:00.4: Host supports USB 3.1 Enhanced SuperSpeed
[ 1.022672] usb usb3: Product: xHCI Host Controller
[ 1.022673] usb usb3: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd
[ 1.023093] usb usb4: Product: xHCI Host Controller
[ 1.023095] usb usb4: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd
[ 1.260100] usb 3-1: new high-speed USB device number 2 using xhci_hcd
[ 1.510604] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 1.633342] usb 3-4: new high-speed USB device number 3 using xhci_hcd
[ 1.830333] usb 3-1.1: new high-speed USB device number 4 using xhci_hcd
[ 1.990659] usb 4-1.2: new SuperSpeed USB device number 3 using xhci_hcd
[ 2.127345] usb 3-1.3: new high-speed USB device number 5 using xhci_hcd
[ 2.309339] usb 3-1.1.1: new low-speed USB device number 6 using xhci_hcd
[ 2.627340] usb 3-1.1.3: new low-speed USB device number 7 using xhci_hcd
[ 4.624390] usb 3-1.4: new full-speed USB device number 8 using xhci_hcd
[ 5.065776] usb 3-1.5: new high-speed USB device number 9 using xhci_hcd
[ 5.363610] usb 3-1.6: new high-speed USB device number 10 using xhci_hcd
[ 5.954726] usb 3-1.6: Product: Blue Microphones
[ 6.049611] input: Generic Blue Microphones Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-1/3-1.6/3-1.6:1.3/0003:046D:0AB7.0007/input/input15
[ 6.101057] input: Generic Blue Microphones as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-1/3-1.6/3-1.6:1.3/0003:046D:0AB7.0007/input/input16
[ 6.101481] hid-generic 0003:046D:0AB7.0007: input,hiddev100,hidraw6: USB HID v1.11 Device [Generic Blue Microphones] on usb-0000:03:00.4-1.6/input3
[ 26.521176] r8152-cfgselector 4-1.2: reset SuperSpeed USB device number 3 using xhci_hcd
[ 38.322399] usb 3-1.3: reset high-speed USB device number 5 using xhci_hcdsudo modeprobe btmtk seems to load bluetooth and allow BlueTUI to launch. But BlueTUI still only presents a blank screen.
View raw text
### System details HP Dev 1 | Omarchy 3.2 ### What's wrong? Attempts at launching bluetui result in " Error: internal error: D-Bus error org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.bluez': unit failed" Prior to upgrading to Omarchy 3.2, I had successfully used and paired devices via the Bluetooth GTK. However, after upgrading, dmesg reports no bluetooth devices. ``` ~ ❯ sudo dmesg | grep -i -e bluetooth -e blue -e hci [sudo] password for dvader: [ 1.020577] xhci_hcd 0000:03:00.3: xHCI Host Controller [ 1.020584] xhci_hcd 0000:03:00.3: new USB bus registered, assigned bus number 1 [ 1.020690] xhci_hcd 0000:03:00.3: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010 [ 1.020992] xhci_hcd 0000:03:00.3: xHCI Host Controller [ 1.020996] xhci_hcd 0000:03:00.3: new USB bus registered, assigned bus number 2 [ 1.020999] xhci_hcd 0000:03:00.3: Host supports USB 3.1 Enhanced SuperSpeed [ 1.021048] usb usb1: Product: xHCI Host Controller [ 1.021050] usb usb1: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd [ 1.021477] usb usb2: Product: xHCI Host Controller [ 1.021479] usb usb2: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd [ 1.022250] xhci_hcd 0000:03:00.4: xHCI Host Controller [ 1.022254] xhci_hcd 0000:03:00.4: new USB bus registered, assigned bus number 3 [ 1.022349] xhci_hcd 0000:03:00.4: hcc params 0x0268ffe5 hci version 0x110 quirks 0x0000020000000010 [ 1.022632] xhci_hcd 0000:03:00.4: xHCI Host Controller [ 1.022635] xhci_hcd 0000:03:00.4: new USB bus registered, assigned bus number 4 [ 1.022637] xhci_hcd 0000:03:00.4: Host supports USB 3.1 Enhanced SuperSpeed [ 1.022672] usb usb3: Product: xHCI Host Controller [ 1.022673] usb usb3: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd [ 1.023093] usb usb4: Product: xHCI Host Controller [ 1.023095] usb usb4: Manufacturer: Linux 6.17.8-arch1-1 xhci-hcd [ 1.260100] usb 3-1: new high-speed USB device number 2 using xhci_hcd [ 1.510604] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd [ 1.633342] usb 3-4: new high-speed USB device number 3 using xhci_hcd [ 1.830333] usb 3-1.1: new high-speed USB device number 4 using xhci_hcd [ 1.990659] usb 4-1.2: new SuperSpeed USB device number 3 using xhci_hcd [ 2.127345] usb 3-1.3: new high-speed USB device number 5 using xhci_hcd [ 2.309339] usb 3-1.1.1: new low-speed USB device number 6 using xhci_hcd [ 2.627340] usb 3-1.1.3: new low-speed USB device number 7 using xhci_hcd [ 4.624390] usb 3-1.4: new full-speed USB device number 8 using xhci_hcd [ 5.065776] usb 3-1.5: new high-speed USB device number 9 using xhci_hcd [ 5.363610] usb 3-1.6: new high-speed USB device number 10 using xhci_hcd [ 5.954726] usb 3-1.6: Product: Blue Microphones [ 6.049611] input: Generic Blue Microphones Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-1/3-1.6/3-1.6:1.3/0003:046D:0AB7.0007/input/input15 [ 6.101057] input: Generic Blue Microphones as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-1/3-1.6/3-1.6:1.3/0003:046D:0AB7.0007/input/input16 [ 6.101481] hid-generic 0003:046D:0AB7.0007: input,hiddev100,hidraw6: USB HID v1.11 Device [Generic Blue Microphones] on usb-0000:03:00.4-1.6/input3 [ 26.521176] r8152-cfgselector 4-1.2: reset SuperSpeed USB device number 3 using xhci_hcd [ 38.322399] usb 3-1.3: reset high-speed USB device number 5 using xhci_hcd ``` sudo modeprobe btmtk seems to load bluetooth and allow BlueTUI to launch. But BlueTUI still only presents a blank screen.
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.