[Bug 881695] Re: Xoscope doesn't work on soundcard (No valid data sources found... exiting)

[Adam Conrad]

Upload to oneiric-proposed sponsored (identical to the precise upload,
modulo the version number), waiting in the unapproved queue.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/881695

Title:
  Xoscope doesn't work on soundcard (No valid data sources found...
  exiting)

Status in “xoscope” package in Ubuntu:
  Fix Released
Status in “xoscope” source package in Oneiric:
  Triaged

Bug description:
  Starting xoscope gives always the error.

   No valid data sources found... exiting

  I think the problem is located in the changed behavior in /dev/dsp.
  Launching with padsp -d shows:

  utils/padsp.c: dsp_open()
  utils/padsp.c: fd_info_new()
  utils/padsp.c: dsp_open() succeeded, fd=8
  utils/padsp.c: unknown ioctl 0xffffffffc0045006
  utils/padsp.c: freeing fd info (fd=8)
  utils/padsp.c: Draining.
  No valid data sources found... exiting

  xoscope version is 2.0-3.1ubuntu1 on ubuntu 11.10

  [Impact]
  Xoscope doesn't work at all on 64 bit architecture. The only way to make it work, is to execute on 32 bit arch only with padsp (raw dsp device was disabled in Ubuntu). The software was conceived to use raw dsp audio as fallback mechanism, but in this case, it is the only way to make it work whit a soundcard. On 64 bit arch, due to the wrong ioctl parameter, it does not work at all, nor with esd (disabled at compile time) nor with padsp.

  [Development Fix]
  The fix use unsigned integer to call the ioctl, calling it the right way. This solve the padsp bug. Patch enables also the esd support by adding libesd0-dev to the compiler dependency. In this way, xoscope can work as it was conceived, using the soundcard via libraries instead accessing the raw device (/dev/dsp). The patch also set the defaut client mode to record, instead of monitor, it works better in pulseaudio. This change is not desruptive because the option could be changed at runtime using a menu inside the software. The only modified package is xoscope upgraded to version 2.0-3.1ubuntu2.

  [Stable Fix]
  Patch accepted for the development fix it applicabile also at the stable one, because the package was at the same version number before the patch was accepted.

  [Test Case]
  To reproduce the bug (32 and 64 bits arch):
  1) Open xoscope from the commandline.
  2) the software cannot find nor the /dev/dsp nor the esd soundcard so it fails whit the error: "No valid data sources found... exiting"

  On 32 bits arch:
  1) Open the software from commandline with "padsp xoscope"
  2) the software works as expected using the virtual /dev/dsp provided by padsp

  On 64 bits arch:
  1) Open the software from commandline with "padsp xoscope"
  2) Software doesn't work and prints the output "No valid data sources found... exiting"
  3) starting the software with "padsp -d xoscope" prints the output:
  utils/padsp.c: dsp_open()
  utils/padsp.c: fd_info_new()
  utils/padsp.c: dsp_open() succeeded, fd=8
  utils/padsp.c: unknown ioctl 0xffffffffc0045006
  utils/padsp.c: freeing fd info (fd=8)
  utils/padsp.c: Draining.
  No valid data sources found... exiting

  Please note the wrong ioctl integer (0xffffffffc0045006, it should be
  0xc0045006) .

  [Regression Potential]
  I think there are no regressions here because the patch changes only an unisigned integer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xoscope/+bug/881695/+subscriptions