http://bugs.winehq.org/show_bug.cgi?id=23384
Summary: Clicking on Audio Tab on Winecfg takes several seconds the first time Product: Wine Version: 1.2-rc5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: luisalvaradox@gmail.com
When you open winecfg and click on Audio, it will take several seconds for it to respond. About 5 to 6 seconds to respond. This was not the case in versions 1.2 rc3 and 1.2 rc4. You could click and see the Audio tab immediately.
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #1 from Austin English austinenglish@gmail.com 2010-06-26 15:01:53 --- Please run a regression test: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=23384
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |trivial
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2010-06-27 14:43:17 --- http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
http://bugs.winehq.org/show_bug.cgi?id=23384
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mstefani@redhat.com
--- Comment #3 from Michael Stefaniuc mstefani@redhat.com 2010-06-29 12:31:05 --- I cannot reproduce the problem with wine-1.2-rc5-37-gdb68b1e. I get the "There is no audio driver currently specified in the registry" popup window in less than a second. That was with a fresh WINEPREFIX. If I configure ALSA and retry again (stop/restart winecfg) the Audio tab shows up instantaneous.
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #4 from Luis Alvarado luisalvaradox@gmail.com 2010-06-29 14:06:07 --- Tested on 2 other PCs. Same result. a HP dv6000 and a Intel Dp35dp desktop pc. Both when you start winecfg and click on audio tab takes several seconds. You can close and open winecfg a million times and still it will take several seconds for the audio tab to appear.
Both of this PC were formatted and installed again with Ubuntu 10.04 32 bit. Added the ppa from wine and downloaded latest. Same problem.
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #5 from Michael Stefaniuc mstefani@redhat.com 2010-06-29 16:36:06 --- Luis, you'll have to run the regression test yourself as I cannot reproduce it on both my desktop and laptop; both run Fedora 13. On my desktop I have even 4 audio drivers compiled in (ALSA, OSS, ESD and JACK) and that takes max 1 second. Come to think of it: do you have by any change the NAS driver installed? That one is known for this type of delay.
http://bugs.winehq.org/show_bug.cgi?id=23384
Raymond superquad.vortex2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |superquad.vortex2@gmail.com
--- Comment #6 from Raymond superquad.vortex2@gmail.com 2010-07-01 02:03:04 --- (In reply to comment #5)
Luis, you'll have to run the regression test yourself as I cannot reproduce it on both my desktop and laptop; both run Fedora 13. On my desktop I have even 4 audio drivers compiled in (ALSA, OSS, ESD and JACK) and that takes max 1 second.
does the oss driver still work since oss emulation has been disabled since Fedora 11 and CUSE seem not enabled by default in Fedora 13 ?
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #7 from Luis Alvarado luisalvaradox@gmail.com 2010-07-02 23:56:37 --- Am using Ubuntu 10.04 32 Bit. Tested again both Pc, fresh install of ubuntu 10.04 and again same problem. Can you teach me how to do regression test am no expert on that subject yet.
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #8 from Raymond superquad.vortex2@gmail.com 2010-07-03 21:13:02 --- (In reply to comment #7)
Am using Ubuntu 10.04 32 Bit. Tested again both Pc, fresh install of ubuntu 10.04 and again same problem. Can you teach me how to do regression test am no expert on that subject yet.
As far as I notice , wine seem also calling JACK_WaveInit even when I did not enabled the Jack driver
WINEDEBUG=+wave wine winecfg
trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_LOAD (00000001), 00000000, 00000000) trace:jack:JACK_drvLoad () trace:jack:JACK_drvLoad SONAME_LIBJACK == libjack.so.0 trace:jack:JACK_drvLoad jackhandle == 0x7cb0f230 trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_ENABLE (00000002), 00000000, 00000000) trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_OPEN (00000003), 00000000, 00000000) trace:wave:JACK_wodMessage (0, 0064, 00000000, 00000000, 00000000); trace:wave:JACK_WaveInit called
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #9 from Luis Alvarado luisalvaradox@gmail.com 2010-07-04 10:42:52 --- (In reply to comment #8)
(In reply to comment #7)
Am using Ubuntu 10.04 32 Bit. Tested again both Pc, fresh install of ubuntu 10.04 and again same problem. Can you teach me how to do regression test am no expert on that subject yet.
As far as I notice , wine seem also calling JACK_WaveInit even when I did not enabled the Jack driver
WINEDEBUG=+wave wine winecfg
trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_LOAD (00000001), 00000000, 00000000) trace:jack:JACK_drvLoad () trace:jack:JACK_drvLoad SONAME_LIBJACK == libjack.so.0 trace:jack:JACK_drvLoad jackhandle == 0x7cb0f230 trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_ENABLE (00000002), 00000000, 00000000) trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_OPEN (00000003), 00000000, 00000000) trace:wave:JACK_wodMessage (0, 0064, 00000000, 00000000, 00000000); trace:wave:JACK_WaveInit called
Could this be the culprid?
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #10 from Raymond superquad.vortex2@gmail.com 2010-07-05 00:10:49 --- (In reply to comment #9)
(In reply to comment #8)
(In reply to comment #7)
Am using Ubuntu 10.04 32 Bit. Tested again both Pc, fresh install of ubuntu 10.04 and again same problem. Can you teach me how to do regression test am no expert on that subject yet.
As far as I notice , wine seem also calling JACK_WaveInit even when I did not enabled the Jack driver
WINEDEBUG=+wave wine winecfg
trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_LOAD (00000001), 00000000, 00000000) trace:jack:JACK_drvLoad () trace:jack:JACK_drvLoad SONAME_LIBJACK == libjack.so.0 trace:jack:JACK_drvLoad jackhandle == 0x7cb0f230 trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_ENABLE (00000002), 00000000, 00000000) trace:jack:JACK_DriverProc (00000000, 0x146248, DRV_OPEN (00000003), 00000000, 00000000) trace:wave:JACK_wodMessage (0, 0064, 00000000, 00000000, 00000000); trace:wave:JACK_WaveInit called
Could this be the culprid?
Even I unchecked ALSA driver , wine seem calling ALSA_ComputeCaps
WINEDEBUG=+alsa,+oss ./wine winecfg fixme:wave:ALSA_ComputeCaps Device has a minimum of 2 channels fixme:wave:ALSA_ComputeCaps Device has a minimum of 2 channels
This may mean that it will try to connect pulse server even if you disable ALSA driver and the default is configured to use pulse device by your distribution
The point is only alsa and oss driver support midi, the other drivers may not support midi
http://bugs.winehq.org/show_bug.cgi?id=23384
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #11 from Dan Kegel dank@kegel.com 2010-07-30 22:51:25 --- It always does this for me. configure --without-nas fixes it.
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #12 from Dan Kegel dank@kegel.com 2010-09-16 16:37:00 CDT --- Should we make --without-nas the default?
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #13 from Luis Alvarado luisalvaradox@gmail.com 2010-12-25 13:01:06 CST --- Still present as of 1.3.10
Install Wine, go to winecfg, select de Audio TAB, see how it lags for a couple of seconds.
http://bugs.winehq.org/show_bug.cgi?id=23384
--- Comment #14 from Raymond superquad.vortex2@gmail.com 2010-12-25 22:25:07 CST ---
It always does this for me. configure --without-nas fixes it.
(In reply to comment #12)
Should we make --without-nas the default?
I think you have to ask ubuntu maintainer since wine-alsa is not installed by default when you installed wine in fedora 10 or later (winepulse is default audio driver in their customised winecfg ) and they also removeed alsa oss emulation in Ubuntu 10.10 but keep wineoss in winecfg
http://bugs.winehq.org/show_bug.cgi?id=23384
Luis Alvarado luisalvaradox@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #15 from Luis Alvarado luisalvaradox@gmail.com 2011-07-25 14:41:31 CDT --- This has been solved in 1.3.25 since now it only shows OSS and ALSA. The tab now opens fast.
http://bugs.winehq.org/show_bug.cgi?id=23384
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Alexandre Julliard julliard@winehq.org 2011-08-05 12:37:56 CDT --- Closing bugs fixed in 1.3.26.