-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log file is not generated on first run #727
Labels
bug
Something isn't working
Comments
wrybyte
added a commit
to wrybyte/azahar
that referenced
this issue
Mar 19, 2025
This fix resolves issue azahar-emu#727. On first start, Log::Initialize attempts to create the `azahar-emu/log/` directory. However, it fails because `azahar-emu/` does not exist. Using FileUtil::CreateFullPath instead will create both `azahar-emu` and `log/`.
PabloMK7
pushed a commit
to wrybyte/azahar
that referenced
this issue
Mar 19, 2025
This fix resolves issue azahar-emu#727. On first start, Log::Initialize attempts to create the `azahar-emu/log/` directory. However, it fails because `azahar-emu/` does not exist. Using FileUtil::CreateFullPath instead will create both `azahar-emu` and `log/`.
OpenSauce04
pushed a commit
that referenced
this issue
Mar 20, 2025
* Fix bug where log file was not generated on first run This fix resolves issue #727. On first start, Log::Initialize attempts to create the `azahar-emu/log/` directory. However, it fails because `azahar-emu/` does not exist. Using FileUtil::CreateFullPath instead will create both `azahar-emu` and `log/`. * Update license header
OpenSauce04
pushed a commit
that referenced
this issue
Mar 20, 2025
* Fix bug where log file was not generated on first run This fix resolves issue #727. On first start, Log::Initialize attempts to create the `azahar-emu/log/` directory. However, it fails because `azahar-emu/` does not exist. Using FileUtil::CreateFullPath instead will create both `azahar-emu` and `log/`. * Update license header
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Affected Build(s)
Tested on the latest commit (d59ea25), 2120-rc1, and 2120-rc3.
Description of Issue
When running Azahar for the first time, the
log/
directory is not created andazahar_log.txt
is not written to. Only after reopening the emulator will a log file be generated. This is not ideal because this may result in important error information being lost.I suspect this is due to the fact that the
azahar-emu/
directory itself is not created initially until another action is performed (e.g., installing a CIA, launching a title, etc.).Expected Behavior
The log file should be generated on first run.
Reproduction Steps
azahar &
Before doing anything else,
azahar-emu/
is not created:This will generate
azahar-emu/
.An error is emitted to the console:
log/
subdirectory has not been created.$ ls --classify ~/.local/share/azahar-emu/ nand/ sdmc/ sysdata/
$ ls ~/.local/share/azahar-emu/log/ azahar_log.txt
Log File
Well, the issue is that there is not a log file...
azahar_log.txt
System Configuration
CPU: AMD Ryzen 5 7640U
GPU/Driver: AMD Radeon 760M (RADV PHOENIX)
RAM: 2 x 8GB 5600 MT/s
OS: Fedora Linux 41 (Sway)
The text was updated successfully, but these errors were encountered: