FS#49197 - [retroarch] 1.3.4 crashes on launch

Attached to Project: Community Packages
Opened by J (im4potato) - Tuesday, 03 May 2016, 20:22 GMT
Last edited by Maxime Gauduin (Alucryd) - Thursday, 05 May 2016, 08:37 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The newly added retroarch 1.3.4 crashes on launch.

Terminal Output:
Protocol error: bad 3 (Window); Sequence Number 5
Opcode (20, 0) = GetProperty
Bad resource 546772258 (0x20971522)
at -e line 15.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Thursday, 05 May 2016, 08:37 GMT
Reason for closing:  Not a bug
Comment by Maxime Gauduin (Alucryd) - Wednesday, 04 May 2016, 16:46 GMT
Some more context would be nice... Is that a clean install or an upgrade? Did 1.3.2 work?
Comment by J (im4potato) - Wednesday, 04 May 2016, 20:18 GMT
Prior to the 1.3.4 update I had been using the retroarch 1.3.2 package found in the AUR (https://aur.archlinux.org/packages/retroarch), which worked fine. With this latest update the package apparently got added to the official repos and the update got pulled from there, but ever since that upgrade it won't launch. I ran pacman -Rncs retroarch and reinstalled it, but I get the same results.
Comment by Maxime Gauduin (Alucryd) - Thursday, 05 May 2016, 06:18 GMT
It's probably just a configuration issue, did you try deleting your configuration? Both 1.3.2 and 1.3.4 work just fine here.
Comment by J (im4potato) - Thursday, 05 May 2016, 06:58 GMT
I just ran pacman -Rncs retroarch again, and then deleted the RetroArch configuration file at /etc/retroarch.cfg. Reinstalling after that did not change anything, it crashes with the same error as above. I then tried installing the retroarch-assets-xmb package just in case that was causing the issue, but that changed nothing as well.

I'm using Mesa with radeonsi if that helps at all.
Comment by Maxime Gauduin (Alucryd) - Thursday, 05 May 2016, 07:07 GMT
Dude, that file is a default config that comes with the package, it is required and should work at all times. The configuration you're looking for is located, like virtually everything out there, in ~/.config.
Comment by sdfdsfsdf (dekece) - Thursday, 05 May 2016, 07:14 GMT
I also had the same problem, it would just crash on launch. running reatroarch --verbose told problems about config, at which point (like mentionned above) renaming the folder .config/retroarch enabled it to launch.

Of course the new config tht gets created is a clean slate, but you can still re-add files if needed (or reconfig, it's rather easy), but at least it does fix the crashing.
Comment by J (im4potato) - Thursday, 05 May 2016, 08:14 GMT
I was only aware of the config mentioned on the wiki, deleting the old config did work. Thank you.
Comment by J (im4potato) - Thursday, 05 May 2016, 08:14 GMT
Everytime I refreshed the page it posted another comment? Now I'm really looking like an idiot.
Comment by Maxime Gauduin (Alucryd) - Thursday, 05 May 2016, 08:36 GMT
You can delete comments, it's no big deal. Anyway, closing this now. Keep an eye out on changes in /etc/retroarch.cfg via pacdiff, this'll usually tell you when the default config changes and that you need to change yours accordingly.

Loading...