SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Could I possibly ask for a bit of advice in troubleshooting a problem with sound in wine? My problem is with sound in Diablo 3, in short there is none.
I have Slackware-current installed, converted to multilib using slackpkg+. I believe the multilib is upto date (even if the kernel(4.4.6 installed) and some other packages aren't), alsa packages also seem to be up to date as well. I installed wine-1.8-x86_64 from AlienBob's repo and it seems to be working fine. When in winecfg I can use the "Test Sound" button and I can hear a sound.
But when I start Diablo 3 I can get no sound from it.
I am attaching the output from when I run Diablo 3. diablo.wine.out.txt
I have searched for similar problems but what I have found on the net seems to be resolving sound issues in wine in general which it seems I don't have as sound tests in winecfg are successful.
Please advise if more info is needed to help with this.
Make sure you have all the dependencies installed required by pulseaudio (assuming you are using it). I had this issue not long ago where some multilib packages were missing, it affected different games, but could be the same problem: https://www.linuxquestions.org/quest...nt-4175571745/
Diablo 3 is working fine, thank you. I get over 25fps on my rig and around 30fps with eyecandy set to lowest values.
My kernel is 4.4.6, I haven't upgraded it. I have made an ISO from -current a while back(when the kernel was at 4.4.6) and made a clean install, since I was putting a new SSD drive in and changing to UEFI boot this seemed the easiest solution. Only /home and a custom configs from /etc have been reused. Since then I have only been updating some packages and left the kernel untouched. I do realise that I am a little behind the current -current, but the alsa and pulseaudio packages are up to date.
This is my .asoundrc,
Code:
[trenton@stormik]$ cat .asoundrc
pcm.pulse {
type pulse
}
ctl.pulse {
type pulse
}
pcm.!default {
type pulse
}
ctl.!default {
type pulse
}
I believe AlienBob has advised this file is no longer needed since inclusion of Pulseaudio in Slackware but to help apps that might require it it should be setup as above(please correct me if this is wrong).
The command "aplay -l" gives the following output:
And yes, I get sound when playing flash videos in Firefox, I get sound in Kodi and mplayer. Thanks to Pulseaudio I can hear these streams simultaneously, something I couldn't achieve with alsa before(maybe I just lacked time to research and configure it properly). And the only frustration now is the lack of sound in Diablo 3.
Thanks
Last edited by jimtrenton; 05-23-2016 at 03:22 AM.
Reason: Corrected reason for the clean install
If you're only partially upgrading your packages that could be the cause of your issue. Packages are built off of each other and, many times, require the versions they were built against to run properly. Diablo 3 may be accessing something that is linking to an old version of pulse or alsa, which could cause your audio to not function.
Have you checked with ldd to see if it's missing any libraries (not that this is conclusive, but if it dumps errors, then they need to get fixed).
Maybe it'd be worth giving Slackware Live Edition[1] a go (a live Slackware version developed by Alien Bob, based on the latest -current release).
[1] Also known as liveslak or Slacklive -- I'm not positive on the name since I've seen several iterations. However, I'm leaning towards liveslak referring to the scripts and Slackware Live Edition as the released ISOs.
If you're only partially upgrading your packages that could be the cause of your issue. Packages are built off of each other and, many times, require the versions they were built against to run properly. Diablo 3 may be accessing something that is linking to an old version of pulse or alsa, which could cause your audio to not function.
Have you checked with ldd to see if it's missing any libraries (not that this is conclusive, but if it dumps errors, then they need to get fixed).
Maybe it'd be worth giving Slackware Live Edition[1] a go (a live Slackware version developed by Alien Bob, based on the latest -current release).
[1] Also known as liveslak or Slacklive -- I'm not positive on the name since I've seen several iterations. However, I'm leaning towards liveslak referring to the scripts and Slackware Live Edition as the released ISOs.
The collection of scripts to create the ISOs is called "liveslak". The resulting ISO will boot "Slackware Live Edition". There is no such thing as "Slacklive".
@slackartist: Thanks. I have seen that page before(the whole site is an often read), but my understanding is that the info there is to help troubleshoot general sound issues in Slackware. I've used that info in the past to configure my alsa setup. But one of the reasons for the reinstall was to have an out-of-the-box install of Pulseaudio and it's working great for everything other than this Diablo install.
@bassmadrigal:I know that upgrading only some of the packages is not always good but after reviewing the possible upgrades, I decided there was nothing I urgently needed. The essential parts of the system, in the form of the multilib, are up to date and I believe that is enough for the core to be considered up to date. I can't check with the 'ldd' as in the meantime I have found the solution to my particular problem.
I have somehow missed the following error in the output I have attached in the first post:
The poster of the same error advises that the issues has been resolved by recompiling Wine.
As my first wine package was installed from AlienBob's awesome packages repository, I thought it should not be an issue but still decided to recompile my own wine package from ponce's SlackBuild for the current branch.
And this proves that building stuff directly on the destination system makes all the difference.
After recompiling Wine and reinstalling Diablo 3 all works great.
Thanks for all the help and suggestions. Time to mark this as SOLVED.
The collection of scripts to create the ISOs is called "liveslak". The resulting ISO will boot "Slackware Live Edition". There is no such thing as "Slacklive".
slackware.uk has it mirrored under alien-slacklive/, so that's probably where my confusion started.
But thanks for confirming my theory on the naming!
Quote:
Originally Posted by jimtrenton
As my first wine package was installed from AlienBob's awesome packages repository, I thought it should not be an issue but still decided to recompile my own wine package from ponce's SlackBuild for the current branch.
And this proves that building stuff directly on the destination system makes all the difference.
After recompiling Wine and reinstalling Diablo 3 all works great.
Glad you got this fixed. I wonder if Eric's wine package was referencing newer libraries than what was on your system, causing the problem. Recompiling it would've fixed that as they would've been built against the older libraries on your system.
Anyway, I'm glad you got it working, and thanks for sharing the solution!
I wonder if Eric's wine package was referencing newer libraries than what was on your system, causing the problem. Recompiling it would've fixed that as they would've been built against the older libraries on your system.
Actually I am thinking that the wine package for slackware-current in my repository is fairly old (30 Dec 2015) whereas PulsAudio was added to Slackware-current on 13 Jan 2016 - two weeks later. Perhaps if I compile a new Wine package, and it picks up PulseAudio, the OP's problem will disappear.
Actually I am thinking that the wine package for slackware-current in my repository is fairly old (30 Dec 2015) whereas PulsAudio was added to Slackware-current on 13 Jan 2016 - two weeks later. Perhaps if I compile a new Wine package, and it picks up PulseAudio, the OP's problem will disappear.
That makes sense as well. Guess I should've looked at the date of your wine package before I assumed it was referencing newer libraries that weren't on OP's computer.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.