[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."

# ── Dynamic linker / shared libraries ────────────────────────────────────────

[[patterns]]
id       = "missing-shared-library"
sources  = ["journald"]
match_text = "cannot open shared object file: No such file or directory"
severity = "warn"
title    = "App is missing a system library"
body     = "This program needs a shared library that isn't installed. On Linux, apps use shared system libraries rather than bundling their own — unlike Windows .exe files. Find the right package: zypper what-provides 'libname.so.6'. Or search: zypper search libname. Install it: sudo zypper install packagename. Note: pip and pip3 cannot fix this — Python packages are not system libraries."

[[patterns]]
id       = "slow-boot-network-wait"
sources  = ["journald"]
match_text = "Failed to start Network Wait Online"
severity = "warn"
title    = "Boot is slow: waiting for network"
body     = "systemd is waiting for a full network connection before finishing boot. This is almost never needed on a desktop or laptop. Disable it: sudo systemctl disable systemd-networkd-wait-online.service NetworkManager-wait-online.service — then reboot. Unlike Windows, Linux lets you disable any boot step that isn't relevant to your setup."

[[patterns]]
id       = "slow-boot-device-timeout"
sources  = ["journald"]
match_text = "Timed out waiting for device"
severity = "warn"
title    = "Boot is slow: a device that no longer exists"
body     = "systemd is waiting for a disk, partition, or device that isn't connected. Common cause: /etc/fstab has an entry for an external drive or old partition. Check: cat /etc/fstab — look for lines pointing to drives that aren't always connected. Add the 'nofail' option to make them optional: UUID=xxx /mnt/point type defaults,nofail 0 0. Or comment the line out with #."

[[patterns]]
id       = "slow-boot-long-running-job"
sources  = ["journald"]
match_text = "A start job is running for"
severity = "info"
title    = "A service is taking a long time to start"
body     = "A background service is taking longer than expected during boot. To find what's slowing your startup: open a terminal after booting and run: systemd-analyze blame — the top entries are the biggest contributors. For a visual timeline saved to a file: systemd-analyze plot > ~/boot-profile.svg — then open the SVG in a browser."

# ── SSH / remote access ───────────────────────────────────────────────────────

[[patterns]]
id       = "ssh-permissions-key"
sources  = ["journald"]
match_text = "WARNING: UNPROTECTED PRIVATE KEY FILE"
severity = "warn"
title    = "SSH key permissions are too open"
body     = "Your SSH private key is readable by other users on this system — SSH refuses to use it as a security measure. Fix: chmod 600 ~/.ssh/id_rsa (replace id_rsa with the key filename shown in the error). Also lock the directory: chmod 700 ~/.ssh. This is different from Windows where file permissions are mostly advisory."

# ── Flatpak ───────────────────────────────────────────────────────────────────

[[patterns]]
id       = "flatpak-missing-runtime"
sources  = ["journald"]
match_text = "error: runtime/org."
severity = "warn"
title    = "Flatpak app is missing a runtime"
body     = "A Flatpak app can't find a required runtime (a shared set of libraries). Update all runtimes first: flatpak update — if that doesn't fix it, reinstall the app: flatpak install flathub com.example.AppName. Flatpak runtimes are like Windows runtime packages (VC++ Redistributable) but for Linux apps."

# ── Display / Wayland compatibility ──────────────────────────────────────────

[[patterns]]
id       = "xwayland-crash"
sources  = ["journald"]
match_text = "XWayland server terminated unexpectedly"
severity = "warn"
title    = "XWayland crashed"
body     = "XWayland is the compatibility layer that lets older X11 apps run under Wayland. It crashed, so apps that aren't Wayland-native will stop working until you restart your session. If XWayland keeps crashing: make sure it's installed (sudo zypper install xorg-x11-server-Xwayland) and check GPU driver stability. Log out and back in to recover."