Opt-in federation for Linux failures

Fixer turns corroborated breakage into patchable work.

Hosts with no Codex can still upload findings. Willing participants with Codex can pull promoted issues, attempt a patch, or explain why a patch is not honest yet. When Fixer produces a patch, it nudges the user to review it and send it upstream.

4
Opted-in installs seen
25
Submission bundles processed
77
Promoted issue clusters
0
Ready patch attempts

Privacy and consent

Fixer may unintentionally collect private or sensitive data, including local paths, package metadata, command lines, stack traces, warning lines, and other evidence gathered to diagnose issues. Uploading findings to a server is opt-in. Richer evidence such as raw coredumps or whole repositories requires a second explicit approval.

Network participation is disabled until the user explicitly opts in. Public pages and public issue JSON only expose aggregate sanitized metadata, never hostnames, install IDs, raw command lines, or evidence bundles.

How the network works

1. Hosts collect findings locally and opt in before uploading.

2. The server quarantines new issue clusters and promotes only corroborated or trusted submissions.

3. Volunteer workers with Codex pull promoted work, produce a patch or a reason it is not patchable yet, and affected users are encouraged to submit the result upstream.

Last submission processed: 2026-03-29 11:17 UTC

Install from APT

Add the public Fixer repository and install the package with normal APT tooling.

curl -fsSL https://fixer.maumap.com/apt/fixer-archive-keyring.gpg | sudo gpg --dearmor -o /usr/share/keyrings/fixer-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/fixer-archive-keyring.gpg] https://fixer.maumap.com/apt/ stable main" | \
sudo tee /etc/apt/sources.list.d/fixer.list >/dev/null
sudo apt update
sudo apt install fixer

The repository lives at https://fixer.maumap.com/apt/. The public signing key is published at https://fixer.maumap.com/apt/fixer-archive-keyring.gpg.

Promoted issues right now

Crash with stack trace in chrome

crash

Top frame: n/a [libEGL_nvidia.so.0]

highpackage: google-chrome-stablescore: 98reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/14

Crash with stack trace in nl

crash

Top frame: __pthread_kill_implementation [libc.so.6]

highpackage: rust-coreutilsscore: 98reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/13

Crash with stack trace in ZoomWebviewHost

crash

Low-signal stack trace; unresolved frames: 1

highpackage: zoomscore: 98reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/12

Crash with stack trace in ZoomWebviewHost

crash

Low-signal stack trace; unresolved frames: 3

highpackage: zoomscore: 98reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/11

Crash with stack trace in ZoomWebviewHost

crash

Low-signal stack trace; unresolved frames: 3

highpackage: zoomscore: 98reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/10

Crash with stack trace in ZoomWebviewHost

crash

Top frame: n/a [/home/kom/.zoom/data/cefcache/3916503/screen_ai/140.18/libchromescreenai.so]

highpackage: zoomscore: 98reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/120

Crash with stack trace in zoom

crash

Top frame: _ZN9QtPrivate25QMetaTypeInterfaceWrapperIbE24IsConstMetaTypeInterfaceE+0x1af131d [/opt/zoom/zoom]

highpackage: zoomscore: 98reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/8

Kernel warning

warning

сак 29 13:05:40 nucat kernel: usb 1-4.2.4.1: Device not responding to setup address.

mediumscore: 64reports: 1

Last seen: 2026-03-29 11:14 UTC. Public JSON: /v1/issues/125