December 2015 - Wine-Bugs - list.winehq.org

[Bug 16301] New: wine user guide asks the user to run programs without explaining how
by wine-bugs＠winehq.org Feb. 28, 2016

Feb. 28, 2016

http://bugs.winehq.org/show_bug.cgi?id=16301 Summary: wine user guide asks the user to run programs without explaining how Product: WineHQ.org Version: unspecified Platform: Other URL: http://www.winehq.org/site/docs/wineusr-guide/running OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: www-unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: madewokherd(a)gmail.com The introductory page under "Running Wine" (http://www.winehq.org/site/docs/wineusr-guide/running) says this: "Assuming you are using a fake Windows installation, you install applications into Wine in the same way you would in Windows: by running the installer." and gives several examples of wine command lines, including an example for starting a program after it has been installed to C:. Yet there is no explanation of how to run a program or use the wine command. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 4

[Bug 39450] New: The polish FAQ is absolutely terrible
by wine-bugs＠winehq.org Feb. 27, 2016

Feb. 27, 2016

https://bugs.winehq.org/show_bug.cgi?id=39450 Bug ID: 39450 Summary: The polish FAQ is absolutely terrible Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: d33tah(a)gmail.com Distribution: --- I just stumbled upon this wiki article: http://wiki.winehq.org/FAQ_pl Somewhere in the middle of the article there are so many spelling mistakes and the style is so bad it's barely comprehensible. There might be some useful information there, but the article needs a lot of work from someone who knows how to write proper Polish. Could you let the Polish translation team know? Also, I replaced a word starting with "drug" (drugi? drugą? either of those) meaning "second" to "kolejny" ("next") because the word "drug" is not allowed. The spam filter is actually making it much more difficult to write articles. -- 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.

1 6

[Bug 29590] New: Search results do not update on webpage (IE8)
by wine-bugs＠winehq.org Feb. 24, 2016

Feb. 24, 2016

http://bugs.winehq.org/show_bug.cgi?id=29590 Bug #: 29590 Summary: Search results do not update on webpage (IE8) Product: Wine Version: 1.3.36 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: msxml3 AssignedTo: wine-bugs(a)winehq.org ReportedBy: ocean04(a)suomi24.fi Classification: Unclassified winetricks ie8 Open http://asunnot.oikotie.fi Search should update automatically every time you make changes to form fields, but does nothing. Workaround winetricks msxml3 I'll attach msxml log. Most interesting parts are: 003d:fixme:msxml:httprequest_get_statusText stub 0x3c82428 0x2b53cd8 and many lines like: 003d:trace:msxml:domdoc_loadXML (0x36ce620)->(L"{\"responseHeader\":{\"status\":0,\"QTime\":11},\"response\":{\"numFound\":22852,\"start\":0,\"docs\":[]}}" 0x268c612) 003d:err:msxml:doparse Start tag expected, '<' not found 003d:trace:msxml:domdoc_loadXML (0x3cef120)->(L"{\"time\":1326303123.1712}" 0x268bfb2) 003d:err:msxml:doparse Start tag expected, '<' not found -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 16

[Bug 39778] New: Errror when starting app that using LIBCEF(TChromiumEmbedded)
by wine-bugs＠winehq.org Feb. 23, 2016

Feb. 23, 2016

https://bugs.winehq.org/show_bug.cgi?id=39778 Bug ID: 39778 Summary: Errror when starting app that using LIBCEF(TChromiumEmbedded) Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: figufigu(a)mail.ru Distribution: --- Created attachment 53072 --> https://bugs.winehq.org/attachment.cgi?id=53072 backtrace.txt Hi I`m a developer of app, that using libcef.dll(TCHromiumEmbedded) components. App developed with Delphi XE. When I try to start it with Wine162 on Linux Mint 17.2 I have an error, described in attached "backtrace.txt" App was installed in system by standart Windows Installer. Please help me to start it, if i could start it I could move hundreds of users to Linux from Windows. PS: After I temporary exclude TChromium from my App to test Wine, it run succefully)) -- 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.

1 4

[Bug 33100] New: ALSA Audio playback in WINE locks up ALSA capture by other applications
by wine-bugs＠winehq.org Feb. 22, 2016

Feb. 22, 2016

http://bugs.winehq.org/show_bug.cgi?id=33100 Bug #: 33100 Summary: ALSA Audio playback in WINE locks up ALSA capture by other applications Product: Wine Version: 1.5.25 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: torsten.crass(a)eBiology.de Classification: Unclassified Hi there, when trying to record sound (e.g. using arecord) played by some application running on WINE (e.g. vlc.exe) via ALSA, and if the recording application is launched *before* the playback application, recording stops immediately when playback starts, and after a while ALSA reports an "Input/output error". This does not happen with native playback applications, e.g. the Linux version of vlc. Funny enough, if recordings starts *after* playback has begun, everything works fine. How to reproduce: 1. In a terminal, issue sudo alsactl restore; arecord -D default -f dat -v -V stereo test.wav 2. In another terminal, launch vlc.exe by issuing something like WINEPREFIX=/path/to/prefix wine /path/to/vlc.exe /path/to/some/audiofile 3. Wait for a few seconds... and see arecord complaining: arecord: pcm_read:1801: read error: Input/output error 4. Re-launch arecrod: sudo alsactl restore; arecord -D default -f dat -v -V stereo test.wav 5. Watch arecord recording happily ever after. I initially suspected WINE to somehow force access to my soundcard's capture device (A SB Live, which seems not to be dsnoop'd by default), but after creating a dsnoop'd device (which did allow for multiple simultaneous recordings with arecord when playing back audio with Linux's vlc) and teaching WINE to actually use it, the problem unfortunately remained. Best regards -- Torsten P.S. If filed this bug with Debian's wine-unstable-alsa package some two months ago already, but since there hasn't been a single reply up to now and since the problem still remains with 1.5.25 (Debian is still at 1.5.6), I found it appropriate to directly re-file this report at WINE's bug tracking system. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.

1 6

[Bug 39743] New: Dragon NaturallySpeaking 13.0 does not train new user or run old one with sound error
by wine-bugs＠winehq.org Feb. 22, 2016

Feb. 22, 2016

https://bugs.winehq.org/show_bug.cgi?id=39743 Bug ID: 39743 Summary: Dragon NaturallySpeaking 13.0 does not train new user or run old one with sound error Product: Wine-staging Version: 1.7.55 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: susancragin(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 53012 --> https://bugs.winehq.org/attachment.cgi?id=53012 NaturallySpeaking 13.0 crash when installing user voice I created a new 32-bit wine prefix this morning, set the Windows version to 10 (sorry) and installed Dragon NaturallySpeaking 13.0 into it. (Under winecfg, the sound was set to default, which had worked previously.) The NatSpeak installation appeared to go flawlessly. But the program will not run. It starts normally but then says it cannot use my "user," that is, the set of files with my voice data in it. I have tried creating a new user, and that does not work either. I also tried changing the sound to pulseaudio in winecfg, ditto on the no work. An error message says that the program cannot find my sound source. Debian LXDE with all updates. wine-1.7.55 (Staging) Attached: crash report, terminal output. -- 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.

1 14

[Bug 35260] New: Sound weirdness with XCOM: Enemy Within
by wine-bugs＠winehq.org Feb. 22, 2016

Feb. 22, 2016

http://bugs.winehq.org/show_bug.cgi?id=35260 Bug ID: 35260 Summary: Sound weirdness with XCOM: Enemy Within Product: Wine Version: 1.7.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winealsa.drv Assignee: wine-bugs(a)winehq.org Reporter: lama(a)lamamail.de Classification: Unclassified This is a strange one... I'll just describe what happened: - I'm using the digital out on my sound card. This works fine with everything but this game in WINE - Got the game working after registering XAudio2_7.dll - There is no sound whatsoever ingame (also no sound options beyond a mixer) - After running the game I have no sound anywhere anymore, even after closing all WINE processes. No errors while playing though (so it's not blocked), just quiet - Mixer settings are fine - Turns out the default ALSA device has been changed to the analog output, even after explicitly selecting the digital output (instead of default) in WINE. Only a reboot fixes this. ALSA documentation doesn't even mention this as a possibility. Oh, and game audio still isn't played through that either. I've tested this with WINE 1.7.9 and built from GIT. -- 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.

1 10

[Bug 36694] New: Using PBM_SETPOS to change the position of a progress bar to what it was before after a style change (for instance, leaving marquee mode) does not redraw the progress bar
by wine-bugs＠winehq.org Feb. 21, 2016

Feb. 21, 2016

http://bugs.winehq.org/show_bug.cgi?id=36694 Bug ID: 36694 Summary: Using PBM_SETPOS to change the position of a progress bar to what it was before after a style change (for instance, leaving marquee mode) does not redraw the progress bar Product: Wine Version: 1.7.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: pietro10(a)mac.com Created attachment 48733 --> http://bugs.winehq.org/attachment.cgi?id=48733 The test program that can be used to duplicate this behavior. If you do this when you switch out of marquee mode on a progress bar: SendMessage(pbar, PBM_SETMARQUEE, FALSE, 0); SetWindowLongPtr(pbar, GWL_STYLE, GetWindowLongPtr(hwnd, GWL_STYLE) & ~PBS_MARQUEE); SendMessage(pbar, PBM_SETPOS, currentPos, 0); the progress bar will not redraw, and thus will continue to show the marquee animation frozen at the place it was at the time of the above call. Attached is a sample program that will demonstrate this behavior. Set one value, then click Marquee and Set again. On Windows XP (at least), the progress bar will redraw properly with the second click of Set. The attached file is also available at https://github.com/andlabs/misctestprogs/blob/master/winprogresstest.c. (As marquees are a comctl32 version 6 feature, you may need a manifest file.) Looking at the soruce, I see here - http://source.winehq.org/source/dlls/comctl32/progress.c#L639 - that the implementation's handling of PBM_SETPOS only draws the progressbar if the new position is different. Thus, I could come up with a variety of ways to fix it, such as adding a style change check there, or always redrawing the progress bar, or redrawing on a style change... but I don't know which is the most correct, so I'll leave it to the experts. Thanks. -- 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.

1 6

[Bug 39760] New: MDK (MDKD3D.EXE) graphics not drawn correctly
by wine-bugs＠winehq.org Feb. 20, 2016

Feb. 20, 2016

https://bugs.winehq.org/show_bug.cgi?id=39760 Bug ID: 39760 Summary: MDK (MDKD3D.EXE) graphics not drawn correctly Product: Wine Version: 1.8-rc3 Hardware: x86 OS: Mac OS X Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jeffz(a)jeffz.name I'm not sure that bug #3569 was actually fixed, but seeing as two different bugs were actually being discussed there (the DirectDraw version of MDK, and the Direct3D version), things were not very clear. I'm splitting it here. Tested on OSX 10.9.5. http://jeffz.name/mdkdemo_repack.tar.bz2 winecfg virtual desktop set to 640x480 cd ~/.wine/drive_c && tar xf ~/mdkdemo_repack.tar.bz2 && cd mdkdemo_repack wine MDKD3D.EXE Credit/intro screen loads. Main menu loads. Start a new game and the loading screen persists to flicker over the game graphics. Confirmed that this bug does not happen on Windows 7. It works fine there. -- 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.

1 5

[Bug 39010] New: Wine msiexec fails while trying to install PhysX
by wine-bugs＠winehq.org Feb. 20, 2016

Feb. 20, 2016

https://bugs.winehq.org/show_bug.cgi?id=39010 Bug ID: 39010 Summary: Wine msiexec fails while trying to install PhysX Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: ban.artem.v(a)gmail.com Distribution: --- Created attachment 51964 --> https://bugs.winehq.org/attachment.cgi?id=51964 Output I got trying to install PhysX with winetricks I tried to install Mass Effect 2. Firstly I tried to run PhysX installer from game setup. I got message 'The program msiexec.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience'. Then I tried to install PhysX with winetricks. Then I downloaded different versions of PhysX from official site and runned 'wine msiexec /i' manually. Then I tried using msiexec downloaded from the Internet. I got the same error every time. -- 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.

1 7