FS#65591 - [alsa-lib] alsa-lib 1.2.2 causes shovel knight to break

Attached to Project: Arch Linux
Opened by Dark Wav (DarkWav) - Saturday, 22 February 2020, 19:30 GMT
Last edited by freswa (frederik) - Sunday, 23 February 2020, 15:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
David Runge (dvzrv)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When upgrading alsa-lib to from version 1.2.1.2-3 to version 1.2.2-1, the game "Shovel Knight" from steam will no longer launch.
No specific errors in console can be seen, any ideas?

Additional info:
* package version(s): 1.2.2-1
* config and/or log files etc. N/A
* link to upstream bug report, if any: https://github.com/alsa-project/alsa-lib/issues/27

Steps to reproduce:
1. Upgrade alsa-lib to 1.2.2-1
2. Try to launch the game "Shovel Knight".

It will not launch, just crash on startup.
This task depends upon

Closed by  freswa (frederik)
Sunday, 23 February 2020, 15:27 GMT
Reason for closing:  Upstream
Comment by Dark Wav (DarkWav) - Sunday, 23 February 2020, 11:05 GMT
So, after some investigation, I found out the broken commits and created a patch to revert them (the fix-shovelknight-crash-alsalib.patch file).
When applying the patch in prepare() by running
patch -p1 -i ../fix-shovelknight-crash-alsalib.patch
and adding the fix-shovelknight-crash-alsalib.patch file to sources, the game will launch fine again.
The sha512sum of fix-shovelknight-crash-alsalib.patch is a6ebd122e1b3532c8ba905b9dc80f868e6ed3437322e4a07975bf5fabb59afc012a6ba8e710eb471f744f222b05b627b0d691a202167ebf2df2db179b2f76799
I don't know if any side effects exist, but I haven't noticed any myself so far.
Is someone able to further investigate wether this patch will have negative side effects or not?
   fix-shovelknight-crash-alsali... (0.7 KiB)
Comment by Dark Wav (DarkWav) - Sunday, 23 February 2020, 13:04 GMT
After some Investigation I found out its a configuration problem, currently discussing with upstream what to do.

Loading...