https://bugs.winehq.org/show_bug.cgi?id=49874
Bug ID: 49874 Summary: audio devices not showing up in windows application Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: endzone102@gmail.com Distribution: ---
Created attachment 68215 --> https://bugs.winehq.org/attachment.cgi?id=68215 foobar2000 debug output
I am trying to set up the foobar2000 audio player in Wine. Everything looks more or less OK, *except* that no audio devices are being found. The only thing I'm getting in the option box is "Null" which tells me that it's not finding the audio devices.
winecfg shows that I'm using pulse, and I've tried using "(system default)", "pulseaudio", AND "built-in audio" devices, all to no avail. I have also tried setting the application to use Windows 7, Windows 10, and Windows XP, all also to no avail. Test sound does work.
I'm running Fedora 32 on an Asus Q524U laptop.
$ uname -a Linux localhost.localdomain 5.8.9-200.fc32.x86_64 #1 SMP Mon Sep 14 18:28:45 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Attached is the log file that results from:
$ WINDEBUG=+tid,+seh,+mmdevapi,+winmm,+driver,+msacm,+midi,+dsound,+dsound3d,+xaudio2,+xapofx,+dmusic,+mci,+pulse,+oss,+alsa,+coreaudio,+timestamp wine ./foobar2000.exe >> /tmp/foobar_wine_debug.txt 2>&1
I'm doing this with foobar2000 1.6 Beta 10.
https://bugs.winehq.org/show_bug.cgi?id=49874
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #1 from joaopa jeremielapuree@yahoo.fr --- Where is the option box in foobar to choose the audio driver?
link for download https://www.foobar2000.org/getfile/1ccd1c1c8005157748ade6d295443c24/foobar20...
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #2 from Greg G endzone102@gmail.com ---
It's under File->Preferences->Playback->Output
It's the "Device" dropdown at the top of that page.
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #3 from joaopa jeremielapuree@yahoo.fr --- Created attachment 68218 --> https://bugs.winehq.org/attachment.cgi?id=68218 screenshot showing everything is fine
Working fine for me. Be sure you are the rights for the audio device
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #4 from Greg G endzone102@gmail.com --- Hmmm. How would I check that? I'm able to use sounds as me on the host with no problems. I try not to run Wine as root.
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #5 from joaopa jeremielapuree@yahoo.fr --- You must not use wine as root...
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #6 from joaopa jeremielapuree@yahoo.fr --- Did you test your application in a fresh wine prefix?
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #7 from joaopa jeremielapuree@yahoo.fr --- An check you installed the 32 bits version of all your pulseaudio packages.
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #8 from Greg G endzone102@gmail.com --- I did. Several times. I tried using winetricks to make a new prefix, I tried removing all of ~/.wine Made no difference.
I suspect I am having some weird permission problem, as after running some OS updates and rebooting, I can no longer even run wine at all. I am opening a new ticket for that issue, and will then come back to this one.
Here's what I have installed for pulse:
Installed Packages alsa-plugins-pulseaudio.x86_64 1.2.2-1.fc32 @anaconda pulseaudio.x86_64 13.99.1-4.fc32 @updates pulseaudio-libs.i686 13.99.1-4.fc32 @updates pulseaudio-libs.x86_64 13.99.1-4.fc32 @updates pulseaudio-libs-glib2.x86_64 13.99.1-4.fc32 @updates pulseaudio-module-bluetooth.x86_64 13.99.1-4.fc32 @updates pulseaudio-module-x11.x86_64 13.99.1-4.fc32 @updates pulseaudio-utils.x86_64 13.99.1-4.fc32 @updates wine-pulseaudio.i686 5.16-1.fc32 @updates wine-pulseaudio.x86_64 5.16-1.fc32 @updates
I'm not sure why I should need the 32-bit versions (since foobar is a 64bit application, at least on Windows), and, if I do, why I'm not getting a warning message somewhere along the line.
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #9 from joaopa jeremielapuree@yahoo.fr --- Wine is a 32-bit software although it can run 64 bit applications.
https://bugs.winehq.org/show_bug.cgi?id=49874
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- The debug otuput attached is very strange. In particular these messages:
0208:err:ole:CoGetClassObject class {00000320-0000-0000-c000-000000000046} not registered
and
0208:err:ole:CoGetClassObject class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
should not happen, and imply that somehow the prefix was corrupted or not completely set up.
Do these messages appear on a newly created prefix? If so, can you post complete console output from the prefix creation?
(In reply to joaopa from comment #9)
Wine is a 32-bit software although it can run 64 bit applications.
To be more accurate, wine has 32-bit and 64-bit components, which are necessary to run 32-bit and 64-bit applications respectively, and which respectively depend on 32-bit and 64-bit support libraries.
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #11 from Greg G endzone102@gmail.com --- Right now, I can't run any part of wine. I opened https://bugs.winehq.org/show_bug.cgi?id=49875 for that. :headwall:
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #12 from Greg G endzone102@yahoo.com ---
As far as I can tell, this was an unfortunate clash with some of Fedora's updates.
I've got it working fine now.
I'm unable to close this ticket. I guess either INVALID or NOTOURBUG would be appropriate.
https://bugs.winehq.org/show_bug.cgi?id=49874
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #13 from Zebediah Figura z.figura12@gmail.com --- (In reply to Greg G from comment #12)
As far as I can tell, this was an unfortunate clash with some of Fedora's updates.
I've got it working fine now.
I'm unable to close this ticket. I guess either INVALID or NOTOURBUG would be appropriate.
You should be able to modify your own tickets, but anyway, marking invalid.
https://bugs.winehq.org/show_bug.cgi?id=49874
--- Comment #14 from Austin English austinenglish@gmail.com --- Closing.
https://bugs.winehq.org/show_bug.cgi?id=49874
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Austin English austinenglish@gmail.com --- Closing.