pyr0ball
e4a682be2f
New SourceOs variants: Android, IpadOs — routed to android-to-* and
ipad-to-* pattern files respectively. Pattern bodies assume zero terminal
experience; every command explained from first principles with App Store /
iOS analogies.
Dual-boot supplement system: PatternFile::extend() + load_supplement()
in patterns.rs; lib.rs loads dualboot-{windows,macos}.toml on top of the
primary pattern file when migration.dual_boot_with is set. Supplement
covers NTFS dirty flag from Fast Startup, clock skew (RTC local vs UTC),
GRUB overwrite by Windows Update, BitLocker, APFS/HFS+ access, T2 Secure
Boot.
complete_onboarding() now accepts dual_boot_with: Option<String> and
normalises it to "windows"/"macos". Onboarding.vue becomes a 3-step flow:
source OS -> (Linux distro if linux) -> (dual-boot if windows/macos).
Mobile users skip the dual-boot step entirely.
10 new pattern files (8 mobile + 2 supplements), config.rs tests updated.
103 lines
4.7 KiB
TOML
103 lines
4.7 KiB
TOML
[meta]
|
|
source_os = "android"
|
|
target_distro_family = "opensuse"
|
|
|
|
# Android user on their first openSUSE install.
|
|
# Assumes NO terminal experience. openSUSE's YaST GUI tool is a good entry point
|
|
# for users unfamiliar with terminal-based administration.
|
|
|
|
[log_paths]
|
|
steam = "~/.local/share/Steam/logs/content_log.txt"
|
|
proton = "~/.local/share/Steam/logs/proton_log.txt"
|
|
|
|
# ── Package management ────────────────────────────────────────────────────────
|
|
|
|
[[patterns]]
|
|
id = "zypper-lock"
|
|
sources = ["journald"]
|
|
match_text = "System management is locked"
|
|
severity = "warn"
|
|
title = "App installer is busy"
|
|
body = "The software installer (zypper) is already running. Wait a minute. If it's stuck: open a terminal and type: sudo zypper ps — to see what's using it."
|
|
|
|
[[patterns]]
|
|
id = "zypper-dep-conflict"
|
|
sources = ["journald"]
|
|
match_text = "conflicts with"
|
|
severity = "warn"
|
|
title = "Two apps conflict with each other"
|
|
body = "Two packages need something that can't be shared. Run a full update to resolve: sudo zypper dup — then try again."
|
|
|
|
# ── AppArmor ──────────────────────────────────────────────────────────────────
|
|
|
|
[[patterns]]
|
|
id = "apparmor-denial"
|
|
sources = ["journald"]
|
|
match_text = "apparmor=\"DENIED\""
|
|
severity = "info"
|
|
title = "App blocked by security policy"
|
|
body = "openSUSE includes AppArmor — a security layer like Android's app permissions but for the whole system. An app was blocked from doing something. Check: sudo aa-status — YaST also has an AppArmor section under Security."
|
|
|
|
# ── YaST ──────────────────────────────────────────────────────────────────────
|
|
|
|
[[patterns]]
|
|
id = "yast-backend-fail"
|
|
sources = ["journald"]
|
|
match_text = "YaST got signal"
|
|
severity = "warn"
|
|
title = "Settings tool crashed"
|
|
body = "YaST is openSUSE's settings tool — like the Settings app on Android but for the whole system. It crashed. Try: sudo yast2 — in a terminal to run the text version, which is more stable."
|
|
|
|
# ── System ────────────────────────────────────────────────────────────────────
|
|
|
|
[[patterns]]
|
|
id = "kernel-driver-firmware"
|
|
sources = ["kmsg"]
|
|
match_text = "firmware: failed to load"
|
|
severity = "warn"
|
|
title = "Hardware driver file missing"
|
|
body = "Install the firmware package: sudo zypper install kernel-firmware — restart after."
|
|
|
|
[[patterns]]
|
|
id = "oom-killer"
|
|
sources = ["kmsg"]
|
|
match_text = "Out of memory: Kill process"
|
|
severity = "warn"
|
|
title = "System ran out of memory — closed an app"
|
|
body = "Linux had to close a program to free up RAM, like Android killing background apps. If this keeps happening, openSUSE's YaST -> System -> Partitioner can add or resize swap space."
|
|
|
|
[[patterns]]
|
|
id = "disk-io-error"
|
|
sources = ["kmsg"]
|
|
match_text = "Buffer I/O error on device"
|
|
severity = "warn"
|
|
title = "Storage error"
|
|
body = "A hardware-level storage error. Install: sudo zypper install smartmontools — then check: sudo smartctl -a /dev/sda"
|
|
|
|
# ── Audio ─────────────────────────────────────────────────────────────────────
|
|
|
|
[[patterns]]
|
|
id = "pipewire-connect-fail"
|
|
sources = ["journald"]
|
|
match_text = "Failed to connect to PipeWire"
|
|
severity = "warn"
|
|
title = "Sound system not responding"
|
|
body = "Restart the audio system: systemctl --user restart pipewire pipewire-pulse wireplumber — or log out and back in."
|
|
|
|
[[patterns]]
|
|
id = "bluetooth-rfkill-blocked"
|
|
sources = ["journald"]
|
|
match_text = "Blocked through rfkill"
|
|
severity = "warn"
|
|
title = "Bluetooth blocked by software switch"
|
|
body = "Run: rfkill unblock bluetooth — in a terminal. YaST -> Network -> Bluetooth also has a toggle."
|
|
|
|
# ── Network ───────────────────────────────────────────────────────────────────
|
|
|
|
[[patterns]]
|
|
id = "networkmanager-activation-fail"
|
|
sources = ["journald"]
|
|
match_text = "Activation failed"
|
|
severity = "info"
|
|
title = "Wi-Fi connection failed"
|
|
body = "Couldn't connect to the network. Check: nmcli device status — or use YaST -> Network Settings to diagnose."
|