Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

bth · 2026-08-12T12:34:04+0100

kyuuemu said:
After installing this fork all homebrew apps instantly crashed Atmosphere and threw me back into Hekate. Reverting to the original Atmosphere fixed it. Using it with with sys-patch and everything seems to work.

that doesnt make much sense, most likely have homebrew of the outdated ABI.

my fork doesn't crash homebrew that has the new homebrew ABI.

kyuuemu · 2026-08-12T15:58:44+0100

bth said:
that doesnt make much sense, most likely have homebrew of the outdated ABI.

my fork doesn't crash homebrew that has the new homebrew ABI.

no it has nothing to do with the ABI, it affected literally every homebrew app including the ones Atmosphere ships with

and reverting to same original Atmosphere version fixed it which is the exact same ABI

bth · 2026-08-12T18:56:10+0100

kyuuemu said:
no it has nothing to do with the ABI, it affected literally every homebrew app including the ones Atmosphere ships with

and reverting to same original Atmosphere version fixed it which is the exact same ABI

That doesn't make much sense. When compiling atmosphere, you compile every homebrew atmosphere normally ships with.

even if theoretically something was compiler linked to libnx version, other ABI, and so on, those homebrew would be compile time linked to the atmosphere fork.

for atmosphere, the only included homebrew .nro's are the usb mtp one, daybreak (firmware upgrade/downgrader) and reboot_to_payload, all of which is compiled while compiling atmosphere

that and /atmosphere/hbl.nsp (homebrew launcher ship/trampoline) + ./hbmenu.nro (what you launch opening album) (these two are not compiled fresh during releases, but rather includes the latest versions from switchbrew)

tl:dr sounds like problem caused by something else, not my fork.

Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

Well-Known Member

Member

Well-Known Member

Similar threads

Popular threads in this forum