<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Failure to open sound /dev/dsp problem (new mystery with old problem)</title>
    <link>http://communities.vmware.com/community/vmtn/archive/desktop/player?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Wed, 10 May 2006 05:16:37 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2006-05-10T05:16:37Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Failure to open sound /dev/dsp problem (solved)</title>
      <link>http://communities.vmware.com/message/397317?tstart=0#397317</link>
      <description>I finally resolved the problem, and it had nothing to do with the VMWare Player.  Actually there were a number of overlapping issues; if you are a Linux user getting /dev/dsp errors, look for my post at one of the SuSE user forums.  You may need to do more than just the following, as I did:&lt;br /&gt;
&lt;br /&gt;
Basically, use #lsof /dev/snd/* and #fuser /dev/snd/* to determine what programs have *these* sound files open.  In my case, because I had turned on KDE's desktop icon preview feature for audio files, the kdesktop program had opened these files; it pipes its preview back through /dev/dsp.  Other processes can do the same.  They need to be killed to free /dev/dsp.  There is a good chance that simply executing as root - #/etc/init.d/alsasound restart - will take care of it for you.&lt;br /&gt;
&lt;br /&gt;
Message was edited by: &lt;br /&gt;
        mingus</description>
      <pubDate>Wed, 10 May 2006 05:15:12 GMT</pubDate>
      <author>mingus</author>
      <guid>http://communities.vmware.com/message/397317?tstart=0#397317</guid>
      <dc:date>2006-05-10T05:15:12Z</dc:date>
      <clearspace:dateToText>3 years, 6 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Failure to open sound /dev/dsp problem (new mystery with old problem)</title>
      <link>http://communities.vmware.com/message/394500?tstart=0#394500</link>
      <description>No.  As indicated above, unable to replicate the problem on my other box (primary sw diff being the default kernel, whereas this box uses the smp).  I had a backup SuSE install on my main box hdb; I blew that away yesterday and reinstalled SuSE fresh, which means back to unpatched kernel and KDE 3.4.  This time I didn't install arts.  I'm gonna install the VMWare and try a controlled restoration to the state on hda, and see if I can trap what change is locking up dsp.&lt;br /&gt;
&lt;br /&gt;
Can you associate when the problem began with any other change to your system?</description>
      <pubDate>Thu, 04 May 2006 14:21:51 GMT</pubDate>
      <author>mingus</author>
      <guid>http://communities.vmware.com/message/394500?tstart=0#394500</guid>
      <dc:date>2006-05-04T14:21:51Z</dc:date>
      <clearspace:dateToText>3 years, 6 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Failure to open sound /dev/dsp problem (new mystery with old problem)</title>
      <link>http://communities.vmware.com/message/391905?tstart=0#391905</link>
      <description>Mingus,&lt;br /&gt;
Did you ever find a resolution for this. My SUSE10/Workstation 5.5 system is exhibiting the exact same behavior.</description>
      <pubDate>Sat, 29 Apr 2006 04:37:28 GMT</pubDate>
      <author>Keith_Reed</author>
      <guid>http://communities.vmware.com/message/391905?tstart=0#391905</guid>
      <dc:date>2006-04-29T04:37:28Z</dc:date>
      <clearspace:dateToText>3 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Failure to open sound /dev/dsp problem (new mystery with old problem)</title>
      <link>http://communities.vmware.com/message/385975?tstart=0#385975</link>
      <description>Sure.  Sorry if that wasn't clear - no problem with sound on the KDE host running as user.&lt;br /&gt;
&lt;br /&gt;
Message was edited by: &lt;br /&gt;
        mingus</description>
      <pubDate>Mon, 17 Apr 2006 13:33:43 GMT</pubDate>
      <author>mingus</author>
      <guid>http://communities.vmware.com/message/385975?tstart=0#385975</guid>
      <dc:date>2006-04-17T13:33:43Z</dc:date>
      <clearspace:dateToText>3 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Failure to open sound /dev/dsp problem (new mystery with old problem)</title>
      <link>http://communities.vmware.com/message/385966?tstart=0#385966</link>
      <description>Does the sound device actually work in KDE with a non-root account - that is, can you play sound with something like XMMS?</description>
      <pubDate>Mon, 17 Apr 2006 13:17:31 GMT</pubDate>
      <author>nick.couchman</author>
      <guid>http://communities.vmware.com/message/385966?tstart=0#385966</guid>
      <dc:date>2006-04-17T13:17:31Z</dc:date>
      <clearspace:dateToText>3 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Failure to open sound /dev/dsp problem (new mystery with old problem)</title>
      <link>http://communities.vmware.com/message/385465?tstart=0#385465</link>
      <description>There have been a lot of posts with this particular problem, with a variety of causes.  I have discovered something on my system that I haven't seen referred to in any other post, perhaps there is a clue here that can help others besides myself . . .&lt;br /&gt;
&lt;br /&gt;
Error msg:  "Failure to open sound device /dev/dsp.  Device or resource busy"   Most suggestions are that the problem is either with (a) arts or esd, or (b) a conflicting application tieing up /dev/dsp.&lt;br /&gt;
&lt;br /&gt;
What I have discovered is that the problem is somehow connected to something that is happening running KDE as a user but not as root.  If I open a single session as root, there is no error running vmplayer.  If I open two root sessions, there is no conflict.  However, if I open a session as the user, then a second session as root and run the player in the root session, I encounter the error.  Or if in the user session I run vmplayer with root priviledge, I also get the error.  &lt;br /&gt;
&lt;br /&gt;
So it looks as if something is running under the user session that ties up /dev/dsp, right?  But I can't find what it is . . . &lt;br /&gt;
&lt;br /&gt;
#fuser /dev/dsp* shows no process using the device&lt;br /&gt;
#lsof | grep dsp shows no process opening the file&lt;br /&gt;
changing all KDE sound settings incl turning audio I/O or sound system off - no effect&lt;br /&gt;
assigning user to all groups, including giving the user root priviledge - no effect&lt;br /&gt;
changing the .vmdk and related file permissions - no effect&lt;br /&gt;
changing the .vmx file sound statements - no effect&lt;br /&gt;
changing permissions to /dev/dsp - no effect&lt;br /&gt;
&lt;br /&gt;
I killed every user process, except the minimum required by KDE (kdeinit, kded, kwin, kdesud, kicker, kdesktop, ksmserver, startkde &amp;#38; kwrapper [under kdm], dbus, dcopserver) - no effect&lt;br /&gt;
&lt;br /&gt;
I should add that when I first installed the player on SuSE 10.0 with KDE 3.4, worked fine.  Also works fine on my other box, SuSE 10.0 and KDE 3.5.1 (although not the smp kernel).  I just updated my primary box to 3.5.2, no help.  &lt;br /&gt;
&lt;br /&gt;
I did not try the vmwaredsp-1.3.tar.gz fix because (a) I saw anothe post indicating it does not work with KDE 3.5 and (b) I don't know how to back it out if it borks something.&lt;br /&gt;
&lt;br /&gt;
I'm stuck.  Can any of you experts help???&lt;br /&gt;
&lt;br /&gt;
Thanks in advance.&lt;br /&gt;
&lt;br /&gt;
mingus&lt;br /&gt;
VMWare Player (build 19317), SuSE 10.0, KDE 3.5.2, 2.6.13-15.8-smp</description>
      <pubDate>Fri, 14 Apr 2006 21:23:48 GMT</pubDate>
      <author>mingus</author>
      <guid>http://communities.vmware.com/message/385465?tstart=0#385465</guid>
      <dc:date>2006-04-14T21:23:48Z</dc:date>
      <clearspace:dateToText>3 years, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
  </channel>
</rss>

