Slackware upgrade to 9.0.188 – lost sound

Forum / NoMachine for Linux / Slackware upgrade to 9.0.188 – lost sound

Tagged: 

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #53091
    EddieA
    Participant

    Upgraded my Slackware 15.0 server and Windows 11 client from 8.16.1 -> 9.0.188.  Following this, I’m not getting any sound at the Windows side from the Slackware server.

    A similarly upgraded Windows 7 server is passing the sound through to Windows 11 client correctly.

    #53190
    jakdud1
    Participant

    Hello

    We’ve tried to reproduce your issue in our labs using the configuration you provided, but we haven’t encountered any problems on our end.
    Could you please try opening the application via your terminal and let us know if the issue still persists? To open the player from the command line, run /usr/NX/bin/nxplayer.

    Regards,
    Jakub

    #53202
    EddieA
    Participant

    Not sure what “configuration” you’re referring to as all I’ve provided was the post above.

    Also not sure exactly what you’re asking me to run.  The server is running on the Slackware side and I’m connecting to it via the Windows UI.  Where does the Linux version of nxplayer fit into this ?

    #53212
    jakdud1
    Participant

    A little follow-up. For the Windows systems the path to the player’s binary file should be something more like this:
    C:\Program Files\NoMachine\bin\nxplayer.exe

    Sorry, I just confused ‘the version’, the path I provided is obviously the Linux one. My fault 🙂

    Regards,
    Jakub

    #53246
    DM85
    Participant

    Similar problem.

    After upgrading to version 9.0.188 on Ubuntu Server 24.04.2 LTS, the sound disappeared both on the client running Windows and Linux Ubuntu.

    The problem persists if you run the client as described in post #53212 and #53190.

    #53248
    EddieA
    Participant

    No, sorry still the same.  I get the sounds from a Windows 7 VM, but not the Slackware VM.

    #53264
    SimpleTechGuy
    Participant

    Not sure if this is relevant, but one of the guys over in the aur was having audio problems on linux and found that: “For people encountering no sound in NoMachine after upgrade to Pulseaudio 17.0, Pulseaudio needs to be rebuild to add the module-esound-sink”

    https://aur.archlinux.org/packages/nomachine#comment-1014435

    #53310
    DM85
    Participant

    There were no updates to PulseAudio. Only the server and client parts of NoMachine were updated, after which the sound disappeared. However, after rebuilding PulseAudio with the modulecouldsink module, the problem remained (in Ubuntu 24.0.4.2 LTS). Is there a solution to the problem at the moment or wait for the NoMachine update?

    #53339
    SimpleTechGuy
    Participant

    My use case is a bit different from you guys, since I’m using linux for the player, but I was having issues with sound initially as well.  I am using pipewire on my server instead of pulseaudio, so the module option didn’t apply to me. If you did try the module-esound-sink and it didn’t work, then I would recommend that you remove that module since it is recommended to not use that unless you have to as it can lead to other problems for other things!
    https://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modules/#module-esound-sink

    I am using pulseaudio on the player side, but yesterday Arch put out a few updates on the server side, one of them being Pipewire 1:1.4.5-1, and now everything is working fine.

    You can check if your linux machine is using PipeWire or PulseAudio by running the command <code class=”qlv4I7skMF6Meluz0u8c wZ4JdaHxSAhGy1HoNVja _dJ357tkKXSh_Sup5xdW”>pactl info in the terminal. If it shows “Server Name: PulseAudio (on PipeWire…)”, then PipeWire is in use; otherwise, if it only mentions PulseAudio, then it is using PulseAudio.

    The steps I took were to to install all updates, reboot, rebuild and reinstall the newest version of NoMachine (make sure you rebuild it and not just reinstall it).  Make sure to do this on both client and server side.  (on windows just uninstall, reboot, then reinstall).  Make sure you have a backup of your connections just in case.  This is basically what I did and now everything is working for me, including a different issue I was having that was causing a core dump.

    Also, as another side note (and I’m only saying this because I’ve done this many times and always forget about it), make sure you didn’t disable sound in the connection settings lol…

    Good luck, hope this helps!

    #53343
    jakdud1
    Participant

    Hi All,

    Providing logs from both the client and server sides of your NoMachine session on PulseAudio would be incredibly helpful for our diagnosis.

    You can find detailed instructions on how to gather them here: https://kb.nomachine.com/DT07S00243

    Please send them to forum[at]nomachine[dot]com, making sure to reference the topic as the subject of the email.

    Regards,

    Jakub

    #53411
    mckaygerhard
    Participant

    Hi there is no need of send logs. NoMachine team just have to check changes in how pulseaudio its detected no matter if pipewire or pulseaudio case..

    This affects all NoMachine 9 and last NoMachine 8.16, older NoMachine version just works without problem

    • pipewire with pulseaudio emulation
    • and pulseaudio

    by example in this clien log line we got:

    AudioIoPulseaudioServer: WARNING! Cannot connect to PulseAudio server.
    AudioIoPulseaudioServer: Failed to get devices list.

    This line will be present in all your connections if you use NoMachine 9 but not if you use NoMachine 8 as client

    I tested NoMachine 9 in older Debians, older Arch and newer ones and always same problem.. failed to get device list where pulseaudio setup is assumed.

     

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic. Please login .