http://bugs.winehq.org/show_bug.cgi?id=18454
Summary: Rosetta Stone Online trial speech recognition component doesn't work Product: Wine Version: 1.1.21 Platform: Other URL: http://trial3.rosettastoneclassroom.com OS/Version: other Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dank@kegel.com
The current Rosetta Stone Online offering (a real web app, not the downloadable win32 client in bug 18433) works in Linux Firefox except for the speech recognition part, which is a downloadable .exe or .msi, so I tried it in Firefox on Wine. The speech package will download and install, but doesn't seem to function. The console shows
The RosettaStoneDaemon service is starting. The RosettaStoneDaemon service was started successfully. fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented recv failed with error 28 for socket 160 ...
and then the app says the speech component has a problem. Tried to get a +relay log without luck.
The trial was free because I am evaluating it for a school. I only have it for another six days.
http://bugs.winehq.org/show_bug.cgi?id=18454
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
--- Comment #1 from Dan Kegel dank@kegel.com 2009-05-13 08:56:27 --- Looks like the system check page http://launch.rosettastone.com/en/system_recommendations/rs3/ce_trial3 links directly to the setup program for the speech recognition component: http://resources.rosettastone.com/rs3/updates/speech/executables/3.2.3/windo... so adding download keyword.
http://bugs.winehq.org/show_bug.cgi?id=18454
chris ahrendt celticht32@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |celticht32@aol.com
http://bugs.winehq.org/show_bug.cgi?id=18454
--- Comment #2 from Rob Frohne rob.frohne@wallawalla.edu 2011-08-25 16:27:53 CDT --- Created an attachment (id=36106) --> (http://bugs.winehq.org/attachment.cgi?id=36106) mixer.c
This doesn't work for me.
http://bugs.winehq.org/show_bug.cgi?id=18454
--- Comment #3 from Rob Frohne rob.frohne@wallawalla.edu 2011-08-25 16:29:47 CDT --- Created an attachment (id=36107) --> (http://bugs.winehq.org/attachment.cgi?id=36107) time.c
This doesn't work for me.
http://bugs.winehq.org/show_bug.cgi?id=18454
--- Comment #4 from Rob Frohne rob.frohne@wallawalla.edu 2011-08-25 16:31:10 CDT --- Created an attachment (id=36108) --> (http://bugs.winehq.org/attachment.cgi?id=36108) The output of patched wine....
http://bugs.winehq.org/show_bug.cgi?id=18454
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #36108|application/octet-stream |text/plain mime type| | CC| |00cpxxx@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=18454
--- Comment #5 from Bruno Jesus 00cpxxx@gmail.com --- This application requires binding twice in the same port, it uses the real meaning of SO_REUSEADDR in Windows, if we use SO_REUSEPORT to map SO_REUSEADDR it would work (this is already done for OSX).
http://bugs.winehq.org/show_bug.cgi?id=18454
--- Comment #6 from Hans Leidekker hans@meelstraat.net --- (In reply to Bruno Jesus from comment #5)
This application requires binding twice in the same port, it uses the real meaning of SO_REUSEADDR in Windows, if we use SO_REUSEPORT to map SO_REUSEADDR it would work (this is already done for OSX).
Note that SO_REUSEPORT is set in addition to SO_REUSEADDR, so we're actually mapping Windows SO_REUSEADDR to the combination. It's still not correct because on Windows SO_REUSEADDR doesn't have to be set on the first socket while SO_REUSEPORT must be set on all sockets on OSX and Linux.
So the app has to set SO_REUSEADDR on all sockets, which might be the case if it was written with portability in mind, for example.
Linux introduced SO_REUSEPORT in 3.9 with slightly different semantics but it looks like it can be used to improve compatibility in the same way as on OSX.
http://bugs.winehq.org/show_bug.cgi?id=18454
--- Comment #7 from Bruno Jesus 00cpxxx@gmail.com --- I agree with everything you said and I think there are only benefits. Since you are the original author that introduced it for OSX would you mind sending the patch to make it less OS strict?
The discussion about enabling SO_REUSEADDR in all sockets belongs to bug 26031 and I still think it would be valid as seen in http://bugs.winehq.org/attachment.cgi?id=47020&action=diff (which fixes the bug).
http://bugs.winehq.org/show_bug.cgi?id=18454
--- Comment #8 from Hans Leidekker hans@meelstraat.net --- (In reply to Bruno Jesus from comment #7)
I agree with everything you said and I think there are only benefits. Since you are the original author that introduced it for OSX would you mind sending the patch to make it less OS strict?
Sure, I'll try to find some time.
https://bugs.winehq.org/show_bug.cgi?id=18454
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|Other |x86 OS|other |Linux CC| |focht@gmx.net Status|NEW |NEEDINFO
--- Comment #9 from Anastasius Focht focht@gmx.net --- Hello folks,
please retest with recent Wine 5.x releases.
If you are unable to do so, please provide exact steps how to reproduce with a browser in WINEPREFIX. Alternatively abandon the report.
I've created a snapshot via Internet Archive:
https://web.archive.org/web/20200413084219/http://resources.rosettastone.com...
Regards