Found a bug? Please report it, but remember to follow the bug reporting guidelines.
Missing a sane feature? Let us know!
But please do NOT request ports to other systems.
I'm running Ubuntu 10.10 and was playing Chrono Trigger just fine until today. I often use the "save state" feature, but today it crashed on me. Ran zsnes in terminal and found it is a "Segmentation Fault." Scoured various forums and adjusted permissions and paths, but no avail; ZSNES won't load my save state in Chrono Trigger. below is the output from terminal when trying to load save state.
Starting Mouse detection.
Unable to poll /dev/input/event7. Make sure you have read permissions to it.
Unable to poll /dev/input/event6. Make sure you have read permissions to it.
Unable to poll /dev/input/event5. Make sure you have read permissions to it.
Unable to poll /dev/input/event4. Make sure you have read permissions to it.
Unable to poll /dev/input/event3. Make sure you have read permissions to it.
Unable to poll /dev/input/event2. Make sure you have read permissions to it.
Unable to poll /dev/input/event1. Make sure you have read permissions to it.
Unable to poll /dev/input/event0. Make sure you have read permissions to it.
ManyMouse: 0 mice detected.
ao_alsa ERROR: Unrecognized channel name "� B��t��
<������ �
�|�R�+1�����&" in channel matrix "� B��t��
<������ �
�|�R�+1�����&"
ao_alsa WARNING: Input channel matrix invalid; ignoring.
Check your ALSA configuration in .asoundrc in your home directory, /etc/asound.conf and as a last resort, /usr/share/alsa/alsa.conf. The last one should mention any other files it's sourcing, and if it is, check those too.
Otherwise, it seems like a bug in your distribution's libraries.
Maybe these people were born without that part of their brain that lets you try different things to see if they work better. --Retsupurae
what irregularities should i be looking for? other forums have suggested that i run 'zsnes -ad alsa' (i'm a noob) but this does not resolve the issue. should i also try a clean install of zsnes??
Eh, it's probably not that if it doesn't look odd o begin with. I'd be willing to blame some package being buggy. Ubuntu auto-updates, right? Could be the source of random failures.
Maybe these people were born without that part of their brain that lets you try different things to see if they work better. --Retsupurae