Skip to content
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

Welcome screen isn't shown anymore #5464

Closed
2 tasks done
lkintact opened this issue Feb 4, 2025 · 4 comments · Fixed by #5478
Closed
2 tasks done

Welcome screen isn't shown anymore #5464

lkintact opened this issue Feb 4, 2025 · 4 comments · Fixed by #5478
Labels

Comments

@lkintact
Copy link

lkintact commented Feb 4, 2025

Describe the bug

Hi, I'm not sure if it's a bug, but when I was using an older (2024.07.01 SDL1) version of DOSBox-X, every time I ran it a welcome screen was shown.
That doesn't happen with the newest (2025.02.01 SDL1) DOSBox-X version - a blank screen is shown instead.

Steps to reproduce the behaviour

.

Expected behavior

No response

What operating system(s) this bug have occurred on?

Windows 10 Home 22H2

What version(s) of DOSBox-X have this bug?

2025.02.01 SDL1

Used configuration

Output log


Additional information

No response

Have you checked that no similar bug report(s) exist?

  • I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

  • I agree to follow the code of conduct and the contributing guidelines.
@lkintact lkintact added the bug label Feb 4, 2025
@maron2000
Copy link
Contributor

I haven't checked but maybe this is due to PR #5403, which may need some refinement.
Since it helps usability and freezes of actual softwares rather than a bios screen, I feel we can allow such regression for the time being.
I currently have no idea for an ultimate solution, though.

@1abcd
Copy link
Contributor

1abcd commented Feb 7, 2025

With the newest version (2025.02.01), pressing F11+R cause a blank screen too. And F11+R again, DOSBox-X crashed.

@maron2000
Copy link
Contributor

The PR I mentioned above was not the cause, but PR #5478 should fix it as far as I tested.
Please try the nightly build after it is built.

@lkintact
Copy link
Author

lkintact commented Feb 9, 2025

@maron2000, thank you, just tried this build, and the issue is gone for me. What @1abcd has reported is gone too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants