[CBLX] et pour Debian alors ? Fwd:SoundTroubleshootingProcedure - Community Ubuntu Documentation

[ Thread Index | Date Index | More lists.tuxfamily.org/carrefourblinux Archives ]


Hello les audiophiles,

l'info que j'ai dénichée sur le net concernant le blème de son bcp trop
faible en sortie parle d'Ubuntu; OK, c utile et en + ça prouve que y a un 
gros problème, et à voir les distribs auxquelles cette URL réfère ça ne date 
même pas d'hier....... 

Donc logique qq part que je tombe moi aussi sur ce "même?" problème en 
installant une Deb Squeeze toute fraîche; c bien ce que je pensais: le
problème n'est pas lié à l'une ou l'autre distrib spécifique, mais donc
quasi tout le monde possédant un chipset intel hda doit potentiellement
rencontrer ce souci ?!
 
Bien; du coup ma question est simple: 
et sous une Debian Squeeze on fais quoi ?
vu que les urls ppa d'Ubuntu ne sont en aucun cas
intervertibles/partageables, comment procéder pour résoudre cela ?

Et au fait, pourquoi Debian Squeeze sensée être stable ils publient 
quand-même une version buguée à ce point d'ALSA/Pulse avec la release ?

Enfin, n'y a-t-il pas moyen de supprimer complètement Pulse pour n'utiliser
sous Debian QUE ALSA ? Sous Ubuntu la doc propose de supprimer puis
réinstaller alsa-base et alsa-utils; es-ce possible de simuler cette
possible solution sous Deb; si oui comment ?
Je suppose qu'il faut alors des alsa-base et alsa-utils d'un autre répo, 
lequel ?
 
Fwd: 
SoundTroubleshootingProcedure - Community Ubuntu Documentation
X-URL: https://help.ubuntu.com/community/SoundTroubleshootingProcedure

   #[1]Start [2]Wikiopmaak [3]Afdrukvoorbeeld [4]Search [5]Index
   [6]Glossary [7]Help

[8]Ubuntu

   [9]________________________ [10]Search
   [11][help-faq.png] Community Documentation
     * [12]Login to Edit

   [13]Ubuntu Documentation > [14]Community Documentation >
   [15]SoundTroubleshootingProcedure
     * [16]SoundTroubleshootingProcedure

   Inhoud
    1. [17]Step 1
    2. [18]Step 2
    3. [19]Step 3
    4. [20]Step 4
    5. [21]Step 5
    6. [22]Step 6
    7. [23]Step 7
    8. [24]Step 8
    9. [25]Step 9
   10. [26]Step 10
   11. [27]Step 11
   12. [28]Step 12
   13. [29]Step 13
   14. [30]Step 14
   15. [31]Step 15
   16. [32]Step 16
   17. [33]Step 17
   18. [34]Other Useful Information to Quote
   19. [35]OSS4 for low performance CPU's
         1. [36]For Ubuntu 10.04
         2. [37]For Ubuntu 10.10
   20. [38]External Links

   Follow his procedure to gather essential troubleshooting information
   about your sound card. This information will be useful in posting a
   question to launchpad:
     * [39]https://answers.launchpad.net/ubuntu/+addquestion

Step 1

   If you are using Ubuntu 11.04 (Natty), then simply skip this step.

   If you are using Ubuntu 10.10 (Maverick), then execute this command and
   reboot:

sudo add-apt-repository ppa:ricotz/unstable; sudo apt-get update; sudo apt-get
--reinstall install alsa-base alsa-utils

   If you are using Ubuntu 10.04 (Lucid), use [40]this link

   If you are using Ubuntu 9.10 (Karmic), then you should upgrade to
   Ubuntu 10.04.2 LTS or newer versions. End of life date for Ubuntu 9.10
   was April 2011.

Step 2

   If you are using the Gnome interface, open [41]the Terminal console via
   "Applications->Accessories->Terminal"

   If you are using the Unity interface, the easiest way to open the
   Terminal is to use the 'search' function on the dash. Or you can click
   on the 'More Apps' button, click on the 'See more results' by the
   installed section, and find it in that list of applications. A third
   way, available after you click on the 'More Apps' button, is to go to
   the search bar, and see that the far right end of it says 'All
   Applications'. You then click on that, and you'll see the full list.
   Then you can go to Accessories > Terminal after that.

   So the methods in Unity are:

   Dash > Search for Terminal

   Dash > More Apps > 'See More Results' > Terminal

   Dash > More Apps > Accessories > Terminal

   In gnome-terminal, make sure that unlimited scrolling is enabled:
     * click on Edit > Profiles > "Default" profile > Scrolling. Choose
       "Unlimited" as scrolling option. Click Close and Close again.

Step 3

   Reboot your computer. Then run the following 2 diagnostic commands.

   Tip: If you have a wheel mouse or 3-button mouse, you do not need to
   type the commands into the Terminal. Instead, copy the commands from
   this web page and paste them into the terminal. To do this, move your
   mouse cursor over the start of the command written on the Web page.
   Then press the left mouse button and drag the mouse till the end of the
   command to highlight the whole command; then release the mouse button.
   Then press the middle mouse button or mouse wheel anywhere inside the
   Terminal. The command should now be printed in the Terminal without
   errors. Now press <Enter> to execute the command.

wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh

bash alsa-info.sh --stdout

   Post the full Terminal output after the script has actually run by
   [42]creating a new question in launchpad then copy&paste the terminal
   output into your newly created question. Carefully inspect the Terminal
   output of the ALSA Information script that was generated by the
   previous diagnostic command
bash alsa-info.sh --stdout

   After upgrading ALSA and rebooting the computer make sure that the ALSA
   driver version, library version and utilities version are all exactly
   the same version number.

   The Terminal output after running the ALSA information script should
   contain something like this:

   # ALSA Version

   # Driver version: 1.0.23

   # Library version: 1.0.23

   # Utilities version: 1.0.23

   If the Driver, Library and Utilities version numbers are not equal,
   this probably due to one of the following issues:

   1. One of the ALSA components was not successfully upgraded during step
   1 in this procedure

   2. ALSA was correctly installed or upgraded, but a wrong / old kernel
   was booted instead of the most recent kernel version. In that case,
   boot the newest kernel version (that is available in the
   standard/default Ubuntu repositories) and then retest sound.

   For example: if you installed or upgraded to Ubuntu 10.10 (Maverick
   Meerkat edition), make sure the running kernel version is
   2.6.35-22-generic or higher. Or else sound will not work!

   For example: if you installed or upgraded to Ubuntu 10.04 (Lucid Lynx
   edition), make sure the running kernel version is 2.6.32-21-generic or
   higher. Or else sound will not work!

   For example: if you installed or upgraded to Ubuntu 9.10 (Karmic Koala
   edition), make sure the running kernel version is 2.6.31-14-generic or
   higher. Or else sound will not work!

Step 4

   Copy & paste the following diagnostic command into the Linux Terminal,
   then press <Enter>. The command starts with the command cat and ends
   with the word sound. (Do not copy & paste this diagnostic command from
   an email message into the Terminal, as that will only copy part of the
   command.) When asked for your password, type your normal user password
   (no stars are given as you type); then press <Enter> again.

   Tip: If you have a wheel mouse or 3-button mouse, you do not need to
   type the commands into the Terminal. Instead, copy the commands from
   this web page and paste them into the terminal. To do this, move your
   mouse cursor over the start of the command written on the Web page.
   Then press the left mouse button and drag the mouse till the end of the
   command to highlight the whole command; then release the mouse button.
   Then press the middle mouse button or mouse wheel anywhere inside the
   Terminal. The command should now be printed in the Terminal without
   errors. Now press <Enter> to execute the command.

cat /proc/asound/{version,cards,devices,hwdep,pcm,seq/clients}; sudo rm /etc/as
ound.conf; sudo rm -r ~/.pulse ~/.asound* ;sudo rm ~/.pulse-cookie; sudo apt-ge
t update; sudo apt-get install aptitude; sudo aptitude install paman gnome-alsa
mixer libasound2-plugins padevchooser libsdl1.2debian-pulseaudio; sudo lshw -sh
ort;ls -lart /dev/snd;  cat /dev/sndstat; lspci -nn;  sudo which alsactl; sudo
fuser -v /dev/dsp /dev/snd/* ; dpkg -S bin/slmodemd; dmesg | egrep 'EMU|probe|e
mu|ALSA|alsa|ac97|udi|snd|ound|irmware'; sudo /etc/init.d/sl-modem-daemon statu
s; sudo grep model /etc/modprobe.d/* ; sudo dmidecode|egrep 'Manufact|Product';
 lsmod | egrep 'snd|usb|midi|udio'; aplay -l; sudo lshw -C sound

   !!! Post the full Terminal output into the original question that you
   previously created at answers.launchpad.net

   !!! Also mention how you want to generate sound output: analog output
   via desktop speakers, digital output via an HDMI connection to the TV,
   via headphones, etc ...

Step 5

   Reboot and retest sound using the headphones and the speakers. Do not
   run a Gnome session in "Gnome Failsafe" mode; speakers are disabled in
   "Gnome Failsafe" mode.

   !!! After rebooting, verify that you have posted the full Terminal
   output from step 3 and step 4 into the original question that you
   previously created at answers.launchpad.net

   !!! Also mention how you want to generate sound output: analog output
   via desktop speakers, digital output via an HDMI connection to the TV,
   via headphones, etc ...

Step 6

   Run the following command in a Terminal:

pavucontrol

   In this application - [43]PulseAudio Volume Control - switch to the
   "Playback" tab and increase System sounds volume to 100%

Step 7

   Run the following command in a Terminal:

gnome-alsamixer

   In this application, make sure to set all channels to high volume
   levels. Make sure the different speakers (especially 'Front', 'Master',
   and 'PCM") are NOT muted and NOT set to low volume levels in
   gnome-alsamixer.

   On some Toshiba laptop models (T40, T43p, ... R51e ...), the audio is
   muted, if either Headphone or Line Jack are NOT muted in alsamixer. See
   also ALSA Wiki FAQ [1]. Also, if Headphone Sense or Line Jack Sense are
   unmuted, audio is dead (R52, X40). By default the Sense settings are
   not shown in GNOME. A channel is muted in alsamixer, if there is an
   "MM" under that specific channel/volume bar.

   On some Toshiba laptop models, setting the PCM channel volume higher
   than 70% in alsamixer, may result in clipping (for example: very
   "harsh" and distorted sound both on the internal speakers and on
   headphones plug), regardless of the Master channel.

   [44]Problem with audio clipping

   HP Laptops in the dv5, dv6, dv7 series and some HP Mini netbook
   computers have a strange problem in Ubuntu. When you plug in the
   headphones, you will hear sound via the headphones and speakers at the
   same time. The following link should provide a workaround for that
   issue:

   [45]Problem with headphones

   On the HP Compaq nx8220, you can solve the simultaneous
   speaker/headphone output issue by enabling the Headphone Jack Sense
   option in the gnome-alsamixer application.

Step 8

   Report if you cannot hear sound through the speakers, the headphones or
   cannot hear sound on both.

Step 9

   If you are using a dual boot system (even with Windows and Ubuntu
   installed on separate partitions), then make sure to set the sound
   volume in Windows to a high level before booting into Ubuntu. Also make
   sure to use the special function keys in Windows to make sure the
   loudspeakers are physically switched ON and working properly in Windows
   before installing and testing Ubuntu. This step is necessary with
   certain Toshiba Tecra laptops.

Step 10

   In System/Administration/Users and Groups, make sure that your normal
   user and the root user are members of the following 5 groups:

   pulse

   pulse-access

   pulse-rt

   audio

   video

Step 11

   Run the command gnome-volume-control and set the Sound Theme to "No
   sounds". The Sound Theme tool is also accessible via System >
   Preferences > Sound

Step 12

   Try connecting headphones to different audio jacks/ports on the
   back-panel of the sound-card until you hopefully hear sound

Step 13

   In the BIOS, reset the BIOS values to default values.

   If you happen to have two sound-cards installed in your pc, one
   integrated into the motherboard - for example: an hda-intel audiochip -
   and one inserted into a PCI slot, then try removing the PCI audio card,
   reboot your pc and retest sound using only the motherboard's on-board
   audio chip.

   If you absolutely need to get the PCI audio card working, try disabling
   the motherboard's on-board audio chip via the BIOS. Then retest sound
   in Ubuntu.

   Save the change in the BIOS and reboot.

Step 14

   If ALSA is still not loading any driver for your soundcard (for
   example: a Soundblaster Audigy PCI card) after upgrading to the newest
   version of ALSA, try reseating the PCI audio card into a different PCI
   slot on your PC's motherboard.

Step 15

   Specify the exact model and make of your PC (if possible) in the new
   thread that you created at Launchpad Answers Forum.

Step 16

   If you want to enable S/PDIF audio output, then unmute and increase
   volume on the S/PDIF and S/PDIF playback channels in the alsamixer
   application. Use the M key to toggle between muted (MM) and unmuted
   (00) states.

   Alternative way to enable SPDIF output automatically on login (tested
   on SoundBlaster Audigy): add following lines to /etc/rc.local:

 # Use COAX-digital output
 amixer set 'IEC958 Optical' 100 unmute
 amixer set 'Audigy Analog/Digital Output Jack' on

   You can see the name of your card's digital output with:

amixer scontrols

   If the optical/coaxial digital output of your motherboard/sound card is
   not working or stopped working, and you have already enabled and
   unmuted it in alsamixer, run
sudo iecset audio on

   You can also put this command in /etc/rc.local , as it may stop working
   after a reboot.

Step 17

   If the HDMI output of your motherboard/sound card is not working or
   stopped working, and have already enabled and unmuted it in alsamixer,
   try the following procedure:

   [46]https://answers.launchpad.net/ubuntu/+question/139924

   Query for Playback Devices:

aplay -l
     * *** List of PLAYBACK Hardware Devices **** card 0: NVidia [HDA
       NVidia], device 0: ALC1200 Analog [ALC1200 Analog]
          + Subdevices: 1/1 Subdevice #0: subdevice #0
       card 0: NVidia [HDA NVidia], device 1: ALC1200 Digital [ALC1200
       Digital]
          + Subdevices: 1/1 Subdevice #0: subdevice #0
       card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
          + Subdevices: 0/1 Subdevice #0: subdevice #0

   Now that we have the info for the HDMI device, try a test, In the
   example below, 0 is the card number and 3 is the device number.

aplay -D plughw:0,3 /usr/share/sounds/alsa/Front_Center.wav

   If aplay does not output any errors, but still no sound is heared,
   "reboot" the receiver, monitor or tv set. Since the HDMI interface
   executes a handshake on connection, it might have noticed before that
   there was no audio stream embedded, and disabled audio decoding.

   If the test is successful, edit/create /etc/asound.conf to set HDMI as
   the default audio device, reboot, and audio should now work. (Is there
   a better way to do this?)

cat /etc/asound.conf
     * pcm.!default {
          + type plug slave.pcm {
               o type hw card 0 device 3
            }
       }
     __________________________________________________________________

Other Useful Information to Quote

   The following string needs to be added to the
   /etc/modprobe.d/alsa-base.conf file
options snd-hda-intel model=YOUR_MODEL

   Valid model names (that replace YOUR_MODEL) depending on the codec
   chip, can be found in "[47]HD-Audio-Models ALSA documentation".

   You can find your audio CODEC chip name by running this Terminal
   command:
cat /proc/asound/car*/co* |  grep Codec

   Please try the following command instead, if the previous command does
   not show the audio CODEC chip name:
cat /proc/asound/car*/co*/* |  head

   You can find your audio MIXER name by running this Terminal command:
cd ~; wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh ; bash alsa
-info.sh --stdout |grep "ixer name"

   You can find your audio DEVICE name by running this Terminal command:
lspci -nn|egrep 'ultimedia|udio|sound|AC97|ac97|EMU'

   Each combination of audio codec, audio mixer and audio device name
   requires a very specific configuration in the alsa-base.conf file, if
   the audio chipset does not work out-of-the-box.

   To see if there is more than one alsactl executable in your path and to
   remove the wrong/oldest one, copy&paste the following command into a
   Terminal and press the <enter> key:
sudo which alsactl

   Having more than one alsactl can cause your sound settings to be muted
   during every boot of the Ubuntu system.

   To understand the various hda_intel related errors that might be
   mentioned at the end of the ALSA Information script output that was
   uploaded to the Pastebin website, read the following documentation:

   [48]HD-Audio documentation
     __________________________________________________________________

OSS4 for low performance CPU's

   How to replace Alsa with OSS4 to improve sound quality on low
   performance CPU's

   !!! WARNING: Only try installing OSS4 as a LAST resort if ALL the
   previous steps did not help resolve your sound output issues using the
   ALSA sound system! Installing OSS4 should only be attempted by people
   who know what they are doing and are very experienced with using Linux
   systems.

   Do not try to fix audio if it is not broken when using ALSA and
   [49]PulseAudio...

   Many applications use the OSS API for sound because it is
   well-documented and portable across several platforms (Linux, Solaris,
   BSD, etc).

For Ubuntu 10.04

   If you want to use OSS4 instead of ALSA in Ubuntu 10.04, follow the
   procedure here:

   [50]OSS4 guide for Ubuntu 10.04

For Ubuntu 10.10

   If you want to use OSS4 instead of ALSA in Ubuntu 10.10, follow the
   procedure here:

   [51]OSS4 guide for Ubuntu 10.10
     __________________________________________________________________

External Links

   For some initial suggestions, also read the following pages

   * [52]https://help.ubuntu.com/community/SurroundSound

   * [53]http://ubuntuguide.org/wiki/Ubuntu:Maverick#Sound

   *
   [54]http://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architectu
   re

   *
   [55]http://drowninginbugs.blogspot.com/2009/10/caveats-for-audio-in-910
   .html

   * [56]https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats

   *
   [57]http://ubuntuforums.org/showthread.php?t=789578&highlight=audacity

   * [58]http://ubuntuforums.org/showthread.php?t=205449

   *
   [59]http://www.ubuntugeek.com/sound-solutions-for-ubuntu-904-jaunty-use
   rs.html

   * [60]https://help.ubuntu.com/community/SoundTroubleshooting

   !!! Check for correct /etc/modprobe.d/alsa-base.conf options on the
   following pages:

   * [61]http://ubuntuforums.org/showthread.php?t=1043568

   * [62]http://doc.ubuntu-fr.org/audio_intel_hda

   *
   [63]http://www.mjmwired.net/kernel/Documentation/sound/alsa/HD-Audio-Mo
   dels.txt

   *
   [64]http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-karmic.git;a=blob_plai
   n;f=Documentation/sound/alsa/ALSA-Configuration.txt
     __________________________________________________________________

   [65]CategoryAudio

   SoundTroubleshootingProcedure (laatst bewerkt op 2011-05-15 10:04:18
   door [66]Mark Rijckenberg)
     * [67]Page History
     __________________________________________________________________

   The material on this wiki is available under a free license, see
   [68]Copyright / License for details
   You can contribute to this wiki, see [69]Wiki Guide for details

References

   1. https://help.ubuntu.com/community/UserDocumentation
   2. https://help.ubuntu.com/community/SoundTroubleshootingProcedure?action=raw
   3. https://help.ubuntu.com/community/SoundTroubleshootingProcedure?action=print
   4. https://help.ubuntu.com/community/FindPage
   5. https://help.ubuntu.com/community/TitleIndex
   6. https://help.ubuntu.com/community/WordIndex
   7. https://help.ubuntu.com/community/HelpOnFormatting
   8. http://help.ubuntu.com/
   9. form field = text entry field
  10. form field = submit button
  11. https://help.ubuntu.com/community
  12. https://help.ubuntu.com/community/SoundTroubleshootingProcedure?action=login
  13. https://help.ubuntu.com/
  14. https://help.ubuntu.com/community
  15. https://help.ubuntu.com/community/SoundTroubleshootingProcedure?action=fullsearch&context=180&value=linkto%3A%22SoundTroubleshootingProcedure%22
  16. https://help.ubuntu.com/community/SoundTroubleshootingProcedure?action=fullsearch&context=180&value=linkto%3A%22SoundTroubleshootingProcedure%22
  17. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 1
  18. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 2
  19. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 3
  20. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 4
  21. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 5
  22. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 6
  23. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 7
  24. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 8
  25. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 9
  26. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 10
  27. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 11
  28. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 12
  29. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 13
  30. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 14
  31. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 15
  32. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 16
  33. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Step 17
  34. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#Other Useful Information to Quote
  35. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#OSS4 for low performance CPU's
  36. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#For Ubuntu 10.04
  37. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#For Ubuntu 10.10
  38. https://help.ubuntu.com/community/SoundTroubleshootingProcedure#External Links
  39. https://answers.launchpad.net/ubuntu/+addquestion
  40. http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-lucid-lynx-10-04/
  41. https://help.ubuntu.com/community/UsingTheTerminal#Starting%20a%20Terminal
  42. https://answers.launchpad.net/ubuntu/+addquestion
  43. https://help.ubuntu.com/community/PulseAudio
  44. http://www.thinkwiki.org/wiki/Problem_with_audio_clipping
  45. http://digitizor.com/2009/10/22/fix-headphone-sound-problem-hp-laptop-linux/
  46. https://answers.launchpad.net/ubuntu/+question/139924
  47. http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio-Models.txt
  48. http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio.txt
  49. https://help.ubuntu.com/community/PulseAudio
  50. http://www.ubuntugeek.com/howto-install-oss4-in-ubuntu-10-04-lucid-for-better-sound-quality.html
  51. http://ubuntuforums.org/showthread.php?t=1594215
  52. https://help.ubuntu.com/community/SurroundSound
  53. http://ubuntuguide.org/wiki/Ubuntu:Maverick#Sound
  54. http://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture
  55. http://drowninginbugs.blogspot.com/2009/10/caveats-for-audio-in-910.html
  56. https://wiki.ubuntu.com/DebuggingSoundProblems/KarmicCaveats
  57. http://ubuntuforums.org/showthread.php?t=789578&highlight=audacity
  58. http://ubuntuforums.org/showthread.php?t=205449
  59. http://www.ubuntugeek.com/sound-solutions-for-ubuntu-904-jaunty-users.html
  60. https://help.ubuntu.com/community/SoundTroubleshooting
  61. http://ubuntuforums.org/showthread.php?t=1043568
  62. http://doc.ubuntu-fr.org/audio_intel_hda
  63. http://www.mjmwired.net/kernel/Documentation/sound/alsa/HD-Audio-Models.txt
  64. http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-karmic.git;a=blob_plain;f=Documentation/sound/alsa/ALSA-Configuration.txt
  65. https://help.ubuntu.com/community/CategoryAudio
  66. https://launchpad.net/~markrijckenberg
  67. https://help.ubuntu.com/community/SoundTroubleshootingProcedure?action=info
  68. https://help.ubuntu.com/community/License
  69. https://help.ubuntu.com/community/WikiGuide

----- End forwarded message -----


 

---
-- 
   CarrefourBLinuX MailingListe 
   Pour obtenir de l'aide, envoyez le sujet  help  à: 
   carrefourblinux-request@xxxxxxxxxxxxxxxxxxx
   Archives: 
   http://listengine.tuxfamily.org/lists.tuxfamily.org/carrefourblinux


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/