Tracer

Games / Fire Emblem Engage

Report #134

Sent svcBreak

Crash on launch when Cobalt 1.31.0 is loaded; doesn't crash on launch if the vanilla game is loaded
Added
As far as I can tell about the new Fire Emblem Engage Cobalt issue is that it has something to do with `nn::fs::ResultNotMounted` (2002-6905)
Game
Fire Emblem Engage
Console
Switch
Title ID
0100A6301214E000
Game version
2.0.0
Signature
svcBreak in 0100A6301214E000 sdk+1470d8
Build
ScarletNX detached ed62d0f-dirty, committed 2026-11-13 (clang 22.1.8, Linux x86_64)
Build ed62d0f-dirty is not a published build (local changes): numbers from it may not match main.
System
'Gentoo Linux' (Linux 7.2.11-tkg-eevdf-gentoo-llvm22-x86_64_v3), AMD Ryzen 7 3700X 8-Core Processor, 16 threads, 31 GB RAM
GPU
AMD Radeon RX 7800 XT (RADV NAVI32)
Driver
06802004

0100A6301214E000.log 69 KB

View the log Download

The game stopped (svcBreak, reason 0). See the .log for details.

In sdk+1470d8

  1. f221918 nn::diag::detail::Abort(nn::Result const*)+18
  2. f2200d8 sdk+1470d8
  3. f22019c sdk+14719c
  4. f2964fc sdk+1bd4fc
  5. ef6b310 subsdk9+21e310

The game's output

Cobalt v1.31.0 is installed and running!
[ozone] nn::socket::Initialize called for the first time

The last lines

    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u type 7 cmd 2 -> 0 (not served: control)
    bsd:u cmd 0 (in 7 8000) -> 0
    bsd:u cmd 1 (in 0 0) -> 0
    nn::am::service::IApplicationFunctions cmd 22 (in 35f202 0) -> 0
FATAL: The game stopped (svcBreak, reason 0). See the .log for details.