@Colin:
Are there any differences to /usr/bin/aoss and /usr/bin/padsp and any preference? Probably padsp should be used ...

CC: (none) => doktor5000, mageia

@Florian. Actually neither should be used directly in .desktop files. We generally prefer to use "soundwrapper" which will run the correct program for you.

In actual fact, these days, osspd is preferred over any kind of LD_PRELOAD hacks. osspd uses cuse (character device fuse). Basically the userspace component (rather than kernel) will crate the /dev/dsp (and friends) character devices and a daemon listens on it and will proxy the data appropriately to either PulseAudio or Alsa. This approach has several advantages over the previous systems so for legacy sound I'd always recommend that.

If osspd is used, you don't actually have to do anything to the .desktop file, but you should probably still use soundwrapper as it can know whether or not osspd is in use and simple be a no-op if it is or defer to padsp or aoss as appropriate otherwise.

Updated .desktop file to Exec=soundwrapper k4guitune

- k4guitune-1.1.1-6.2.mga5
- k4guitune-1.1.1-8.mga6

Please test.

CC: (none) => yann.cantin

Thanks Yann. When pushing an update candidate, please assign the bug report to the QA team (qa-bugs@ml.mageia.org) and provide an advisory [1] that describes what the update does in plain English (intended for end users).

[1] https://wiki.mageia.org/en/Update_Advisory_Announcement_Example

Uploaded patched package for Mageia 5 and Cauldron.

The application should start when launched via menu now, please test.

Advisory:
========================

Use soundwrapper in k4guitune desktop file.

========================

Updated packages in core/updates_testing:
========================
k4guitune-1.1.1-6.2.mga5
k4guitune-1.1.1-8.mga6

From source RPMs:
k4guitune-1.1.1-6.2.mga5.src.rpm
k4guitune-1.1.1-8.mga6.src.rpm

Assignee: bugsquad => qa-bugs
Whiteboard: (none) => advisory

tested in MGA5 42Bit VBox: installation works: soundwrapper will be installed as dependency and K4guitune starts now from menu. 
It does not not get any sound input, however it seems that it is due to the virtual machine, since pavucontrol shows no input sound as well. Will try tomorrow on real hw.

This bug is listed for Mageia 4 rather than Mageia 5. Can this be corrected? (I prefer not to do it since it is not 'my' bug; and I may be wrong).

@Marc
There has been a lot of talk about sound not working with some Mageia host/guest combinations under VirtualBox.

Version: 4 => 3
CC: (none) => lewyssmith

I've changed the version to 5 and added MGA4TOO to the whiteboard since there is no indication that the bug has been fixed in mga4.

I've also removed the advisory keyword since I don't think the advisory has been uploaded yet to SVN.

Version: 4 => 5
Hardware: x86_64 => All
Whiteboard: advisory => MGA4TOO

Uploaded patched package for Mageia 4, Mageia 5 and Cauldron.

The application should start when launched via menu now, please test.

New advisory:
========================

Use soundwrapper in k4guitune desktop file.

========================

Updated packages in core/updates_testing:
========================
k4guitune-1.1.1-4.1.mga4
k4guitune-1.1.1-6.2.mga5
k4guitune-1.1.1-8.mga6

From source RPMs:
k4guitune-1.1.1-4.1.mga4.src.rpm
k4guitune-1.1.1-6.2.mga5.src.rpm
k4guitune-1.1.1-8.mga6.src.rpm

Tested it on real hw MGA5 64bit and have only partially success. 
First I checked the KDE menu and the entry in exec is: soundwrapper k4guitune %i -caption "%c" 

It starts from the menu, but does not get any input from microphone by default. When trying to change the Sample frequency at Configuration --> Audio Device the program crashes with error message from #1
- starting it from Konsole --> same error message as above and it does not start.
- starting it with 'aoss k4guitune' from konsole everything works. 

to be honest: I'm not sure if it is worth fiddling around, since I (and probably no one else?) do not use this prog. I only stumbled upon it by chance last year...
But if you want to, I'm always happy to test it :)

Adding feedback whiteboard marker, because of mixed testing results.

Whiteboard: MGA4TOO => MGA4TOO feedback

mga5 64 LANG=fr_FR.UTF-8
VT8237A/VT8251 HDA Controller

Installed :
soundwrapper-1.7-5.mga5
pulseaudio-5.0-6.mga5

k4guitune-1.1.1-6.2.mga5.x86_64.rpm

No mic attached.

Starts from the menu or console : not getting input at first.
Settings --> Configure k4guitune --> Audio Device --> change Sample frequency :
got some signal (obviously electronic noise).

Update OK for me.

Whiteboard: MGA4TOO feedback => MGA4TOO feedback MGA5-64-OK

Why does this have the feedback marker?  I see an OK for Mageia 5 and nothing that indicates that something is different on Mageia 4.

OK, we discussed on IRC and the Comment 10 issue indicates that it isn't working with Pulseaudio.  Perhaps it could work with it if you fiddled with some settings.  Disabling Pulseaudio or running osspd should make this work fine with soundwrapper.  Disabling Pulseaudio will cause soundwrapper to call aoss, and osspd will have it just run it directly which should work too.  This is something we can cycle back to and see how we want to handle things going forward for Mageia 6.  Feel free to file a bug if you deem it necessary.  I've confirmed that the soundwrapper was also correctly added to the menu entry for Mageia 4, so validating this now.

New advisory:
========================

The k4guitine application uses the OSS sound API, therefore the menu entry to
launch the program needed to use soundwrapper, which it previously did not.
This has been corrected in this update.

Keywords: Junior_job => validated_update
Whiteboard: MGA4TOO feedback MGA5-64-OK => MGA4TOO MGA5-64-OK MGA4-32-OK
CC: (none) => sysadmin-bugs

Advisory uploaded.

Whiteboard: MGA4TOO MGA5-64-OK MGA4-32-OK => MGA4TOO advisory MGA5-64-OK MGA4-32-OK

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0126.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED