denemo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Denemo-devel] [bug #26515] /dev/dsp stuck open, other sound not working


From: anonymous
Subject: [Denemo-devel] [bug #26515] /dev/dsp stuck open, other sound not working, after 'play back entered notes immediately'
Date: Sun, 10 May 2009 07:41:57 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.10) Gecko/2009042513 Ubuntu/8.04 (hardy) Firefox/3.0.10

URL:
  <http://savannah.gnu.org/bugs/?26515>

                 Summary: /dev/dsp stuck open, other sound not working, after
'play back entered notes immediately'
                 Project: GNU Denemo, a gtk+ frontend to GNU Lilypond
            Submitted by: None
            Submitted on: Sun 10 May 2009 07:41:56 AM UTC
                Category: None
                Severity: 3 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Hello all,

I'm running Denemo 0.8.4 on Ubuntu Hardy (gnome), with pulseaudio, without
jack or lash.  I'm new to Denemo and so far I'm really thrilled with it, so a
big thanks to everyone who's worked on it!

The one problem I'm having is with playing notes as they're entered.  The
notes play fine, but after that Denemo will not play the normal midi output,
and other sound on my system will not work until I close Denemo.

I get this message in my syslog:
pulseaudio[5935]: module-alsa-sink.c: Error opening PCM device front:0:
Device or resource busy

And while the problem is occurring, lsof shows:
denemo    13256   blahblah    6r      CHR       14,3             11891
/dev/dsp

The sequencer device in Denemo is the default /dev/sequencer, which I do have
on my machine.

I've tried running as an ordinary user and as root with no difference.  I
also tried launching Denemo with pasuspender, but that didn't help either.

I'm getting this behavior with two laptops, so it's not specific to the
hardware.  However, they're configured quite similarly as far as the software
goes.

Can someone help me out with this?  Is there just a setting somewhere I'm
missing?  I keep thinking this must have an obvious solution.

Let me know what additional information I should supply.

Thanks,

Victoria




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26515>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]