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

[issue]: Fedora 38 does not boot when a directory in its path contains a space on Ventoy 1.0.90+ #2385

Closed
1 task done
Silejonu opened this issue May 8, 2023 · 2 comments

Comments

@Silejonu
Copy link
Contributor

Silejonu commented May 8, 2023

Official FAQ

  • I have checked the official FAQ.

Ventoy Version

1.0.91

What about latest release

Yes. I have tried the latest release, but the bug still exist.

Try alternative boot mode

Yes. I have tried them, but the bug still exist.

BIOS Mode

Both

Partition Style

MBR

Disk Capacity

256GB

Disk Manufacturer

SanDisk / Samsung

Image file checksum (if applicable)

None

Image file download link (if applicable)

https://download.fedoraproject.org/pub/fedora/linux/releases/38/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-38-1.6.iso

What happened?

When booting Fedora 38, it reaches GRUB, but hangs for a while, then after a couple minutes, the screen gets spammed by error messages and ends up on this:
IMG_20230508_093259

The problem only occurs when a directory in the ISO path contains a space:

  • /Ventoy/Fedora Workstation/Fedora-Workstation-Live-x86_64-38-1.6.iso will not boot
  • /Ventoy/Fedora/Fedora-Workstation-Live-x86_64-38-1.6.iso will boot correctly

I could reproduce the bug in the following conditions:

  • MBR and GPT style partitions
  • exFAT filesystem (I did not try with NTFS or anything else)
  • Ventoy 1.0.90 and 1.0.91
  • 3 different computers, with various configurations
  • 3 different flash drives

The problem is not present on Ventoy 1.0.89. Other operating systems seem to not be affected.

@ventoy
Copy link
Owner

ventoy commented May 8, 2023

Please refer #2360

@Silejonu
Copy link
Contributor Author

Silejonu commented May 8, 2023

Please refer #2360

This does indeed fix the issue, thank you.

I checked for existing bug reports, but did not think of checking already closed ones, sorry.

@Silejonu Silejonu closed this as completed May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants