VisualBoyAdvance-M is a GameBoy Advance emulator. It is based on VisualBoyAdvance and integrates the best features from the various other forks.

It also features a GTK frontend.

As said on IRC today

Status: NEW => ASSIGNED
CC: (none) => mageia
Assignee: bugsquad => mageia

"VBA-M is a fork from the now inactive VisualBoy Advance project, with goals to improve the capatibility and features of the emulator with:" http://vba-m.com/about.html
	 	
It is important for a community distro as Mageia can count on great diversity of programs designed for desktop end users.

CC: (none) => frateraec

Oops,my message was not complete. I don't understand why...
As said on IRC today, I will import vba-m and make VirtualBoyAdvance provides vba-m as the first one in no more developped.

It is because the VisualBoy is having problems with audio, and this happens in several distributions. This VBA-M is the only Gameboy Advanced emulator that works today.

I'm trying to build the SVN snapshot (1103) but for now, missing dependency. WIP.

Please test vbam-1.8.0-0.svn1103.2.mga3 and enjoy!

Ok ;)

What is the link to download?

just update your media and install game:
# urpmi.update -a
# urpmi virtualboyadvance
no link as their is deps so better to wait if your repository is not uptodate.

N.B: you first need to enable "Core Updates_testing" repository

Advisory:
-------------
The package virtualboyadvance (no more maintained) is available in Mandriva 2010.x but was missing in Mageia 2 (so upgrades were broken). This update fixes this issue by providing vbam (fork of Virtualboyadvance) to Mageia distribution. This package provides virtualboyadvance and obsolete it.

Packages:
-------------
vbam-1.8.0-0.svn1103.1.mga2 (package of vbam)
sfml-1.6-2.mga2 (needed to build vbam, so please import at the same time)

How to test:
-------------
- Just try vbam check it works.
/!\ you will need a Game Boy rom file.

Assignee: mageia => qa-bugs
Summary: vbam - A GameBoy Advance emulator => [Update Request] vbam - A GameBoy Advance emulator [mga2]

If we don't provide vbam or visualboyadvance in Mageia 1, then the upgrade path still is broken as we don't guarantee upgrade from mdv 2010.1 to mga2 but to mga1.

CC: (none) => stormi

Oops, I forget Mageia 1... :-)
Thanks

Advisory:
-------------
The package virtualboyadvance (no more maintained) is available in Mandriva
2010.x but was missing in Mageia 1 and 2 (so upgrades were broken). This update fixes this issue by providing vbam (fork of Virtualboyadvance) to Mageia
distributions. This package provides virtualboyadvance and obsolete it.

Packages:
-------------
vbam-1.8.0-0.svn1103.1.mga1 (package of vbam for Mageia 1)
vbam-1.8.0-0.svn1103.1.mga2 (package of vbam for Mageia 2)
sfml-1.6-2.mga2 (needed to build vbam, so please import at the same time)
gtkglextmm-1.2.0-1.mga1 (needed to build vbam, so please import at the same time)

How to test:
-------------
- Just try vbam check it works.
/!\ you will need a Game Boy rom file.

Michael Martins: Could you please help validating this update by following the procedure described here: https://wiki.mageia.org/en/QA_process_for_validating_updates ?

Not many (QA-) people have Game Boy rom files, so your help would be very much appreciated here.

CC: (none) => wassi

I've been testing this over the weekend (I have full sets of GB/GBC/GBA Roms) and It's played everything I've given it perfectly (VirtualBoyAdvance had very glitchy sound and ran too fast and was not throttling correctly)

I've been testing this on MGA2 x86_64 edition, speed is correct, sound is correct, no slowdown, I've tested all the scalers etc (biliner/AdvanceMAME x2 etc) and they run as expected, was a little tricky getting my gamepad working (had to manually edit the config with the JoySDL keycodes) but that worked fine.

Any other requests I could try out?

CC: (none) => lemonzest

Working perfectly. Thanks:)

@ Michael Martins: Thanks a lot for your feedback! However we need one more bit of information: which architecture and Mageia version are you on? If you're unsure, please post the content of the file /etc/release (it's a plain text file, you can open it with any text editor)
Thanks a lot in advance!

@ Simon Putt: Well, if you still have an MGA1 installation somewhere, you could test the package for it. :) It needs to be tested on all architectures on all releases before it can be validated. Apart, did installing vbam obsolete virtualboyadvance (that is, if you had this package installed)? If I'm not mistaken it should... Other than that, I'm not aware of anything else that needs to be tested for. Thank you very much for your help!

Mageia release 2 (Official) for i586

Thank you!

Whiteboard: MGA1TOO => MGA1TOO, MGA2-32-OK

The advisory needs correcting, The package name is VisualBoyAdvance (not virtualboyadvance) , also the obsolete/provides in the vbam.spec need correcting the reflect this also, as the upgrade from the mandriva package to the mga one is not working (because of the incorrect package name in the spec)

(In reply to comment #20)
> The advisory needs correcting, The package name is VisualBoyAdvance (not
> virtualboyadvance) , also the obsolete/provides in the vbam.spec need
> correcting the reflect this also, as the upgrade from the mandriva package to
> the mga one is not working (because of the incorrect package name in the spec)

Oops, my bad.
Thanks, fixing and submitting it right now.
Stay tuned!

New packages are:
- vbam-1.8.0-0.svn1103.1.1.mga2
- vbam-1.8.0-0.svn1103.1.1.mga1

What means this: + Revision: 273004?

Removing whiteboard keywords as new packages need retesting

Whiteboard: MGA1TOO, MGA2-32-OK => MGA1TOO

(In reply to comment #23)
> What means this: + Revision: 273004?

What do you mean?

(In reply to comment #24)
> Removing whiteboard keywords as new packages need retesting

Just the provide, so just need to test that from MDV 2010.x to mga1 the provide works.
No need to redo all test.

$ vbam
Segmentation fault

@ Michael Martins and Simon Putt: could be please test again the new update candidates? There's no reason they wouldn't work, but we need testing since they were rebuild.

oops, the segmentation fault part above was meant to be in this comment:

On my computer it doesn't work:

$ vbam
Segmentation fault

This is all I could get as a backtrace:

(gdb) bt
#0  0x00000000 in ?? ()
#1  0xb7d0b568 in ?? () from /usr/lib/nvidia-current/libGL.so.1
#2  0x00000054 in ?? ()
#3  0xbfffec08 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I get the crash in both archs for Mageia 1 (comment #27 was about Mageia 1 i586).

Here is a better backtrace:

Starting program: /usr/bin/vbam
[Thread debugging using libthread_db enabled]
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-system.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-audio.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-graphics.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-network.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-window.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libstdc++.so.6.0.14.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/lib64/libgcc_s-4.5.2.so.1.debug

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff68f9935 in ?? () from /usr/lib64/nvidia-current/libGL.so.1
#2  0x00007ffff68f2f0b in ?? () from /usr/lib64/nvidia-current/libGL.so.1
#3  0x00007ffff68e3c69 in glXGetConfig () from /usr/lib64/nvidia-current/libGL.so.1
#4  0x00007ffff6e04ae3 in sf::priv::WindowImplX11::CreateContext(sf::VideoMode const&, XVisualInfo&, sf::WindowSettings&, XVisualInfo, unsigned long) () from /usr/lib64/libsfml-window.so.1.6
#5  0x00007ffff6e06c92 in sf::priv::WindowImplX11::WindowImplX11() () from /usr/lib64/libsfml-window.so.1.6
#6  0x00007ffff6e0263a in sf::priv::WindowImpl::New() () from /usr/lib64/libsfml-window.so.1.6
#7  0x00007ffff6e02519 in sf::Context::Context() () from /usr/lib64/libsfml-window.so.1.6
#8  0x00007ffff6e025a5 in sf::Context::GetGlobal() () from /usr/lib64/libsfml-window.so.1.6
#9  0x00007ffff6e02609 in global constructors keyed to Context.cpp () from /usr/lib64/libsfml-window.so.1.6
#10 0x00007ffff6e06ed6 in __do_global_ctors_aux () from /usr/lib64/libsfml-window.so.1.6
#11 0x00007ffff6dff553 in _init () from /usr/lib64/libsfml-window.so.1.6
#12 0x00007fffffffdba8 in ?? ()
#13 0x00007ffff7ded719 in call_init (l=0x7ffff7fd64f0, argc=-150957952, argv=0x7fffffffdb98, env=0x7fffffffdba8) at dl-init.c:70
#14 0x00007ffff7ded857 in _dl_init (main_map=0x7ffff7ffe188, argc=1, argv=0x7fffffffdb98, env=0x7fffffffdba8) at dl-init.c:134
#15 0x00007ffff7de0aca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#16 0x0000000000000001 in ?? ()
#17 0x00007fffffffdfa3 in ?? ()
#18 0x0000000000000000 in ?? ()

(In reply to comment #26)
> $ vbam
> Segmentation fault
> 
> @ Michael Martins and Simon Putt: could be please test again the new update
> candidates? There's no reason they wouldn't work, but we need testing since
> they were rebuild.

Works the same as the previous build here, no segfaults but then I'm using the Radeon/Mesa stack and not nVidia/ATI Blobs (And NO I would not be willing to install the AMD/ATI Radeon Blob)

inxi -G

Graphics:  Card: ATI Turks [Radeon HD 6670] X.Org: 1.11.4 driver: radeon Resolution: 2048x1152@59.9hz 
           GLX Renderer: Gallium 0.4 on AMD TURKS GLX Version: 2.1 Mesa 8.0.2

Updating package list, dams forgot sfml for Mageia 1 :)

Advisory:
-------------
The package virtualboyadvance (no more maintained) is available in Mandriva
2010.x but was missing in Mageia 1 and 2 (so upgrades were broken). This update
fixes this issue by providing vbam (fork of Virtualboyadvance) to Mageia
distributions. This package provides virtualboyadvance and obsoletes it.

Packages:
-------------
vbam-1.8.0-0.svn1103.1.mga1 (package of vbam for Mageia 1)
sfml-1.6-2.mga1 (needed to build vbam, so please import at the same time)
gtkglextmm-1.2.0-1.mga1 (needed to build vbam, so please import at the same
time)

vbam-1.8.0-0.svn1103.1.mga2 (package of vbam for Mageia 2)
sfml-1.6-2.mga2 (needed to build vbam, so please import at the same time)

How to test:
-------------
- Just try vbam check it works.
/!\ you will need a Game Boy rom file.

Which I thought was bad, was it have updated the RPM to 4.9. Then when I went to install the necessary programs to marshal, had to install all of the testing repository.
Other than that, it ran normally.

Question: How do I be a marshaler Mageia official? I know package, but do not know how to upload to the repository.

Is running normally, as we can see in the screenshot.

http://www.zimagez.com/zimage/capturadetela-31-08-2012-125358.php

http://www.imagebam.com/image/656357208568309

Also running here (Yoshi's Island)

Works with a SpeedLink Strike 2 (PSX Style pad, recognised as a generic Green Asia pad) and a SpeedLink 360 Style pad.

@ Michael and Simon

Could you please say whether you tested on i586 or x86_64. It needs to be tested on both to be able to validate the update so it can be pushed.

Thanks

(In reply to comment #34)
> @ Michael and Simon
> 
> Could you please say whether you tested on i586 or x86_64. It needs to be
> tested on both to be able to validate the update so it can be pushed.
> 
> Thanks

I'm on x86_64 and Mageia 2 with a Phenon II x6 (Over-clocked to 3.6Ghz) and a Radeon HD 6770 1GB, Ram is 16GB

i586, Mageia 2 with Intel Atom, 2Gb RAM

Great so testing is complete on mga2, thanks. 

It just needs testing on Mageia 1 now, then it can be pushed as an update.

Whiteboard: MGA1TOO MGA2-64-OK => MGA1TOO MGA2-64-OK mga3-32-OK

I'll see if I can install Mageia 1 on a machine here for testing. For now do a test on virtualbox.

Virtualbox is fine Michael, thanks.

It needs testing i586 and x86_64 there too, the same as mga2.

Testing complete on Mageia 1 i586 and x86-64.

Without a rom file to test with, I can only test that the
packages install cleanly, and the programs vbam and gvbam
run without failing.  Given the low risk, if the programs
do fail, I think that's sufficient for this update.

Could someone from the sysadmin team push the srpms
vbam-1.8.0-0.svn1103.1.1.mga2.src.rpm
sfml-1.6-2.mga2.src.rpm
from Mageia 2 Core Updates Testing to Core Updates and
push the srpms
vbam-1.8.0-0.svn1103.1.1.mga1.src.rpm
sfml-1.6-2.mga1.src.rpm
from Mageia 1 Core Updates Testing to Core Updates.

Advisory: This update adds vbam, A Game Boy emulator, and sfml,
a C++ multimedia API, which were available in Mandriva 2010.2,
but missing from Mageia.

https://bugs.mageia.org/show_bug.cgi?id=6807

Keywords: (none) => validated_update
CC: (none) => davidwhodgins, sysadmin-bugs
Whiteboard: MGA1TOO MGA2-64-OK mga2-32-OK => MGA1TOO MGA2-64-OK mga2-32-OK MGA1-32-OK MGA1-64-OK

It still segfaults on my computer in both i586 and x86_64 for Mageia 1. This seems to me a valid reason to not validate the update as is. We need at least to know where the problem comes from so that we can decide whether we push or notregardless of the segfault.

Also, why remove the feedback keyword?

Keywords: validated_update => (none)
Whiteboard: MGA1TOO MGA2-64-OK mga2-32-OK MGA1-32-OK MGA1-64-OK => MGA1TOO MGA2-64-OK mga2-32-OK MGA1-32-OK MGA1-64-OK feedback

Confirmed stormi's segfault (mga1 64 nvidia-current)

(gdb) run
Starting program: /usr/bin/vbam 
[Thread debugging using libthread_db enabled]
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-system.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-audio.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-graphics.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-network.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libsfml-window.so.1.6.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/usr/lib64/libstdc++.so.6.0.14.debug
warning: no loadable sections found in added symbol-file /usr/lib/debug/lib64/libgcc_s-4.5.2.so.1.debug

Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff68f9935 in ?? () from /usr/lib64/nvidia-current/libGL.so.1
#2  0x00007ffff68f2f0b in ?? () from /usr/lib64/nvidia-current/libGL.so.1
#3  0x00007ffff68e3c69 in glXGetConfig () from /usr/lib64/nvidia-current/libGL.so.1
#4  0x00007ffff6e04ae3 in sf::priv::WindowImplX11::CreateContext(sf::VideoMode const&, XVisualInfo&, sf::WindowSettings&, XVisualInfo, unsigned long) ()
   from /usr/lib64/libsfml-window.so.1.6
#5  0x00007ffff6e06c92 in sf::priv::WindowImplX11::WindowImplX11() () from /usr/lib64/libsfml-window.so.1.6
#6  0x00007ffff6e0263a in sf::priv::WindowImpl::New() () from /usr/lib64/libsfml-window.so.1.6
#7  0x00007ffff6e02519 in sf::Context::Context() () from /usr/lib64/libsfml-window.so.1.6
#8  0x00007ffff6e025a5 in sf::Context::GetGlobal() () from /usr/lib64/libsfml-window.so.1.6
#9  0x00007ffff6e02609 in global constructors keyed to Context.cpp () from /usr/lib64/libsfml-window.so.1.6
#10 0x00007ffff6e06ed6 in __do_global_ctors_aux () from /usr/lib64/libsfml-window.so.1.6
#11 0x00007ffff6dff553 in _init () from /usr/lib64/libsfml-window.so.1.6
#12 0x00007fffffffe0d8 in ?? ()
#13 0x00007ffff7ded719 in call_init (l=0x7ffff7fe34f0, argc=-150957952, argv=0x7fffffffe0c8, env=0x7fffffffe0d8) at dl-init.c:70
#14 0x00007ffff7ded857 in _dl_init (main_map=0x7ffff7ffe188, argc=1, argv=0x7fffffffe0c8, env=0x7fffffffe0d8) at dl-init.c:134
#15 0x00007ffff7de0aca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#16 0x0000000000000001 in ?? ()
#17 0x00007fffffffe3f7 in ?? ()
#18 0x0000000000000000 in ?? ()

Looks like the problem only happens with nvidia.  On my ati+fglrx system,
it doesn't segfault.

(In reply to comment #43)
> Looks like the problem only happens with nvidia.  On my ati+fglrx system,
> it doesn't segfault.

And only in 1.
Stormi, MrsB: did you tried with "nouveau" in 1 and with "nvidia" in 2?

I tried only with nvidia drivers.

Been playing with this the past few months and still no crashing on ATI + OSS Radeon mesa driver. Looks like it is an nVidia problem?

Summary: [Update Request] vbam - A GameBoy Advance emulator [mga2] => [Update Request] vbam - A GameBoy Advance emulator [mga1, mga2]

Validating as the segfault preventing push was on mga1 which is not now supported.

Advisory:
-------------
The package virtualboyadvance (no more maintained) is available in Mandriva
2010.x but was missing in Mageia 1 and 2 (so upgrades were broken). This update
fixes this issue by providing vbam (fork of Virtualboyadvance) to Mageia
distributions. This package provides virtualboyadvance and obsoletes it.

Packages:
-------------

vbam-1.8.0-0.svn1103.1.mga2 (package of vbam for Mageia 2)
sfml-1.6-2.mga2 (needed to build vbam, so please import at the same time)

Could sysadmin please push to updates.

Thanks!

Keywords: (none) => validated_update
Summary: [Update Request] vbam - A GameBoy Advance emulator [mga1, mga2] => [Update Request] vbam - A GameBoy Advance emulator [mga2]
Whiteboard: MGA2-64-OK mga2-32-OK MGA1-32-OK MGA1-64-OK feedback => MGA2-64-OK mga2-32-OK MGA1-32-OK MGA1-64-OK

Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0238

Status: ASSIGNED => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED