VBA hangs when closed. Must be killed with -9

[FakeNamePleaseDeleteMe]

Binary package hint: visualboyadvance

When closing VBA (pressing esc) it hangs with "Shutting down" as its last sentence. The window just stay there.

And worse, if you have it running at full screen the desktop will be unusable. You can't change desktops or do anything except switching to one of the terminal to kill -9 it.

This bug started happening in gutsy. It's happens 90% of the time, and sometimes it happens randomly even though you didn't try to shut VBA down.

I suspect the sound, because it began stuttering and stopping more than in fiesty, especially if you use the turbo button. I'm using libsdl1.2debian-oss.

[FakeNamePleaseDeleteMe (6br8gshz0nmy1pc)]

UPDATE!

This only happens when I modprobe snd_hda_intel with model=auto or model=3stack. So that confirms my suspicion about the sound.

BTW: I had to add "options snd-hda-intel model=3stack" to /etc/modprobe.d/alsa-base to fix the drop in sound volume that happened after the upgrade from fiesty to gutsy.

[Christian Apolloni (christian-apolloni)]

Here it happens every time no matter the options for snd-hda-intel.
A strace suggests it waits for a futex forever.

In the ubuntu repositories (amd64) there is version 1.8 beta3, the stable version is missing... I tried with the executable of the stable version (1.7.2) from debian and it works correctly.

[Christian Apolloni (christian-apolloni)]

Forgot to say that with gvba (GTK executable) it works correctly, the bug happens only with the GUI-less executable.

I'd like to be able to use the GUI-less version since the GTK one has very choppy sound...

[Adna rim (adnarim)]

I can confirm this problem with Gutsy and visualboyadvance.

[Christian Apolloni (christian-apolloni)]

As alternative workaround for people willing to play GBA games, mednafen works very well.

It's GBA emulation is based on VBA from what I read but this bug does not happen. At least in my case it provides better sound and very nice filters for high resolution too.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.