Ubuntu 8.04 -- Sound: Rhythmbox blocks Skype

Bug #236283 reported by pinguino
2
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Incomplete
Undecided
Elliot Hughes

Bug Description

Hi,

when I am using Rhythmbox and I get a call with Skype. The person, who call, get a message on the screen that my audio is not working and I can't heard nothing when I get a call but I can see on the screen that somebody call me.
Thanks

Regards

pinguino

Revision history for this message
Elliot Hughes (elliot-hughes) wrote :

Hi,
To help you with this bug I will need to know whether you experience this difficulty when using other media players with Skype, this is so I can make a decision over which package this would be best reported against.

Thanks for your bug report,
Elliot

Revision history for this message
pinguino (pcboard) wrote :
Download full text (17.8 KiB)

Hi,

Thanks for your answer. I can only report this situation. Rhythmbox with Skype. When I try to answer the skype call Skype crash. So I must to call the person again without Rhythmbox.
I was looking for a similar bug here and there are similar behavors in some threads.

I have found one on the net:

http://www.linuxquestions.org/questions/fedora-35/sound-conflict-between-skype-and-xmmsrhythmbox-600347/

http://www.wlug.org.nz/UbuntuNotes

http://ubuntuforums.org/showthread.php?t=785159

*****************************************************

My computer data:

http://www.nethands.de/pys/show.php4?user=pinguino

********************************************************

lspci

00:00.0 Host bridge: Intel Corporation 82845 845 [Brookdale] Chipset Host Bridge (rev 11)
00:01.0 PCI bridge: Intel Corporation 82845 845 [Brookdale] Chipset AGP Bridge (rev 11)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 82)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 420 Go] (rev a3)
02:07.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link)
02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
02:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 32)
02:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 32)
02:0d.0 System peripheral: Toshiba America Info Systems SD TypA Controller (rev 03)
03:00.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)

*************************************************************************

lshw

pinguino
    description: Notebook
    product: Portable PC
    vendor: TOSHIBA
    version: Version 1.0
    serial: 0000000000
    width: 32 bits
    capabilities: smbios-2.3 dmi-2.3
    configuration: administrator_password=disabled boot=normal chassis=notebook frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled
  *-core
       description: Motherboard
       product: Portable PC
       vendor: TOSHIBA
       physical id: 0
       version: Version A0
       serial: 0000000000
     *-firmware
          description: BIOS
          vendor: TOSHIBA
          physical id: 0
          version: Version 1.50 (01/13/2005)
       ...

Revision history for this message
Elliot Hughes (elliot-hughes) wrote :

Thanks for the update - if you can get me a crash log as soon as possible I can confirm this for you.

Elliot

Revision history for this message
Elliot Hughes (elliot-hughes) wrote :

Hi,
It's nearly one week since your last communication. It would be brilliant if you could get back to me with crash logs as soon as you are next available.

Revision history for this message
pinguino (pcboard) wrote :

Hi,

Thanks for your comments. I have got a Skype call at 19:37 and the calling person tell me again that I have a problem with the sound because she get a skype message which it says: " My sound device has a problem"
I found the following lines under /var/log/syslog:

Jun 6 19:35:58 pinguino -- MARK --
Jun 6 19:44:02 pinguino pulseaudio[5636]: module-alsa-sink.c: Error opening PCM device front:0: Device or resource busy
Jun 6 19:55:58 pinguino -- MARK --
Jun 6 20:01:05 pinguino pulseaudio[5636]: module-alsa-sink.c: Error opening PCM device front:0: Device or resource busy

but I am not sure if this lines are the problem because I have seen the time and it was 19:37. Is it possible a difference between the hardware clock and the system clock in this case?

Do you know, where I can find another logs for Skype or Rhythmbox specially?

Thanks a lot

Regards

pinguino

Revision history for this message
Elliot Hughes (elliot-hughes) wrote : Error logs

Its unlikely that Rhythmbox will show errors as by the looks of things
its blocking the sound device. However try running both apps from a
terminal to see output.
E.g $ rhythmbox > rhythmboxlog.txt
Or
$ rhythmbox
By itself

Revision history for this message
pinguino (pcboard) wrote :

Hi,

I have started both programs and after that I have tried to make a call. On the terminal window from Skype (opened 2 terminal windows for each program) show me:

ALSA lib pcm_dmix.c:874:(snd_pcm_dmix_open) unable to open slave

and on the GUI from Skype I can see " Problem with the audio"

Revision history for this message
Elliot Hughes (elliot-hughes) wrote :

Thanks for your work reporting this bug - it appears this bug is actually a duplicate of the bug #198453 - luckily there are a few possible workaround with that bug for you.

Thanks alot,

Elliot

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.