Closed HalcyonSeas73 closed 1 year ago
Te faltan los sighpatches correctos.
El El vie, 13 oct 2023 a las 20:59, HalcyonSeas73 @.***> escribió:
Bug Report What's the issue you encountered?
After installing the latest Atmosphere update (1.6.0-master-8a9eb85e0) and Hekate 6.0.7, I booted into emuMMD, and after a few seconds, this error screen appeared.
[image: image] https://user-images.githubusercontent.com/84727791/275011266-bbfca065-9ab9-44ec-aefe-f0a74afcabdc.png
No changes were made to Atmosphere itself. How can the issue be reproduced?
As indicated in the initial description, this error can be reproduced by updating Atmosphere to 1.6.0 Crash Report
https://gist.github.com/HalcyonSeas73/31d3a174b5ede79f7a7fa70e692a5998/raw/3c1c29b9469a2a579a40c1149503f74d4ca8e7be/01697222774_0100000000001000.log System Firmware Version
17.0.0 Environment?
- What bootloader (fusèe, hekate, etc) was Atmosphère launched by: Hekate
- Official release or unofficial build: Official
- Do you have additional kips or sysmodules you're loading:
- Homebrew software installed: [N/A]
- EmuMMC or SysNAND: EmuMMC
Additional context?
- Additional info about your environment: N/A
— Reply to this email directly, view it on GitHub https://github.com/Atmosphere-NX/Atmosphere/issues/2205, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATM72Y5V3ICBFHJ4Z7H36S3X7GFR5AVCNFSM6AAAAAA57RV6ZCVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE2DENBYGAZTSMY . You are receiving this because you are subscribed to this thread.Message ID: @.***>
mismo error, donde actualizo los sighpatches?
Same error, where update the sighpatches?
The actual error here is that prodinfo blanking is fixed in 17.0.0, and causes a fatal error now. You'll have to disable it (and rely on dns redirection or airplane mode). To the commenters, piracy is not supported
Bug Report
What's the issue you encountered?
After installing the latest Atmosphere update (1.6.0-master-8a9eb85e0) and Hekate 6.0.7, I booted into emuMMD, and after a few seconds, this error screen appeared.
No changes were made to Atmosphere itself.
How can the issue be reproduced?
As indicated in the initial description, this error can be reproduced by updating Atmosphere to 1.6.0
Crash Report
https://gist.github.com/HalcyonSeas73/31d3a174b5ede79f7a7fa70e692a5998/raw/3c1c29b9469a2a579a40c1149503f74d4ca8e7be/01697222774_0100000000001000.log
System Firmware Version
17.0.0
Environment?
Additional context?