[Bug 42311] New: winecfg can't detect Wine's own Pulseaudio driver
https://bugs.winehq.org/show_bug.cgi?id=42311 Bug ID: 42311 Summary: winecfg can't detect Wine's own Pulseaudio driver Product: Wine Version: 2.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 0xe2.0x9a.0x9b(a)gmail.com Distribution: --- Output from Gentoo Linux's package manager: $ qlist wine | grep pulse /usr/lib64/wine/winepulse.drv.so /usr/lib64/wine/fakedlls/winepulse.drv /usr/lib32/wine/winepulse.drv.so /usr/lib32/wine/fakedlls/winepulse.drv Removing *.reg from $HOME/.wine/ has no effect on the issue. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P1 CC| |0xe2.0x9a.0x9b(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 --- Comment #1 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> --- Created attachment 57049 --> https://bugs.winehq.org/attachment.cgi?id=57049 winecfg screenshot -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 --- Comment #2 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> --- Created attachment 57050 --> https://bugs.winehq.org/attachment.cgi?id=57050 Build log (gzip compressed) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #3 from winetest(a)luukku.com --- Similar/dupe to bug 39524. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de --- Comment #4 from Sebastian Lackner <sebastian(a)fds-team.de> --- Based on your log the winepulse driver is compiled correctly. Does sound output work with other applications? Could you attach a log with WINEDEBUG=+tid,+seh,+mmdevapi,+winmm,+driver,+msacm,+midi,+dsound,+dsound3d,+xaudio2,+xapofx,+dmusic,+mci,+pulse,+oss,+alsa,+coreaudio,+timestamp ? Take a look here if you need additional information how to do that: https://wiki.winehq.org/FAQ#How_do_I_get_a_debug_trace.3F -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 --- Comment #5 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> --- (In reply to Sebastian Lackner from comment #4)
Based on your log the winepulse driver is compiled correctly.
Does sound output work with other applications?
Non-wine application: yes
Could you attach a log with WINEDEBUG=+tid,+seh,+mmdevapi,+winmm,+driver,+msacm,+midi,+dsound,+dsound3d, +xaudio2,+xapofx,+dmusic,+mci,+pulse,+oss,+alsa,+coreaudio,+timestamp ?
Take a look here if you need additional information how to do that: https://wiki.winehq.org/FAQ#How_do_I_get_a_debug_trace.3F
$ cd .wine $ rm -f *.reg $ ls dosdevices drive_c $ WINEDEBUG=... winecfg &>> winecfg.log $ ls dosdevices drive_c system.reg user.reg $ grep -i pulse *.reg (no match) The contents of drive_c are NOT being deleted by me when switching Wine versions. After executing the following code: $ rm -rf $HOME/.wine $ winecfg winecfg reports that Wine is using winepulse.drv This means that the cause of this bug is related to Wine updates. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 --- Comment #6 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> --- Created attachment 57059 --> https://bugs.winehq.org/attachment.cgi?id=57059 winecfg.log -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal --- Comment #7 from Bruno Jesus <00cpxxx(a)gmail.com> --- Looks weird: 95.883:0014:trace:driver:DRIVER_TryOpenDriver32 Unable to load 32 bit module L"msacm.imaadpcm": Not a 32 bit lib It repeats for every codec. Can you redo the log with the same channels plus +loaddll? Can you test in a clean prefix? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 --- Comment #8 from Alexandre Julliard <julliard(a)winehq.org> --- (In reply to Jan Ziak (http://atom-symbol.net) from comment #5)
$ cd .wine $ rm -f *.reg
You should never do that. The registry won't be re-created to match the contents of the C drive, you'll just get a broken prefix. If you want a fresh prefix you have to remove the entire directory. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED --- Comment #9 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> --- After thinking about what actually happened in the beginning, a real issue appears to be the fact that Wine configuration updater (first Wine launch after the update from 1.9.23-staging to 2.0, or after deleting ~/wine/.update-timestamp) is taking unexpectedly long time to complete - about 1 minute - without consuming any CPU time. The user can get the impression that the updater hang and kills it by SIGTERM/SIGKILL. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 --- Comment #10 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> --- Created attachment 57062 --> https://bugs.winehq.org/attachment.cgi?id=57062 Screenshot: Wine configuration updater -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #11 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42311 --- Comment #12 from Jan Ziak (http://atom-symbol.net) <0xe2.0x9a.0x9b(a)gmail.com> --- (In reply to Austin English from comment #11)
Closing.
Ok. But are you sure that the issue described in comment 9 has been resolved? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org