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

Segfault at HDMI step of the 4.91 XMB initial setup under Linux #16465

Closed
nathanielcwm opened this issue Dec 28, 2024 · 15 comments · Fixed by #16513 · May be fixed by #16510
Closed

Segfault at HDMI step of the 4.91 XMB initial setup under Linux #16465

nathanielcwm opened this issue Dec 28, 2024 · 15 comments · Fixed by #16513 · May be fixed by #16510

Comments

@nathanielcwm
Copy link

nathanielcwm commented Dec 28, 2024

Quick summary

Under Arch Linux (6.13rc3) when trying to run the XMB at the HDMI step it segfaults and the emulator freezes when I try stopping the emulation.

Details

I used the AUR rpcs3-git package (7a4e88c and b2949f1). The issue also persists with the AppImage.

The issue does not occur under Windows 11 23H2 (b2949f1)

Using Vulkan on both Linux and Windows

Attach a log file

RPCS3.log
TTY.log

Attach capture files for visual issues

No response

System configuration

ArchLinux w/ CachyOS Zen 4 repos

6.13rc3

R5 7540U

Mesa 24.3.2-cachyos1.2

KDE Plasma 6.2.4 (Wayland)

Pipewire 1.2.7

LLVM 18.1.8-10

Other details

Answering both Yes and No to this step of the initial startup crashes the emulator with a similar segfault.

@Mr-Bobby
Copy link

I've had the same issue on Pop!-os linux. Same thing where when selecting either yes or no at option of using HDMI on initial setup it just crashes and then freezes when trying to close it. Tried re-setting it and redoing, and deleting and downloading fresh the latest AppImage but still it still crashes at that stage on set-up.

@CrazyCSIW6
Copy link

This issue appears to now be occurring under Windows as well.

@nathanielcwm
Copy link
Author

This issue appears to now be occurring under Windows as well.

wtf

@alexconsole04
Copy link

The initial set up process is what's broken, however if you've already set it up before it broke recently, you won't experience this issue.

@Mr-Bobby
Copy link

Mr-Bobby commented Dec 30, 2024

I managed to get it working it seems, at least to the point of installing the playstation software and getting to the main menu. I rolled back to an older version that I thought might be old enough to potentially not have the bug, and chose version 34-17220. This time the PS3 interface came up in the game list, so I reset the cache and tried again at running the PS3 software installer, and this time it worked, and managed to complete the set-up. Yet to try any actual games but it seems at least rolling back to an older version should get it to run in the mean time until a proper fix is sorted.

@borpshws
Copy link

this issue is also happening for me on windows 11 using firmware 4.91

regardless of selecting yes or no to the HDMI prompt, the program crashes

@bigol83
Copy link

bigol83 commented Dec 31, 2024

This issue appears to now be occurring under Windows as well.

Same for me,Windows 10, i just didn't care for xmb considering it's not really useful right now

@nameAltF4
Copy link

I have the same issue.

My system specs:

Acer Nitro 5 AN515-58
Intel i5 12500H
RTX 3050 Ti Laptop GPU / Intel UHD Graphics
8 GB DDR4 3200 MHz RAM

Windows 10
RPCS3 1 January 2025 build

@emeraldsucksss
Copy link

happening to me on Windows 11 23H2, im on the latest version of RPCS3

@emeraldsucksss
Copy link

image

no matter what i choose it never works

@quangmng
Copy link

quangmng commented Jan 3, 2025

I rolled back to an older version that I thought might be old enough to potentially not have the bug, and chose version 34-17220.

BTW Is there a way you can roll back/install older versions of RPCS3 for Windows (other than build/cmake)? Looking up the homepage & download only has the latest version available.

@emeraldsucksss
Copy link

I rolled back to an older version that I thought might be old enough to potentially not have the bug, and chose version 34-17220.

BTW Is there a way you can roll back/install older versions of RPCS3 for Windows (other than build/cmake)? Looking up the homepage & download only has the latest version available.

https://rpcs3.net/compatibility?b

@alexconsole04
Copy link

alexconsole04 commented Jan 3, 2025

Found the version that broke the Initial Setup which is the main issue everyone here is facing, that being 17230.
Downgrading to 17229 is the last working build, so alongside #16472, this is a regression.
Screenshot_2025-01-03_000928

Log for reference from 17230: RPCS3.log
Please test and report this is the case.

@emeraldsucksss
Copy link

Found the version that broke the Initial Setup which is the main issue everyone here is facing, that being 17230.

Downgrading to 17229 is the last working build, so alongside #16472, this is a regression.

Screenshot_2025-01-03_000928

Log for reference from 17230: RPCS3.log

Please test and report this is the case.

You're a lifesaver to those who are confused on which version to downgrade to. Guess you're here on GitHub for a reason other than school. 😆

Jokes aside, this info could be really useful. Maybe one of the changes in 17230 should be reverted back?

@emeraldsucksss
Copy link

emeraldsucksss commented Jan 4, 2025

Still wonder, why was the issue closed when we are still awaiting a fix. Do they not want people to know about this💀💀

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

Successfully merging a pull request may close this issue.

9 participants